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 15 Sequoia on Unsupported Macs Thread
- Thread starter flagers
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I tried the compact view a while back when it was new, and I was testing it under Monterey (supported OS.) I just didn't like it, so I've kept the standard layout. I've heard compact view has bugs on supported macs too.
I've updated my main laptop, a 2013 MBA, to Sonoma 14.8. Now that Tahoe has come out, I'm thinking of an OTA update to Sequoia 15.7, which I'm already running on a 2013 MBA I use for testing. I've waited because earlier versions of Sequoia were unstable on my MBA while Sonoma was reliably stable after about 14.5.
My two questions: What apps aren't working on Sequoia 15.7? What are the main reasons to upgrade from 14.8 to 15.7?
My two questions: What apps aren't working on Sequoia 15.7? What are the main reasons to upgrade from 14.8 to 15.7?
Last edited:
Having used Sonoma for a while first before going back and trying Sequoia again, for me just about anything I need to do works.
I've updated my Mid 2012 MBP to 15.7. It seems that while WebGL is still not working in Safari 26 that something has changed that allows sites to properly fall back to alternative options perhaps. Both of the sites I regularly use that wouldn't work are now working in Safari 26. I'm going to try running 26 instead of the older Tech Preview version for a while and see how it goes.
Is the WebGL a limitation of your specific model? It works here on this late 2015, 27" iMac.
Too late - I reinstalled all the Office apps via App Store already.
Everything works except OneNote - it's unable to create a notebook. It's important to note that you still have to turn off Copilot in the settings of each app, no matter what Microsoft says about applying your privacy preferences to the apps.
I'll try installing with the standard combined .dmg package with the next update and share the log - I suspect it won't be very detailed, with similar "update error" verbiage.
Everything works except OneNote - it's unable to create a notebook. It's important to note that you still have to turn off Copilot in the settings of each app, no matter what Microsoft says about applying your privacy preferences to the apps.
I'll try installing with the standard combined .dmg package with the next update and share the log - I suspect it won't be very detailed, with similar "update error" verbiage.
I have LibreOffice installed, I don't own a copy of MS office anymore. Does it not like a patched OS?
The Microsoft Office apps run fine after you install on an OCLP system, it's just that AutoUpdate fails.
It takes a long time to download and install the new versions, then gives up with "Update error" and no details. Retrying doesn't help at all.
We'll see if the App Store versions update properly when Microsoft releases the next round of updates in a few weeks. They have announced that they'll be forcing Copilot app installs on the Windows versions in October.
It takes a long time to download and install the new versions, then gives up with "Update error" and no details. Retrying doesn't help at all.
We'll see if the App Store versions update properly when Microsoft releases the next round of updates in a few weeks. They have announced that they'll be forcing Copilot app installs on the Windows versions in October.
Seems strange that the auto update issue would be tied to OCLP, sounds more like Microsoft's poor coding.
It is a hot mess for sure. I've had Word completely bork and required multiple restarts to get working again when I tried to update it a few months back. Now I'm just leaving it as is. When my license expires with my university course finishing, I'll promptly uninstall and revert back to Pages which is where I do all my work anyway. I just copy into Word so that the formatting is correct as Pages has done a rubbish job of doing so since iWork 😅
I had enless issues with Sonoma on my rMBP which haven't come up at all since being on Sequoia. One of my main crumbles was Safari crashing whenever I used keyboard shortcuts to switch tabs. I can't begin to explain how frustrating it was. The other reason for updating was to ensure iCloud, macOS and iOS were all on the latest versions so that they operated in harmony. My 2011 Mac Mini has never shown many issues but then it doesn't do a whole lot these days.
Before I jump to 26, I'll run it off an external drive for a month to see how things play out. Sad that this will be the last update for my Intel Macs
Use LibreOffice, it's a lot better now, and people have said it's much more compatible with Office these days.
The failure of Microsoft Autoupdate while running Sequoia on OCLP been mentioned a few times earlier on this thread. It's a well-known issue. Something is borked with running the exit scripts under the automatic updater.
If you download and manually run the individual Office app installers, the installations will complete successfully. I guess the full installer also works, but I've found it easier to work with the individual installers now that Microsoft seems to update individual packages more frequently.
You can download the installer packages from
There was a detailed discussion about the underlying issue on another site somewhere. Unfortunately, I can't find the link at the moment. IIRC, certain types of scripts run extremely slowly when invoked under some circumstances with OCLP and Sequoia, and the autoupdate essentially times out. I think there are other examples besides the Microsoft Autoupdate case, but I may be misremembering.
If you download and manually run the individual Office app installers, the installations will complete successfully. I guess the full installer also works, but I've found it easier to work with the individual installers now that Microsoft seems to update individual packages more frequently.
You can download the installer packages from
Update history for Office for Mac - Office release notes
Provides IT Pros with information about the latest updates for Office for Mac, including links to download packages, and an update history
learn.microsoft.com
There was a detailed discussion about the underlying issue on another site somewhere. Unfortunately, I can't find the link at the moment. IIRC, certain types of scripts run extremely slowly when invoked under some circumstances with OCLP and Sequoia, and the autoupdate essentially times out. I think there are other examples besides the Microsoft Autoupdate case, but I may be misremembering.
I think it's a problem for any machine with a cpu missing the AVX2 instruction set. I think 2013 or 2014 onward are ok, but mine is pre AVX2.
OS15.7 on iMac 18,3, OC 2.4.1
With the latest OC version I tried to enable Microphone access for my various audio interfaces (MOTU, Steinberg) via the TCCPlus option, yet when executing Terminal command to allow microphone access for the respective interface App IDs I get "zsh: killed" error......any guidance or advice on this please? Note AMFIPass is enabled in OC.....thank you
With the latest OC version I tried to enable Microphone access for my various audio interfaces (MOTU, Steinberg) via the TCCPlus option, yet when executing Terminal command to allow microphone access for the respective interface App IDs I get "zsh: killed" error......any guidance or advice on this please? Note AMFIPass is enabled in OC.....thank you
Updated MBP10,2, MBA6,2, MBP14,3 successfully to 15.7. Only MBA6,2 got stuck in the update process. Had to go via safe mode. Now everything (Microsoft Auto-updater doesn't count) seems to work well.
Last edited:
As FYI: With this update, Spotlight was broken again. Only after many tries I was able to enable Spotlight server.
Below as steps to reproduce in case someone faces the same issue:
% sudo rm -rf /.Spotlight-V100 sudo mdutil -i on / sudo mdutil -E / sudo rm -rf /.Spotlight-V100 sudo mdutil -i on / sudo mdutil -E /
Spotlight server is disabled.
Spotlight server is disabled.
Spotlight server is disabled.
Spotlight server is disabled.
....
% sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
% sudo rm -rf /.Spotlight-V100
sudo mdutil -i on /
sudo mdutil -E /
sudo mdutil -s /
/: Indexing enabled.
/: Indexing enabled.
/: Indexing enabled.
Below as steps to reproduce in case someone faces the same issue:
% sudo rm -rf /.Spotlight-V100 sudo mdutil -i on / sudo mdutil -E / sudo rm -rf /.Spotlight-V100 sudo mdutil -i on / sudo mdutil -E /
Spotlight server is disabled.
Spotlight server is disabled.
Spotlight server is disabled.
Spotlight server is disabled.
....
% sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
Unload failed: 5: Input/output error
Try running `launchctl bootout` as root for richer errors.
% sudo rm -rf /.Spotlight-V100
sudo mdutil -i on /
sudo mdutil -E /
sudo mdutil -s /
/: Indexing enabled.
/: Indexing enabled.
/: Indexing enabled.
On MBP11,1: yes, metalllib support package 15.6.1-24G90 was used for patching instead of the direct match for 15.7 which wasn't there yet.
Updated my iMac 14,2 and Mac Mini 7,1 to 15.7 with OCLP 2.4.1 OTA. All went well and both machines running fine as before.
Hi there,
I need some advice on a specific problem I'm having with OCLP on my MacBook Pro 2016 (13,2), which has a broken Touch Bar.
Because of the broken Touch Bar, the integrated T1 chip isn't recognized, making it impossible to boot macOS directly or pass any secure authentication checks (like iCloud). To work around this, I used OCLP to create a USB installer for macOS Sequoia, spoofing the SMBIOS to a MacBookPro13,1 (a similar model without a Touch Bar/T1 chip).
This workaround was successful! The OS is running perfectly, and all services, including iCloud authentication, now work.
However, I've run into a new problem. When I open the OCLP app on the installed system, it detects the mismatch between my actual hardware (13,2) and the spoofed SMBIOS (13,1). It then tries to force a rebuild and installation of the correct OpenCore for my actual model, trapping me in a loop that can't be dismissed to access the app's settings.
It's not a huge deal since I can build OpenCore on another machine, but it's very inconvenient not being able to manage it on the MacBook itself.
My question is: Is there any way to bypass this model check within the OCLP app or edit a config file to prevent it from forcing a rebuild?
Thanks for any help you can provide!
I need some advice on a specific problem I'm having with OCLP on my MacBook Pro 2016 (13,2), which has a broken Touch Bar.
Because of the broken Touch Bar, the integrated T1 chip isn't recognized, making it impossible to boot macOS directly or pass any secure authentication checks (like iCloud). To work around this, I used OCLP to create a USB installer for macOS Sequoia, spoofing the SMBIOS to a MacBookPro13,1 (a similar model without a Touch Bar/T1 chip).
This workaround was successful! The OS is running perfectly, and all services, including iCloud authentication, now work.
However, I've run into a new problem. When I open the OCLP app on the installed system, it detects the mismatch between my actual hardware (13,2) and the spoofed SMBIOS (13,1). It then tries to force a rebuild and installation of the correct OpenCore for my actual model, trapping me in a loop that can't be dismissed to access the app's settings.
It's not a huge deal since I can build OpenCore on another machine, but it's very inconvenient not being able to manage it on the MacBook itself.
My question is: Is there any way to bypass this model check within the OCLP app or edit a config file to prevent it from forcing a rebuild?
Thanks for any help you can provide!
Hi, as far as the touch bar, you need to install the last supported OS for that Mac to get the embedded OS back, and then upgrade to Sequoia from that install. It's been discussed quite a bit by Mr. Macintosh, and others. Maybe someone with a Mac in the same situation as yours can provide more specific info, and experience, since I don't own a touch bar Mac.