OpenCore Legacy Patcher does two separate jobs. OpenCore lives on your EFI partition and convinces macOS to install and boot on hardware Apple dropped. Root patches are different: they copy legacy drivers back into the macOS system volume itself, restoring graphics acceleration, Wi-Fi, Bluetooth and audio.
Because root patches modify the system volume, every macOS update replaces them — even a small 15.6.1 security update. Your Mac still boots, but the patched hardware stops working until you reapply them.
The two halves of OCLP, and why only one survives updates
People treat OpenCore Legacy Patcher as one thing. It isn't, and the distinction is the whole game:
| What it is | Where it lives | Survives a macOS update? |
|---|---|---|
| OpenCore — the bootloader that spoofs supported hardware so macOS will install and start | The EFI partition, outside macOS entirely | Yes. Updates never touch the EFI partition. |
Root patches — legacy kexts and frameworks copied into /System to restore GPU, Wi-Fi, Bluetooth, audio | Inside the macOS system volume | No. An update ships a fresh system volume and your patches go with the old one. |
This is why your Mac keeps booting perfectly after an update but suddenly feels broken. OpenCore did its job. The root patches were overwritten.
Why macOS can't just leave them alone
Since Big Sur, macOS boots from a Signed System Volume — a read-only snapshot of /System with a cryptographic seal over its entire contents. Apple verifies that seal at boot. The design goal is that nothing, including root, can alter the system files.
Root patching necessarily breaks that seal: OCLP mounts the system volume writable, injects the legacy drivers Apple deleted, and rebuilds the snapshot without a valid Apple signature. That's not a bug in OCLP, it's the only way to put a 2011 GPU driver back into an OS that shipped without one.
An update doesn't patch files in place — it installs a whole new sealed system volume. There is no mechanism by which your modifications could carry across, which is why OCLP has to redo the work every single time.
A visible side effect: because the seal is broken, your Mac can no longer take small delta updates. macOS will download the full installer (often 12 GB or more) for what would otherwise be a 700 MB update. That's expected on a patched machine, not a sign of trouble.
How to tell your root patches are missing
You don't need to guess. Open OpenCore Legacy Patcher and look at Post-Install Root Patch — it reports what is currently applied and what your Mac needs. If it lists patches as available to install on a Mac you already patched, an update wiped them.
The symptoms are also fairly distinctive:
- ✓Window dragging and Mission Control feel like a slideshow, and transparency effects are gone
- ✓The Wi-Fi menu bar icon has vanished entirely, or shows no hardware installed
- ✓Bluetooth reports “not available” and won't turn on
- ✓The built-in webcam or the SD card slot stopped being detected
- ✓Everything above started the moment you installed a macOS update
If instead your Mac won't reach the desktop at all, root patches aren't your problem — see Mac stuck on boot after OCLP.
Reapplying them, step by step
Update OCLP before you update macOS.
An older OCLP build often doesn't know how to patch a newer macOS. Grab the current release from the download page first — this single habit prevents most post-update disasters.
Open OCLP and choose Post-Install Root Patch.
It detects your Mac and the running macOS version, then lists exactly which patches apply. You don't select anything manually.
Click Start Root Patching and authenticate.
It mounts the system volume, injects the drivers and rebuilds the snapshot. Expect several minutes, and expect the fans on an older Mac. Don't sleep the machine or close the lid.
Reboot when prompted.
The patches only take effect on the next boot. Graphics acceleration, Wi-Fi and Bluetooth should all return together — they're restored in the same pass.
OCLP can do most of this for you. Its auto-patcher notices that the OS changed underneath it and offers to reapply patches shortly after you log in following an update. If you dismissed that notification, the manual route above is identical in effect.
The habit that makes this a non-event
Treat a macOS update on a patched Mac as a two-part operation, never one:
- Update OCLP itself.
- Install the macOS update.
- Reapply root patches.
- Then judge whether anything is broken.
Nearly every “OCLP broke my Mac” report is someone judging at step 2. If you do all four in order, an update on a patched Mac is as boring as it is on a supported one.
Common questions
Do I need to reapply root patches after every single macOS update?
Yes — including minor point releases and security updates. Any update that replaces the system volume removes them. The only updates that don't are Safari-only or XProtect definition updates, which leave the system volume alone.
Is it safe to run macOS with root patches applied?
It's safe in the sense that it works and is reversible, but be clear about the trade: your system volume is no longer sealed and System Integrity Protection is partially lowered so the patches can be written. On a machine holding sensitive data, that's a real consideration.
My Mac needs no root patches at all. Did something go wrong?
No — that's the best possible outcome. Newer Metal-capable Macs (roughly 2013 onward, with modern Broadcom Wi-Fi) run current macOS with nothing but OpenCore. Those machines are unaffected by updates and need no reapplication.
Can I re-enable SIP after patching?
Don't do it manually from Recovery. Root patches depend on the SIP state OCLP configured; forcing full SIP back on typically produces a Mac that boots to a broken desktop. If you want stock SIP, revert the root patches first — see how to uninstall OCLP cleanly.