macOS 15 Sequoia on Unsupported Macs Thread

[Coselmann]

I have now tried it several days without the problem. Thanks again!

Thanks!

 

[rehkram]

Heads up, a new build of 15.7.2 is available, takes 15.7.2 from 24G313 to 24G317. According to the sys updater content window it contains security fixes. Seems to be installing OK using OTA on an rMBP10,1 2012 (unsupported) and a min8,1 2018 (supported).

 

[rehkram]

I spoke too soon. While the supported min8,1 update went well, the unsupported rMBP10,1 came up with the older version 24G313 still installed. So I'll wait until it's available for manual download via the OCLP 'Create Installer' function.

 

[MacinMan]

I spoke too soon. While the supported min8,1 update went well, the unsupported rMBP10,1 came up with the older version 24G313 still installed. So I'll wait until it's available for manual download via the OCLP 'Create Installer' function.

Since you have a supported, and unsupported Mac, you may be a good one to ask about a problem I've had in Messages after upgrading to Sequoia. From Monterey, to Sonoma, whenever I would get a code in SMS for 2FA, it would be underlined, and I could right click and select "copy code". That is gone under Sequoia, and checking the Apple Support community seems to be a mixed bag where some still have it, and for others it's gone. Is there a way to get it back in Sequoia? It's not a big deal, as I can just double click the code to select it and copy, but if I can get the shortcut back, it would be nice.

 

