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.6 With Security Updates
- Thread starter MacRumors
- Start date
- Sort by reaction score
Interesting. I haven't seen that bug. Whatever the case, seems like there are multiple issues with QuickLook.
Thanks. This is all new to me. I Googled and found: 'A content delivery network (CDN) refers to a geographically distributed group of servers which work together to provide fast delivery of Internet content.' I understand it is something like the backbone of the MacAppStore.
In what directory is this cache stored? I see that you can specify what volume you want the cache to live on, but no indication of where on that volume.
Upon updating, I noticed that my battery health went up from 85 to 97...
Planned longevity.
I just updated to Monterrey for the first time and it works better than Big Sur. I update to a whole new OS version everytime it gets to X.6... So it was time to move to Monterrey. It is the best way to always use a stable Mac.
Last edited:
Yeah, I updated to Monterey few months ago, and I noticed it much snappier than Big Sur.
The Mr. Macintosh blog links all point to direct Apple downloads. Nothing is hosted on the blog itself.
HobeSoundDarryl
macrumors G5
Another update!!! Will this one fix the "unexpected ejection" problems with some- but not all- enclosures hooked to Silicon Macs... that doesn't happen when the same device using the same cable is hooked to Intel Macs running macOS before Big Sur?
To date, a perfectly stable HDD enclosure with my Intel Macs hasn't been able to remain connected for more than about 3 hours to my "latest & greatest" Mac Studio Ultra. I've tested through multiple cables and ALL ports and I'm far from the only one with this problem.
Try, trying again and will post the outcome either way. Fingers crossed that Apple finally worked on Silicon port management software to get it as "universally" compatible (the promise of USB ports) as Intel Macs running older macOS versions!
Update (not quite 24 hours of 12.6)
Here's hoping Apple fixes this in Ventura. ☹️
To date, a perfectly stable HDD enclosure with my Intel Macs hasn't been able to remain connected for more than about 3 hours to my "latest & greatest" Mac Studio Ultra. I've tested through multiple cables and ALL ports and I'm far from the only one with this problem.
Try, trying again and will post the outcome either way. Fingers crossed that Apple finally worked on Silicon port management software to get it as "universally" compatible (the promise of USB ports) as Intel Macs running older macOS versions!
- Update (2 hours): so far, so good. About 70+ minutes more would be a new record. Will update again.
- Update (4 hours): new record time. Could this bug(s) have finally be addressed? I'll give it the night and update again.
- Update (11 hours): still connected!!! 🎉🎉🎉
Update (not quite 24 hours of 12.6)
Last edited:
So this looks like security updates only? Pity as I was hoping Apple would fix the core problems with Monterey; constant slow downs, applications failing to open and requiring force quitting and restarting the Mac to get out of whatever is happening, Finder search hanging... the list goes on... Monterey is at times borderline unusable.
They threw us a bone with Saf 16, what more do you want?
I believe it's called Stage Fright.
To cut costs Apple has the OS checked by the same reviewers that check submissions for the app store. I believe they're given about five minutes to evaluate the product. The only difference between the review process for macOS and a third-party app is that the macOS ships regardless of whether it passes the review.
CoreAudio constantly breaking?? How so?
I'd be dead if CoreAudio was constantly breaking here as my Mac is primarily for Cubase Pro and Ableton Live.
Not a single audio issue here at all through all of Monterey with my MOTU interface or the built in audio on my Mac Mini.
That's good. I have AirPods problems pretty regularly. Haven't used my Monterey machine with anything else though.
One would think but I specifically tried this and I can see the update still coming from Apple CDN.
This feature doesn’t seem to work reliably, and Eclectic Light Company has documented evidence of it actually preventing the installation of XProtect updates which I can also confirm.
That's what happens on my 16/512 m1 Mini if i start sifting through photos stored on a spinning hard drive. Sometimes I can fix it with Force Quit on the Finder, other times it requires a reboot.
The other thing I get is when I sift through photos on an SSD, and Finder takes up more and more memory into the 2 or 3 GB range until everything comes to a halt, reboot.
I've also had a pesky memory problem with kernel_task taking up more and more memory into the 2 or 3 GB range. But I installed macOS 12.6 six hours ago, and Finder and kernel-task are using small amounts of memory and not increasing. Maybe they've been taught to LET GO OF MEMORY WHEN YOU'RE DONE WITH IT.
I found this good explanation:
When FileVault is enabled it encrypts EVERYTHING on the SSD and doesn't allow even the computer to have access to that data until you enter your password. That includes the software that loads during startup which would normally activate such things as the backlighting on your keyboard and the touch-bar. Which is why, with FileVault enabled, the login screen you get at startup is stored on Apple's version of their BIOS chipset, NOT on the SSD. After you enter your password on startup the decryption process begins and all of those necessary pieces of software start to load. Making your keyboard backlight turn on and your touch-bar activate. This is not a flaw or an oversight. It is how FileVault was built and how it protects against ALL AVENUES of data breech/intrusion. You'll be amazed at how hackers can devise code to use the backlight of the keyboard to hack into data on the storage device.
This is interesting. Is battery capacity only displayed on M1/2 Macs? My Intel MBP on 12.6 doesn't display capacity on this screen. It's different in one other way, though - it has a checkbox next to "Manage battery longevity."
Looks like that might be the case, but it was last updated in July, and if there's a significant security exploit in the wild I would hope that they might consider patching it. My 2012 rMBP is still going strong as a secondary device and I'm not quite ready to retire it.