Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases macOS Monterey 12.5.1 With Security Updates
- Thread starter MacRumors
- Start date
- Sort by reaction score
This update has completely reset my user account. My home folders are on an external drive, basically it has made my user account a 'new' one with no file associations / libraries. It doesn't know where anything is. Thanks apple for a few hours work!
HobeSoundDarryl
macrumors G5
Did it fix the "unexpected ejection" of a USB drive that remains reliably connected when the same cable is switched to any of my Intel Macs running macOS BEFORE Monterey?
Nope. And it only took a few minutes to find out this time.
I miss "just works" Apple. I wish the U in USB was not like the "unlimited*" in cell plans. It is highly frustrating to have a perfectly stable USB drive when hooked to Intel Macs running earlier versions of macOS but then not have the same with "latest & greatest" Mac Studio running latest macOS version.
Yes, I know that some USB drives work perfectly fine, but that redirection misses the concept of the what the U means. This drive works perfectly fine on Macs- just not my shiny new Silicon Mac running Monterey. And no, this is not a one person issue- there are plenty of threads here, elsewhere and on Apple support forums about unexpected ejections for all kinds of enclosures hooked to Silicon Macs running Monterey (or Big Sur in some cases).
Nope. And it only took a few minutes to find out this time.
I miss "just works" Apple. I wish the U in USB was not like the "unlimited*" in cell plans. It is highly frustrating to have a perfectly stable USB drive when hooked to Intel Macs running earlier versions of macOS but then not have the same with "latest & greatest" Mac Studio running latest macOS version.
Yes, I know that some USB drives work perfectly fine, but that redirection misses the concept of the what the U means. This drive works perfectly fine on Macs- just not my shiny new Silicon Mac running Monterey. And no, this is not a one person issue- there are plenty of threads here, elsewhere and on Apple support forums about unexpected ejections for all kinds of enclosures hooked to Silicon Macs running Monterey (or Big Sur in some cases).
Last edited:
"Just works" went a long time ago, and it is getting more and more frustrating with each update.
Just installed it on my 16-inch Macbook Pro with Apple M1Pro chip
Fixed a bug in 12.5 - it was impossible to switch to other start partitions in Settings (I have a secondary Ventura partition), only with boot options, and Disk Utility did not recognize any partitions.
Is the 12.5.1 update available for a Mac Studio with a M1 Max chip? I was not able to update to 12.5, figured it was because that version had been pulled. But my Mac Studio says I am "Up to Date" on 12.4. I have tried a computer restart and forcing the Mac to search for an update via System Preferences and nothing.
Attachments
My M1 iMac (and M1 MBP) both updated with no issues whatsoever, though it took a good bit of time (9+ minutes).
The Software Update preferences pane on the iMac had a button "Restart now" which when clicked changed to a button ("Download now?" "Install now?" I forget exactly) but I knew from past experience to NOT click that, just leave it be, and within about 10 seconds it restarted and began the update. Bad UX there, after "Restart now" it shouldn't have a button there at all.
That setup are not supported. So… sucks to be you and stop whining.
Yeah, this has been a bug for a while now. Once the preparing update stage is finished, there’s a notification to automatically reboot in 1 minute. Don’t hit the update button! I find if you hit the button, it’ll go back to downloading the update again, which will of course cause the preparing stage to repeat. It essentially wastes 20 minutes of your time. Just let the system reboot itself and the update will install. I think this bug has been there for a year.
Apple seriously needs to fix that.
Curious about something: This update had an Apple Studio Display firmware update that downloaded and installed first before updating the OS on my MBP 14 M1 Max. I've not seen any mention of this studio firmware update and I already had the firmware update installed that Apple pushed out a few months ago for the display. Anyone know what this additional new display firmware update addresses?
Interesting bug - on my Mac Studio & wireless keyboard combo, it turned F11 and 12 into different keys - F11 was "Show Desktop" - so had to reconfigure it in System Preferences.
macOS Monterey has been extremely iffy and unstable on my x86 macs. My guess is that at least the thunderbolt/usb/graphics-protocols is buggy. I've had a LG-monitor being recognised correctly on M1 hardware and not on x86 hardware. I've had WindowServer crashes bricking the machine (possibly related to the former problem, but reliably related to a single user's Preferences regarding Displays). The first time I upgraded one Mac mini to Monterey it was completely unable to drive the monitor (thus bricking it), a SMC reset and NVRAM reset (you could try that) fixed that, but the problem returned. I have failures to wake from deep sleep by wired (Apple) keyboard (USB being so dead it requires disconnecting and reconnecting the device). I've had USB flash disks not being mounted after a reboot (again, disconnecting/reconnecting physically solves the issue). As far as I'm concerned, I wish I never upgraded to Monterey it is a PoJ under the hood.
I had multiple reboots (and boots, sometimes, the process did not reboot itself properly). I seemed to be in a reboot loop myself. It seems party of the update is at least some firmware updates. Then, after about 8 reboots, it suddenly did not halt or restart, but it started saying things like "About 10 minutes remaining..." and the process continued. Looking at it now.
The security issues this update fixes seem to be very serious (and have been exploited in the wild) so it is important to update. But the update itself may have been rushed/iffy. Rock. Hard place.
I had to do a few manual boots during the process (maybe there is some firmware updating going on) but after about 8 times it suddenly proceeded with the update. Some of these starts-stops were really short. So, maybe keeping booting the machine might get you out of it.
After several reboots, some of which I had to initiate myself, the system is again up and running. Now here's hoping it is more stable that it was.
You don't know when they were informed. The information on the CVE is not available yet afaik. Often they are informed long before. It may take them many months to fix. In the meantime they are under pressure because it will be published after a certain period (say 6 months). Then after 5 months they come with the fix.