[iMac'd]

With the delay or possible impossibility of Tahoe becoming workable via OCLP - I've tried using Google Gemini to find a way to stop getting reports/badges about Tahoe - but to get them for updates to Sequoia or the current installed OS. Unless Gemini missed some readily available options then my 3 hours on the topic indicates that it can't be done.
The further context here is that the badge showing 1. for updates in system settings won't change when updates for the currently installed OS are available; so only manual checks will reveal when updates are available.

 

[rehkram]

Replying to MacinMan, I have not seen (or maybe just not noticed) that problem here but I'm more often using the supported mini these days. I'm keeping the rMBP10,1 up to date purely for standby purposes and general curiosity.

 

[MacinMan]

I have not seen (or maybe 'noticed') that problem here but I'm more often using the supported mini these days. rMBP10,1 is purely on standby.

OK, according to what I gathered reading on the Apple support communities, it was happening with supported Macs too.
They usually don't like open core talk over there, so most people reporting problems I've asked about are using a supported mac of some kind.

 

[rehkram]

.

 

[rehkram]

I spoke too soon. While the supported min8,1 update went well, the unsupported rMBP10,1 came up with the older version 24G313 still installed. So I'll wait until it's available for manual download via the OCLP 'Create Installer' function.

Update later: I got the OTA update to work successfully by selecting the 'Update Tonight' option, letting it finish download- & prep normally, then selecting 'Update Now'. Successfully updated the rMBP10,1 from 15.7.2 (24G313) to build 24G317, on first login OCLP 2.4.1 prompted to reinstall patches as expected.

 

[amaze1499]

Update later: I got the OTA update to work successfully by selecting the 'Update Tonight' option, letting it finish download- & prep normally, then selecting 'Update Now'. Successfully updated the rMBP10,1 from 15.7.2 (24G313) to build 24G317, on first login OCLP 2.4.1 prompted to reinstall patches as expected.

Same here OTA update to 24G317 done without any interruptions. Patched using 2.4.1.

 

[macpro_mid2014]

OTA update to Sequoia 15.7.2 on my MBP11,2. OCLP 2.4.1 patched the system without issues.

 

[BloxUnskilleden]

Wait. There is a 15.7.2?

 

[hvds]

Wait. There is a 15.7.2?

Still a release candidate (RC2) but probably a release soon.

 

[brotherjoe]

Wait. There is a 15.7.2?

I think only available for Beta/RCC.

 

[Larsvonhier]

24G317 running fine and without any (new) troubles on cMP3,1 (single CPU) and cMP5,1.
OC 2.4.1 / 2.4.0 patches still work and hold.

 

[Daniel Pascoal]

Hey all, I've run into some slight issues toggling between my installed versions of macOS, and was hoping someone could give me some pointers on how to optimize things. Whenever I've been running in Monterey for a while, and reboot back into Sequoia things are extremely slow, for about 5 to 10 minutes after the initial reboot. Going the other way, Monterey is only sluggish for about maybe 2 minutes or so. Both are on the internal Fusion drive, and share the entire drive via APFS Volumes. Is there a way to optimize Sequoia's login process ? Loading the same stuff always seem slower on Sequoia than Monterey. Is there any part of OCLP I can disable, that might run at startup, that may not run under Monterey, as it's not needed? After things have settled down things are fine, and if I reboot Sequoia, without switching installs, things are fine as well. So I'm mainly asking if I can optimize load times between switching installs.

I'll help you out, as I also dual boot my 2012 Macbook Pro and had exactly the same headaches of high cpu usage while switching OSes, I'm also using fusion drive with a 2TB SSD (on the optical drive slot) + 2TB HDD, and have no issues with speed, though my SSD is much larger, but I don't think the Fusion drive is you problem.

Mac OS was never designed to dual boot between versions, it's designed to upgrade the OS only, and therefore when you start up the newer OS it immediately detects an older indexing Spotlight DB and starts to update it to the new version, hence the slowness on start, you're getting the new OS installed feeling every time, you'll see a high mds process cpu usage. And when you return to the older OS it detects a unsupported Spotlight DB, discards it and starts over the indexing.

There's two solutions for this, you either disable Spotlight on every volume that are accessed from both OSes, by adding the volume on Spotlight Privacy list, inside Spotlight settings. This sets a flag on the volume itself, so both OSes will know not to index that volume. You will lose the ability to search for files using Spotlight for that volume.

The other option is prevent the auto-mount of the volume that you don't want Spotlight touching, by adding the Volume UUID using "sudo vifs", Google this for more precise instructions.

I use a combination of both, by preventing the OS to mount the other OS volume, thus keeping Spotlight, and I have other Volumes for personal files storage with Spotlight disabled, so I can access them on whichever OS is running.

Additionally, if you want your supported MacOS running vanilia, with all security enabled, you have to uncheck NVRAM WriteFlash on OCLP, rebuild and install OpenCore, and perform the NVRAM reset once, by holding Option-Command-P-R keys when powering on. After that you should only boot to the supported OS by holding the Option key (leave OCLP for newer OS only). This will keep both OS NVRAM settings clompletely separated. You can check the security by running: csrutil status

Hope this helps everyone swithing between MacOS versions, as I spent a long time figuring this out.

And thank you very much to all OCLP developers, it's amazing!

 

[MacinMan]

I'll help you out, as I also dual boot my 2012 Macbook Pro and had exactly the same headaches of high cpu usage while switching OSes, I'm also using fusion drive with a 2TB SSD (on the optical drive slot) + 2TB HDD, and have no issues with speed, though my SSD is much larger, but I don't think the Fusion drive is you problem.

Mac OS was never designed to dual boot between versions, it's designed to upgrade the OS only, and therefore when you start up the newer OS it immediately detects an older indexing Spotlight DB and starts to update it to the new version, hence the slowness on start, you're getting the new OS installed feeling every time, you'll see a high mds process cpu usage. And when you return to the older OS it detects a unsupported Spotlight DB, discards it and starts over the indexing.

There's two solutions for this, you either disable Spotlight on every volume that are accessed from both OSes, by adding the volume on Spotlight Privacy list, inside Spotlight settings. This sets a flag on the volume itself, so both OSes will know not to index that volume. You will lose the ability to search for files using Spotlight for that volume.

The other option is prevent the auto-mount of the volume that you don't want Spotlight touching, by adding the Volume UUID using "sudo vifs", Google this for more precise instructions.

I use a combination of both, by preventing the OS to mount the other OS volume, thus keeping Spotlight, and I have other Volumes for personal files storage with Spotlight disabled, so I can access them on whichever OS is running.

Additionally, if you want your supported MacOS running vanilia, with all security enabled, you have to uncheck NVRAM WriteFlash on OCLP, rebuild and install OpenCore, and perform the NVRAM reset once, by holding Option-Command-P-R keys when powering on. After that you should only boot to the supported OS by holding the Option key (leave OCLP for newer OS only). This will keep both OS NVRAM settings clompletely separated. You can check the security by running: csrutil status

Hope this helps everyone swithing between MacOS versions, as I spent a long time figuring this out.

And thank you very much to all OCLP developers, it's amazing!

Thanks for the help, I will keep these steps handy, when I dual boot again. For Now, I've signed out of iCloud on the older installer of Monterey, and deleted the APFS volume, leaving only Sequoia. Right now, Sequoia is stable, and if I ever need something not supported on the unsupported install, I'll dual boot Monterey, and Linux, and use Linux as the newer OS, and keep Monterey as my supported OS for Apple specific features, that don't require OCLP to use.

 

[amaze1499]

OTA update to 24G322 went without interventions. Patched using 2.4.1. All in all the performance seem to have degraded due to the amount of background processes running parallel in 15.7.2 and the amount of RAM thats being used. Swap is being active quite often as well. More than before.

 

[MacinMan]

OTA update to 24G322 went without interventions. Patched using 2.4.1. All in all the performance seem to have degraded due to the amount of background processes running parallel in 15.7.2 and the amount of RAM thats being used. Swap is being active quite often as well. More than before.

So, is it not a good idea to update, for a production machine? This iMac has 32 GB RAM, and I've never had swap even enabled on here, or if it is there, it's never used.

 

[rehkram]

OTA update to 24G322 went without interventions. Patched using 2.4.1. All in all the performance seem to have degraded due to the amount of background processes running parallel in 15.7.2 and the amount of RAM thats being used. Swap is being active quite often as well. More than before.

Thanks, betaWiki IDs it as RC3

I've updated my small herd of 2 Macs:

1. Supported macMini8,1 2018 OTA update completed normally, running normally.

2. Unsupported rMBP10,1 2012 w/OCLP 2.4.1 still downloading, will report progress later.

 

[s3eker]

my 2013 iMac with 1.25TB Fusion Drive and 16GB RAM getting slower on Mac OS sequoia. it's going worse on every. updates. same as my rMBP 11,2 2013.

 

[rehkram]

2. Unsupported rMBP10,1 2012 w/OCLP 2.4.1 still downloading, will report progress later.

Failed to install. Used OTA "Update tonight" to download and prep, completed normally. Then hit the "Restart now" which stalled; after an hour I forced power off, waited 10 seconds and restarted. It came up still on the previous, RC2

I might try removing the patches before restarting when I get time.

 

[rehkram]

I might try removing the patches before restarting when I get time.

SilentKnight found some updates so I installed them first. Be careful when doing this, the RC3 will be in the list of updates found. So I used SK's named updates function, copying and pasting each of the three items (in my case) into the dialog box, see SK menu > File > Install Named Update

I then reverted the patches and ran OTA "Install later" ---> "Restart now" again from the top. It updated the rMBP10,1 2012 to 15.7.2 RC3 (24G322) successfully, and I reapplied the OCLP post install patches when auto-prompted on first login. It's running fine, no fan noise, Activity Monitor showing everything is nominal.

BTW the SK updates found were:

XProtectPlistConfigData 2025-10-21 13:38:43 +0000 : 5319
XProtectPayloads 2025-08-06 00:07:31 +0000 : 153
MRTConfigData 2025-10-21 13:37:19 +0000 : 1.93

 

[MacinMan]

SilentKnight found some updates so I installed them first. Be careful before doing this, the RC3 might be in the list of updates found. So I used SK's named updates function, copying and pasting each of the three items (in my case) into the dialog box, see SK menu > File > Install Named Update

I then reverted the patches and ran OTA "Install later" ---> "Restart now" again from the top. It updated the rMBP10,1 2012 to 15.7.2 RC3 (24G322) successfully, and I reapplied the OCLP post install patches when auto-prompted on first login.

BTW the SK updates found were:

XProtectPlistConfigData 2025-10-21 13:38:43 +0000 : 5319
XProtectPayloads 2025-08-06 00:07:31 +0000 : 153
MRTConfigData 2025-10-21 13:37:19 +0000 : 1.93

What updates did SilentKnight show you? I usually check from time to time to make sure I'm up to date, so just wondering if they were updates common to any Mac.

Thanks for the edit, and info. I just checked here, and the only update found is the Tahoe upgrade. Everything else is up to date for me.

 

[basslik]

Updated my Sequoia to the current version on my 5,1

For some reason, is feels snappier than before.

I noticed it right away when I click on the system settings. A little quicker.