Thank You. With iPhone, password and Syned Tabs it is still too much hassle to move to alternate browser. Let's see if Cloudflare could update their tools instead.
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.
macOS 14 Sonoma on Unsupported Macs Thread
- Thread starter dhinakg
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Thank You. With iPhone, password and Syned Tabs it is still too much hassle to move to alternate browser. Let's see if Cloudflare could update their tools instead.
I have installed Sonoma and then Sequoia on my MacBook Air 2017, MacbookPro mid 2015 and iMac 2015 using OCLP. Most things seem to work ok but having problems with the graphics on NIK collection ver7 on my MBP dual graphics laptop. I have tried opening the apps on their own and from within Photoshop and have updated to latest version but still they do not work has anyone had experience of this or able to suggest a work around?
Hi
macOS 14.7.6 (23H626) is now officially released
OCLP 2.4.0 released too
macOS 14.7.6 (23H626) is now officially released
OCLP 2.4.0 released too
Last edited:
@TheIntruder By “currently supported OSes” do you mean supported by OCLP, or supported by Apple?
Because Apple definitely doesn’t support macOS Ventura anymore. Only Sonoma and Sequoia.
I have a Late 2012 Mac mini (quad-core Core i7) and Sonoma 14.7.4 seems to run pretty well on it. I’m using an external Thunderbolt 1 SSD as my boot volume. No obvious glitches while running, I have had issues where the external SSD was not ‘seen’ at boot time, and some graphics issues that were mostly addressed by the root patches in OCLP 2.3.2.
Smooth upgrade from Sonoma 14.7.5 -> 14.7.6 and Safari 18.4 -> 18.5 on my HackBookPro6,2 (non-metal Nvidia Tesla). Applying post-install patches with OCLP 2.2.0. Posting this with Safari 18.5. All good for my limited use of this museum piece 
As opposed to its stance on hardware status, Apple's (infuriatingly unstated) policy is to support the current OS, plus the last two versions.
Ventura 13.7.5 was issued less than a month-and-a-half ago, and 13.7.6 was issued today.
Mea culpa. Our IT folks at my work had drilled it into my head that only the current and previous OS were well and truly supported.
Hi, @Riot Nrrrd! First of all, you're not wrong about Sonoma as it's the last mature macOS before Apple started to fundamentally revolutionise the entire System, especially suitable for silicon Macs, to experiment with integrating AI features, incompatible with Intel Macs.
Ventura, therefore, was a transition between the solid Monterey (which up to one version still had all the drivers for all Mac hardware, etc.) and the new features in view of Sonoma and Sequoia; which are almost the same, but Sequoia is not as stable with older Macs compared to Sonoma, although it seems as smooth and snappy as Sonoma. (You can also read my posts on the thread regarding Sequoia and unsupported Macs).
As for the fact that some Macs sometimes refuse to boot from external disks, it could be due to the (little known) fact that some USB ports have a DFU function or are dedicated to Apple test tools. Search the Internet for this and their layout on the Mac.
It could also depend on the reduced power of some ports.
You can try changing ports or using a HUB whose stability and speed you are sure of.
In my case, for example, Bluetooth does not work at Mac start-up (so Apple's Magic devices do not work) when a device not formatted with APFS is connected to the ports on the back of my iMac, but also if there are multiple devices connected on the back. On the contrary, Bluetooth at Mac start-up works if I connect some devices (even exFAT or JHFS+) to an old Amazon Basic USB 3.0 HUB. But be careful because there are HUBs whose connected devices disconnect sometimes for no reason, other times if they are under stress or when the Mac goes into standby.
Perhaps many people have never noticed this problem because they do not use OCLP and do not use FileVault, which requires the password at start-up, before loading the entire operating system. Or they have a wired mouse and keyboard. In this case, disks plugged in at the back do not cause any problems for Bluetooth when the Mac starts up. Whereas if you have Apple's Magic wireless devices (mouse, keyboard and trackpad), it becomes impossible to start Recovery Utilities or install OCLP EFIBoot or reset NVRAM or enter the FileVault password or press OPTION to select an internal or external boot disk, etc.
Conversely, if nothing needs to be done at start-up, the Mac gets to the Login password screen or directly to the Desktop without any problems and everything seems to work.
So I also assume that Bluetooth requires more power at start-up and hangs if there are multiple devices connected to the Mac, but also if there is only one not formatted in APFS (maybe APFS draws less power?... It might).
Last edited:
Understandable. It all begins with Apple's disrespectful attitude toward users, even enterprise users, who aren't given clear guidance as to what the software support timelines are.
At least with hardware, we know it will be declared "vintage" (ceased sales more than 5 and less than 7 years ago), then then "obsolete" (more than 7 years ago), and what that means in terms of parts and service.
For software, everyone has to read the tea leaves, resulting in stories like this and this.
MS, for all its history and faults, has more transparency in this respect.
Anyway, any further experiences with 14.7.6? OCLP auto updated itself to 2.4.0, but I've held off on the OS update.
I've found in general that I have to keep things as simple as possible. I have no Apple wireless devices on any of my Macs at the moment. I have an old Bluetooth keyboard and Bluetooth mouse lying around but I try to never use them, and certainly not on OCLP Macs. I'm on a wired Apple keyboard and wired Microsoft Intellimouse Explorer 3 mouse (no trackpad) as I type this, for example.
When I go to System Preferences -> Bluetooth, under "My Devices" there's nothing, and under "Nearby Devices" it says "Searching..." with a forever spinning cursor. I'm not even sure this OCLP 2012 Mac mini (running macOS Sonoma 14.7.4 atm) even has working Bluetooth ...
Sonoma 14.7.6 with OCLP 2.4.0 on MBA (see sig) via OTA update. No glitches or hitches. Running smoothly.
I've read on the Sequoia thread that Intel dual core machines like the MBA can feel sluggish on 15.x.x. Sticking with Sonoma for now.
I've read on the Sequoia thread that Intel dual core machines like the MBA can feel sluggish on 15.x.x. Sticking with Sonoma for now.
Don't worry, @riot Nrrrd… As OCLP has long since made many Macs so stable in everything, as if Apple were selling them... My iMac 14,2 at least, officially stopped at Catalina, had already achieved absolute perfection with Monterey.
After that, the switch to Ventura had brought a few minor bugs, but these disappeared with the latest Ventura’s versions.
Then came Sonoma, and already by version 14.3 I began to realise that the pinnacle of quality had now been definitely reached!
Unfortunately, I expected the same thing with macOS 15 Sequoia and foolishly installed it as soon as the official version was available. But with Sequoia I felt like I no longer had a Mac, but a pc (note the lower case characters for “pc”
asta:...).The fault does not lie with OCLP but with the changes Apple is making to the System, which is now (rightly) geared to working well with Apple Silicon CPUs/GPUs; as well as having to be integrated with AI technologies... Which makes Sequoia an almost experimental 'hybrid', waiting for a totally new System...
Updated to 14.7.6 with OCLP 2.4.0. No major issues.
But I noticed one minor change -- the Sunrise/Sunset widget was blank after the update, and there is no readily apparent way to "fix" by removing it because it can't be reinstalled. It no longer appears in the options under the Weather category.
Edit to add -- the Filevault boot issue has long been a known problem, native to Mac OS, and forcing peripheral makers like Logitech to include disclaimers in their documentation, and displayed on their packaging.
But I noticed one minor change -- the Sunrise/Sunset widget was blank after the update, and there is no readily apparent way to "fix" by removing it because it can't be reinstalled. It no longer appears in the options under the Weather category.
Edit to add -- the Filevault boot issue has long been a known problem, native to Mac OS, and forcing peripheral makers like Logitech to include disclaimers in their documentation, and displayed on their packaging.
Last edited:
Updated my cMP 5,1 to 14.7.6 from 14.7.5 today using a USB stick. I Reverted Root Patches on my 14.7.5 volume first before updating. The update is very slow at times, but patience is a virtue and well worth not interrupting it (form lessons learned).
I use RefindPlus as my boot loader (MyBootMgr 104) so there's a few extra steps needed to update my RefindPlus EFI partition and the USB Stick.
In the config.plist file (generated by OCLP) I search "launcher" and change
Apple's Safari (17.6), Music app and AppleTV all seem to play fine. Never had issues with them previously other than Music crashing when searching for Apple Music songs (works fine now).
I use RefindPlus as my boot loader (MyBootMgr 104) so there's a few extra steps needed to update my RefindPlus EFI partition and the USB Stick.
In the config.plist file (generated by OCLP) I search "launcher" and change
<string>Full</string> to <string>Disabled</string>. While I'm there I also add in Innie (just below WhateverGreen). I then deploy the updated OC folders to my RefindPlus EFI>EFI>OC_X01 and OC_X02 folders as well as the USB Stick EFI>EFI>OC folder. A bit of a rigmarole, but it allows me to run Windows Legacy.Apple's Safari (17.6), Music app and AppleTV all seem to play fine. Never had issues with them previously other than Music crashing when searching for Apple Music songs (works fine now).
Just a short note about an issue I am having after updating to 14.7.6 and OCLP 2.4.0 on my MacBook Pro 9,1.
Launching Photos leaves the system with a black screen. Photos doesn't crash, but any attempt to quit the app or minimize from the keyboard has no effect.
I can log into my MBP from another machine using screen sharing. From my screen sharing client I see a live working desktop on the laptop.
Using a brand new user test account gives the same result.
It appears that if you can connect from another system through screen sharing you will be able to log out of the account without having to do a hard shutdown. The screen will then recover.
I've checked the OCLP Discord forum to see if there was anything reported there, so far nothing.
So, this may just be my system. I'm continuing to investigate and I will report back if I find something useful.
Launching Photos leaves the system with a black screen. Photos doesn't crash, but any attempt to quit the app or minimize from the keyboard has no effect.
I can log into my MBP from another machine using screen sharing. From my screen sharing client I see a live working desktop on the laptop.
Using a brand new user test account gives the same result.
It appears that if you can connect from another system through screen sharing you will be able to log out of the account without having to do a hard shutdown. The screen will then recover.
I've checked the OCLP Discord forum to see if there was anything reported there, so far nothing.
So, this may just be my system. I'm continuing to investigate and I will report back if I find something useful.
I've had that issue since quite a while ago on Monterey with legacy Metal Kepler. For me it was Google maps that would crash the tab. I had to disable webgl on Safari by changing settings using defaults command. Did not have to use tech preview Safari.
OCLP 1.4.2, macOS 14.7.5 -> macOS 14.7.6 OTA, macbookpro 11,2. I hit an issue.
Normally I would uninstall root patch before running the OTA, but this time I forgot.
The macbook rebooted 2 times during the update, then got stuck on third boot at 40% for 20 minutes. Hard reset, still stuck at 40%.
Booted into safe mode (shift + enter when on OpenCore's boot menu), booted past 40%, the update completed. Prompted for username, entered desktop. Opened OCLP, removed root patches. Reboot. Still stuck at 40%.
Booted into safe mode again. Manually deleted some kext from /Library/System/Extensions (as part of the OCLP resolution for being stuck at boot after root patching). Reboot. Now I can boot normally without safe boot.
Booted normally. Opened OCLP, removed root patches again just to be safe. Reboot. Open OCLP, install root patches. Reboot. I'm up and running.
Now I have OCLP 1.4.2, macOS 14.7.6 running flawlessly.
Normally I would uninstall root patch before running the OTA, but this time I forgot.
The macbook rebooted 2 times during the update, then got stuck on third boot at 40% for 20 minutes. Hard reset, still stuck at 40%.
Booted into safe mode (shift + enter when on OpenCore's boot menu), booted past 40%, the update completed. Prompted for username, entered desktop. Opened OCLP, removed root patches. Reboot. Still stuck at 40%.
Booted into safe mode again. Manually deleted some kext from /Library/System/Extensions (as part of the OCLP resolution for being stuck at boot after root patching). Reboot. Now I can boot normally without safe boot.
Booted normally. Opened OCLP, removed root patches again just to be safe. Reboot. Open OCLP, install root patches. Reboot. I'm up and running.
Now I have OCLP 1.4.2, macOS 14.7.6 running flawlessly.
I reformatted the hard drive to HFS+ and did a clean install of Mojave. Runs much faster than Catalina. Leaving as is, I like the fact iTunes is back - good for audiobook file edits.
I'm tempted to upgrade my 15" MacBook Pro 2015 [intel only graphics] from Catalina to OCLP Sonoma although I just use it to AirDrop photos and videos from my iPhone 11 Pro Max.
I browse on it from time to time using Firefox ESR which still receives updates and security patches.
I know I can upgrade to Monterey but the beach ball and the lag during Disk Utility and install made me decide to just keep it on Catalina.
I browse on it from time to time using Firefox ESR which still receives updates and security patches.
I know I can upgrade to Monterey but the beach ball and the lag during Disk Utility and install made me decide to just keep it on Catalina.
macOS 14.7.6 installed atop 14.7.5 OTA, OCLP 2.4.0, runs as expected.
👏
👏
Last edited:
Updated rMBP 11,3 Late 2013 to OCLP 2.4.0 and then USB installer to update to 14.7.6 no problems.
Yesterday MBP 11,4 Mid 2015 to OCLP 2.4.0 and then OTA to 14.7.6 no problems.
There is an ongoing minor issue that plagues the 11,3 but not the 11,4. These are essentially the same machine but the 11,4 is a little slower and has no video card NVIDIA GT 750M. Both have 16GB RAM and have been upgraded to 2TB OWC SD. The 11,3 often, but particularly when checking for updates, pops up the crash window (attached) for the nsattributedstringagent. It appears to be harmless (for my purposes) but a dozen such windows will pop up every few seconds and must be dismissed. It interferes with what I am doing at the moment and is ... unesthetic.
Does anyone know a fix for this?
Yesterday MBP 11,4 Mid 2015 to OCLP 2.4.0 and then OTA to 14.7.6 no problems.
There is an ongoing minor issue that plagues the 11,3 but not the 11,4. These are essentially the same machine but the 11,4 is a little slower and has no video card NVIDIA GT 750M. Both have 16GB RAM and have been upgraded to 2TB OWC SD. The 11,3 often, but particularly when checking for updates, pops up the crash window (attached) for the nsattributedstringagent. It appears to be harmless (for my purposes) but a dozen such windows will pop up every few seconds and must be dismissed. It interferes with what I am doing at the moment and is ... unesthetic.
Does anyone know a fix for this?
Sonoma 14.7.5 and now 14.7.6 are crashing my TV app whenever it is opened.macOS 14.7.6 installed atop 14.7.5 OTA, OCLP 2.4.0, runs as expected.
My Classic macPro 5,1 with Sonoma 14.7.5 had been working fine until about 2 weeks ago when the TV app suddenly started to crash whenever I tried to open the app., or if another app, such as Get iPlayer Automator, tried to open it.
I didn't resolve this issue and went straight back to Monterey, which has always worked well as far as the TV app was concerned. I rely on the TV app for all my TV viewing (about 20 TB of TV shows and Movies) on 3x24 TB RAID drives—(The Original, The Father-BackUp, and The GrandFather-Backup).
When Sonoma 14.7.6 was released after waiting a few days to see if anyone was reporting issues with the TV app., on it. As I did not see any I updated my Sonoma drive (using a USB install over the original), hoping this might fix the TV app crashing... - it was a hope, not an expectation.
It has not corrected the problem. It is obviously something else.
Here is a zipped copy of the crash report. Does anyone have a suggestion as to what I may try to fix this?
Thanks...
Thanks for pointing that out.
defaults write com.apple.Safari WebKitPreferences.webGLEnabled 0
I tried it in the latest Safari on my machine and it does seem to fix most issues I've had with Safari. Of course if you actually need WebGL then using the older Safari Tech Preview seems to be the way to go.
A couple of you - @JedNZ and @RumorChaser - have said this past week that you backed out the root patches before going OTA to 14.7.6. What is the reasoning, is this common knowledge? I’ve never heard about it before today.
Some have noticed that the OTA update is more reliable when you are running without the root patches. I've noticed in the past that it can take multiple attempts to get an OTA to start or complete when running with the root patches. On my current setup with Sequoia and the past couple of revisions of OCLP it seems to work fairly well to just run with the root patches.
I think results also vary with the particular hardware you have.This is probably one of those things where you should use whatever method works best for you. Some people always make a USB installer and update that way to avoid the OTA updates entirely. I have used that method myself in the past when I was having issues with the OTA update. USB installer is probably the safest way to go.