Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Combo updaters have not been a thing since macOS Catalina (10.15). You just need to either use software update (which works fine) or download a full Ventura installer and run it.
I didn't realize that until I recently tried to download one... I guess there's always the full version, but I'm probably better off sticking with software update.
 
  • Like
Reactions: Pinkyyy 💜🍎
I’m not really sure if understood correctly, but is that what you’re looking for ?

Thank you for the link, but I was looking for something different. The post I replied to (directly above) confirms that my searches were in vain, as they are no longer available - which I did not realize :(
 
  • Sad
Reactions: Pinkyyy 💜🍎
I don't know if this is related, but one of my Macs (Intel) now has the Find My>>Items all borked up.

They show on both of my iPads, iPhones, and M1 Mac mini.

:/

Screen Shot 2023-08-19 at 16.40.38 PM.png
 
Updated from 13.4.1 to 13.5.1 no issues. Confirmed Location Bug FIXED. Same 18 apps with proper toggle settings showed up in the System Settings/Privacy & Security/Location Services window. Thanks to all for posting the bug.

BONUS: 13.5 or 13.5.1 FIXED three other bugs:

1) Opening window from the Weather app and News app always crept down about a half inch upon reopening. Had to resize every time. Finally remembers size in this OS version, FIXED. Maybe solved by Finder version update from 13.4 to 13.5?

2) FIXED consistent very high CPU use when accessing System Settings/Internet Accounts/iCloud settings. Worked fine when accessed through System Settings/Apple ID/iCloud. Worked with 2 senior advisors for over a month starting last April. One advisor (using Intel) was able to duplicate. Bug started when I updated from 12.6.4 to 13.3. Finally fixed in 13.5.1.

3) FIXED Terminal command bug to return EFI firmware Integrity check on Intel computers. The terminal command stopped working some time after I think 13.3? But now the command works as before and returns proper results.

And, EFI firmware (Boot ROM version) updated correctly from 512.0.0.0.0 to current, 515.0.0.0.0, no problem. Hardware specific and Intel only.
 


Apple today released macOS Ventura 13.5.1, a bug fix update for the macOS Ventura operating system released last October. macOS Ventura 13.5.1 comes three weeks after the launch of macOS Ventura 13.5.

Ventura-Macs-Feature-Red.jpg

The ‌‌‌‌macOS Ventura‌‌‌‌ 13.5.1 update can be downloaded for free on all eligible Macs using the Software Update section of System Settings.

macOS Ventura 13.5.1 addresses a bug that impacts location services settings on the Mac. Mac users have complained since July of an issue with the location privacy settings, with the bug preventing them from accessing and controling location permissions for first and third-party apps.

macos-13-5-location-services.jpg

Under System Settings > Privacy and Security > Location Services, macOS Ventura 13.5 had no apps listed, preventing users from accessing location services toggles or seeing apps that have access to their location information. Newly installed apps were also unable to be given access to location.

According to Apple's release notes, the macOS 13.5.1 update fixes the issue, so Location Services should work as expected going forward.

Article Link: Apple Releases macOS Ventura 13.5.1 With Fix for Location Services Bug
 
Hi everybody. I made the update but curiously it is not 13.5.1. My update is 13.5 (22G74)... Anybody know why?
 
Hi everybody. I made the update but curiously it is not 13.5.1. My update is 13.5 (22G74)... Anybody know why?
Check for updates again. Open Software Update and if it doesn’t refresh automatically, type command-r.
 
Check for updates again. Open Software Update and if it doesn’t refresh automatically, type command-r.
Hi chrfr. Thanks for your answer but I tried (Command-r) but the only choice that appear is for Sonoma 14 beta 3 (and I'm not ready for Sonoma...). The choice in my Beta updates is for Mac Os Ventura Public updates and I got Ventura 13.5 (22G74). And like I said, other choice is for Sonoma... I restart my MAc and nothing change.
 
Hi chrfr. Thanks for your answer but I tried (Command-r) but the only choice that appear is for Sonoma 14 beta 3 (and I'm not ready for Sonoma...). The choice in my Beta updates is for Mac Os Ventura Public updates and I got Ventura 13.5 (22G74). And like I said, other choice is for Sonoma... I restart my MAc and nothing change.
Turn off beta updates and check again.
 
Updated from 13.4.1 to 13.5.1 no issues. Confirmed Location Bug FIXED. Same 18 apps with proper toggle settings showed up in the System Settings/Privacy & Security/Location Services window. Thanks to all for posting the bug.

BONUS: 13.5 or 13.5.1 FIXED three other bugs:

1) Opening window from the Weather app and News app always crept down about a half inch upon reopening. Had to resize every time. Finally remembers size in this OS version, FIXED. Maybe solved by Finder version update from 13.4 to 13.5?

2) FIXED consistent very high CPU use when accessing System Settings/Internet Accounts/iCloud settings. Worked fine when accessed through System Settings/Apple ID/iCloud. Worked with 2 senior advisors for over a month starting last April. One advisor (using Intel) was able to duplicate. Bug started when I updated from 12.6.4 to 13.3. Finally fixed in 13.5.1.

