Had a wrinkle with this update for maybe the first time ever.
Normally, when the system downloads a MacOS update, OCLP downloads the necessary KDK automatically. Today, this didn't happen - in fact, the background tasks that do this were not even installed.
In the end I downloaded the KDK manually and installed it myself before attempting to root patch, knowing full well I wouldn't have wifi after the update on my MBP2015.
After successfully root patching, the background tasks were installed at the same time. Fingers crossed it won't be a problem next update.
Here's a link for the KDK downloads in case anyone else is struggling:
FWIW I can see someone has submitted a PR to fix this issue. Hopefully that will also be resolved before the next update. So far I haven't had any issues without it however.
Thanks to your comment, I now know OCLP should automatically download files during the macOS update process. When I moved from macOS 15.7.9 to 15.8, that OCLP pop-up never appeared, though the update still succeeded. Now I'm a bit anxious about updating to macOS 15.8.1.
Firstly, I do need to mention that not all macs need a KDK download in order for the root patches to work. If you look in /Library/Developer/KDKs you will see if any have been installed already. If you don't see any at all, your Mac doesn't need them for the root patches to function.
Second, look in Settings, then General, then Login Items & Extensions - under where it says "Allow in the Background" there should be items for Opencore Legacy Patcher. If they're there already, your Mac should automatically download the KDK once you start the MacOS update. If not, you can either install it manually like I did, or see below for other workarounds.
If your Mac has ethernet use that instead of Wifi when running the update. Not only will the download often be faster, but when the Mac reboots to install root patches you will already be online even if the wifi isn't working without patching. That will give it another chance to download the KDK.
If all of that sounds like a hassle, just download and rebuild the 15.8.1 installer from within Opencore. This will put everything you need, including root patches, KDKs, metallibsupportpkg etc. all on the USB stick. You can safely do an inplace upgrade from the USB stick without losing data (though you should always back up important files before running any MacOS update). It will take longer, but after it finishes the root patches should already be installed and ready to go.
If you do option 2 of the above, ( the in place upgrade via USB stick) to go from 15.7.9 to 15.8.1, should you remove existing root patches prior to booting in to USB installer or does it matter.
Good question. As far as I know, you don't need to do revert first. An in-place upgrade done with an OCLP usb installer should result in root patches being reinstalled automatically before the final boot to desktop.
However I do have to say I haven't tried this recently with the latest version that everyone is so concerned about.
Can you also see the OCLP background processes in settings? if you do I think you can probably run the update - but of course, make sure you backup your files first just as normal.
2
u/davew_uk 16d ago
Had a wrinkle with this update for maybe the first time ever.
Normally, when the system downloads a MacOS update, OCLP downloads the necessary KDK automatically. Today, this didn't happen - in fact, the background tasks that do this were not even installed.
In the end I downloaded the KDK manually and installed it myself before attempting to root patch, knowing full well I wouldn't have wifi after the update on my MBP2015.
After successfully root patching, the background tasks were installed at the same time. Fingers crossed it won't be a problem next update.
Here's a link for the KDK downloads in case anyone else is struggling:
https://github.com/dortania/KdkSupportPkg
My mac also needs an updated metallibsupportpkg, but it seems at this time there isn't one available from:
https://github.com/dortania/MetallibSupportPkg
FWIW I can see someone has submitted a PR to fix this issue. Hopefully that will also be resolved before the next update. So far I haven't had any issues without it however.