3) FIXED Terminal command bug to return EFI firmware Integrity check on Intel computers. The terminal command stopped working some time after I think 13.3? But now the command works as before and returns proper results.

And, EFI firmware (Boot ROM version) updated correctly from 512.0.0.0.0 to current, 515.0.0.0.0, no problem. Hardware specific and Intel only.
I think most of this would have been 13.5. To be sure, there are no firmware updates when going from 13.5 to 13.5.1.
 
Did this break 1Password autofill/connection in Chrome browsers or is it just a coincidence?

EDIT: Weird, on my Mac Studio, both Chrome and Edge 1PW extensions failed to connect to 1PW. Had to reinstall both browser extensions to get to work again.

It’s a coincidence. I hadn’t initiated the update until today but my 1PW in Chrome broke as well last week before updating to 13.5.1
 
  • Like
Reactions: netnothing
I think most of this would have been 13.5. To be sure, there are no firmware updates when going from 13.5 to 13.5.1.
Agreed. No way to test though, as I skipped 13.5. I was worried about the firmware not updating as its inclusion was documented in 13.5, but maybe skipped in 13.5.1. Happily worried for no reason. yup. And grateful that the odd System Settings CPU and Terminal command bugs were crushed for me. Shows they are still working on our lowly little Intel critters. Ventura's the last OS on this machine, until M3 upgrade next year...
 
Ever since upgrading to 13.5.1 the external drive volume I use for Time Machine will no longer mount! What's even weirder is that another volume (that I use for random stuff) on the same drive still mounts and works fine. No amount of rebooting, unplugging/replugging, First Aid, or attempts to mount using Disk Utility app or diskutil in Terminal have solved the problem.

Also, the volume that does mount refuses to eject or unmount.

Has anyone else seen anything weird like this? Any ideas????

BTW, this is on a 2023 16-inch MacBook Pro with M2 Pro.

Thanks!
 
System to system was around 1.4GB for my M1 MBP all done and dusted in about 10 minutes. At 12GB that's the complete OS...

Q-6
Yes. Even my old 2012 MBP updated too quickly for it to have downloaded the entire 12GB. But even 1.4GB for a patch for such a small bug is crazy. I guess I'm just a spoiled Linux user :cool:
 


Apple today released macOS Ventura 13.5.1, a bug fix update for the macOS Ventura operating system released last October. macOS Ventura 13.5.1 comes three weeks after the launch of macOS Ventura 13.5.

Ventura-Macs-Feature-Red.jpg

The ‌‌‌‌macOS Ventura‌‌‌‌ 13.5.1 update can be downloaded for free on all eligible Macs using the Software Update section of System Settings.

macOS Ventura 13.5.1 addresses a bug that impacts location services settings on the Mac. Mac users have complained since July of an issue with the location privacy settings, with the bug preventing them from accessing and controling location permissions for first and third-party apps.

macos-13-5-location-services.jpg

Under System Settings > Privacy and Security > Location Services, macOS Ventura 13.5 had no apps listed, preventing users from accessing location services toggles or seeing apps that have access to their location information. Newly installed apps were also unable to be given access to location.

According to Apple's release notes, the macOS 13.5.1 update fixes the issue, so Location Services should work as expected going forward.

Article Link: Apple Releases macOS Ventura 13.5.1 With Fix for Location Services Bug
Wherre is t
in case anyone actually wants to know, the update does indeed fix the Location Services bug. It took just about ten minutes to download and update. Never ceases to amaze me that Apple gets trashed on MacRumors for fixing something. Well, Apple gets trashed on MacRumors for everything doesn't it?
 


Apple today released macOS Ventura 13.5.1, a bug fix update for the macOS Ventura operating system released last October. macOS Ventura 13.5.1 comes three weeks after the launch of macOS Ventura 13.5.

Ventura-Macs-Feature-Red.jpg

The ‌‌‌‌macOS Ventura‌‌‌‌ 13.5.1 update can be downloaded for free on all eligible Macs using the Software Update section of System Settings.

macOS Ventura 13.5.1 addresses a bug that impacts location services settings on the Mac. Mac users have complained since July of an issue with the location privacy settings, with the bug preventing them from accessing and controling location permissions for first and third-party apps.

macos-13-5-location-services.jpg

Under System Settings > Privacy and Security > Location Services, macOS Ventura 13.5 had no apps listed, preventing users from accessing location services toggles or seeing apps that have access to their location information. Newly installed apps were also unable to be given access to location.

According to Apple's release notes, the macOS 13.5.1 update fixes the issue, so Location Services should work as expected going forward.

Article Link: Apple Releases macOS Ventura 13.5.1 With Fix for Location Services Bug
Where is the Big new iMac that can take lots of photo files and music file any kind of files, where is the speed increase and where is the touch screen bugger AI lets get back to basics memory storage and speed And bloody cheap
 
I'd like to know if this fixes the Ventura bug where Time Machine causes serious corruption on internal disks when creating APFS snapshots, under allocation and over allocation errors etc. This problem happened on a 2019 Intel Mac.
I went through serious issues back in June 2021 with a brand new mac and TM… out of the box. So much troubleshooting and they blamed me- said it must be something external, etc. Turns out it was a big issue. My replacement that they gave me has worked fine for two years…. Now it’s crashing again. Went through this in 2021- got so bad I could only get 5-10 mins before it’d crash.

Disk utility shows some issue relating to Time Machine. Told me to run repair in recovery mode. That failed. Told me to back up my stuff.

So now I’m on borrowed time again and Apple likely has no solutions once again.

Please let me know if you find any way to repair these issues stemming from Time Machine.
 
I went through serious issues back in June 2021 with a brand new mac and TM… out of the box. So much troubleshooting and they blamed me- said it must be something external, etc. Turns out it was a big issue. My replacement that they gave me has worked fine for two years…. Now it’s crashing again. Went through this in 2021- got so bad I could only get 5-10 mins before it’d crash.

Disk utility shows some issue relating to Time Machine. Told me to run repair in recovery mode. That failed. Told me to back up my stuff.

So now I’m on borrowed time again and Apple likely has no solutions once again.

Please let me know if you find any way to repair these issues stemming from Time Machine.

The corruption I'm referring to seems to be different than yours. Our Mac was working just fine in this regard for 4 years, and the problem started when updating to Ventura from Monterey, and seemed to go away when I did a wipe and revert to Monterey from Ventura. It seems to be a bug introduced in Ventura, or else made much more frequent in that it was never seen otherwise before. Also the corruption seems to appear on multiple machines that updated to Ventura of different types, again seeming to be a Ventura bug, the other machine being an M1 Mini.
 
The corruption I'm referring to seems to be different than yours. Our Mac was working just fine in this regard for 4 years, and the problem started when updating to Ventura from Monterey, and seemed to go away when I did a wipe and revert to Monterey from Ventura. It seems to be a bug introduced in Ventura, or else made much more frequent in that it was never seen otherwise before. Also the corruption seems to appear on multiple machines that updated to Ventura of different types, again seeming to be a Ventura bug, the other machine being an M1 Mini.
When I had to get a new computer (after my iMac died after 8 years of flawless use), they were on Big Sur and I couldn’t move backward because it was a new machine. It sounds like the issue possibly started back then based on the thread I found here and that it wasn’t solved with the next OS. The TM issues date back to 2021.

I’m pretty good at problem-solving and taking out different variables to isolate the cause of the issue, but given the history I have here- it really appears to be rooted in their TM system overall and I don’t doubt a certain OS brought out more issues for people. I wait longer now to update the OS because they’ve been increasingly more problematic over the years.

Given what disk utility is telling me- corruption is from TM. Why is it starting the past few weeks and was mostly ok for almost two years—- I can’t figure that out. This machine would glitch every now and again when I got it which leads me to believe the issue was still there to some extent and now getting worse which is what happened on that first machine (just at an accelerated pace on the first machine).

I’m going to look into other backups like the clone one people mention and if I can make it through my season… come December- I’ll have to wipe the machine and see if I can rid it of the corruption and never set up Time Machine. Disappointing bc TM was always such a useful tool. Just disappointed it causes such a severe problem and Apple hasn’t fixed whatever is going on. Was hopeful someone had some sort of workaround or fix.
 
When I had to get a new computer (after my iMac died after 8 years of flawless use), they were on Big Sur and I couldn’t move backward because it was a new machine. It sounds like the issue possibly started back then based on the thread I found here and that it wasn’t solved with the next OS. The TM issues date back to 2021.

I’m pretty good at problem-solving and taking out different variables to isolate the cause of the issue, but given the history I have here- it really appears to be rooted in their TM system overall and I don’t doubt a certain OS brought out more issues for people. I wait longer now to update the OS because they’ve been increasingly more problematic over the years.

Given what disk utility is telling me- corruption is from TM. Why is it starting the past few weeks and was mostly ok for almost two years—- I can’t figure that out. This machine would glitch every now and again when I got it which leads me to believe the issue was still there to some extent and now getting worse which is what happened on that first machine (just at an accelerated pace on the first machine).

I’m going to look into other backups like the clone one people mention and if I can make it through my season… come December- I’ll have to wipe the machine and see if I can rid it of the corruption and never set up Time Machine. Disappointing bc TM was always such a useful tool. Just disappointed it causes such a severe problem and Apple hasn’t fixed whatever is going on. Was hopeful someone had some sort of workaround or fix.

I should clarify that for the most part the corruption I observed did not seem to manifest in normal computer behavior, but rather just showed up in Disk Utility Disk First Aid results.

Here is an example of the output showing the corruption:

Code:
...
Checking snapshot 16 of 21 (com.apple.TimeMachine.2023-09-05-132507.local)
Checking snapshot 17 of 21 (com.apple.TimeMachine.2023-09-05-143055.local)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (55780288 + 4)
warning: mismatch between extentref entry reference count (1) and calculated fsroot entry reference count (0) for extent (112160392 + 4)
Checking snapshot 18 of 21 (com.apple.TimeMachine.2023-09-05-153750.local)
error: mismatch between extentref entry reference count (-1) and calculated fsroot entry reference count (0) for extent (55780288 + 4)
error: mismatch between extentref entry reference count (-1) and calculated fsroot entry reference count (0) for extent (112160392 + 4)
Checking snapshot 19 of 21 (com.apple.TimeMachine.2023-09-05-164920.local)
Checking snapshot 20 of 21 (com.apple.TimeMachine.2023-09-05-175128.local)
Checking snapshot 21 of 21 (com.apple.TimeMachine.2023-09-05-190156.local)
Checking the document ID tree.
Checking the fsroot tree.
Checking the extent ref tree.
Checking the file key rolling tree.
Verifying volume object map space.
The volume /dev/rdisk3s5 was found to be corrupt and needs to be repaired.
...
Verifying allocated space.
Performing deferred repairs.
error: orphan/invalid physical extent (55780288) at snapshot 1669273
Skipped 4/4 repairs of this type in total.
error: missing/invalid physical extent (112160396 + 8) with refcnt 1 at snapshot 1669273
Skipped 2/2 repairs of this type in total.
Deferred repairs skipped.
The container /dev/disk0s2 could not be verified completely.
Storage system check exit code is 8.
Storage system verify or repair failed. : (-69716)
Operation successful.

I should also say Disk First Aid reports a green checkmark despite reporting this extents problem.

Now, this sounds like a very serious issue, but at the same time it seems specific to the Mac internal disk APFS snapshots themselves. Those snapshots normally only live 24 hours, and if I manually delete them in Disk Utility and run Disk First Aid again, it says there are no problems. But then within a day or so the problem comes back.

In theory this problem may be like those medical conditions where you don't know you have the problem if you haven't run the test because there weren't outward symptoms, so this might be something that looks terrible but isn't an actual problem because the regular non-snapshot filesystem isn't impacted.

However, I can't know for sure, and Apple shouldn't be allowing this to happen. They should be fixing whatever is causing this.

Also on one machine there were seemingly new errors in a program, and it may have been a coincidence, but I couldn't know that it wasn't caused by the same issue manifesting to the live filesystem, hence I decided to rollback the OS.

EDIT: That particular quoted output was from the M1 Mini, which was a less serious manifestation. The 2019 Intel iMac I mentioned first had more occurrences of the error, and it was the latter with the program errors.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.