OpenCore Legacy Patcher Root Patching Errors and Fixes

Root patching is the step where OpenCore Legacy Patcher writes the drivers Apple removed back onto your system volume — graphics, Wi-Fi, Bluetooth, USB 1.1. It is also the step most likely to throw an error, because it has to break the seal on a volume macOS would rather keep locked.

These are the errors OCLP produces during patching and what each one actually means. If the Mac will not boot at all, you want Mac won’t boot after OpenCore Legacy Patcher instead.

“Unable to resolve dependencies, error code 71”

The most common root patching failure. It typically means you have offending kernel extensions in /Library/Extensions — third-party kexts left behind by old drivers, RAID utilities, virtualisation tools or audio interfaces, which OCLP cannot reconcile against the patched system.

The fix is to clear that folder, keeping only the three extensions known to be safe. Work through these in order and stop as soon as patching succeeds.

Fix 1 — clear the extensions folder

The quick way, in Terminal. Replace Macintosh HD with your actual drive name if it differs — check with ls /Volumes:

sudo zsh
cd "/Volumes/Macintosh HD/Library/Extensions" && ls | grep -v "HighPoint*\|SoftRAID*" | xargs rm -rf

Prefer to see what you are deleting? Do it by hand instead. Navigate to /Library/Extensions and delete everything except these three:

• HighPointIOP.kext
• HighPointRR.kext
• SoftRAID.kext

Then run the OCLP root patcher again.

Fix 2 — clear the Kernel Debug Kits

If it still fails, navigate to /Library/Developer/KDKs and delete everything inside. A corrupt or mismatched Kernel Debug Kit will block patching just as effectively as a stray kext. Run the root patcher again.

Fix 3 — reset to the sealed snapshot

If it fails a third time, the system volume itself is in a bad state. Roll it back to the last sealed snapshot, then patch from clean:

sudo bless --mount "/Volumes/Macintosh HD/" --bootefi --last-sealed-snapshot

Again, substitute your real drive name. Run the root patcher once more afterwards.

This command is run from a booted macOS, which is why it needs sudo. If you are running it from a Recovery Terminal because the Mac will not boot, you are already root and the form is slightly different — see the snapshot revert procedure. Use the variant that matches where you are typing it.

“SystemVersion.plist build version mismatch”

The error names two macOS versions, along these lines:

SystemVersion.plist build version mismatch: found 15.4 (24E247), expected 13.7.5 (22H527)

Your numbers will differ. What matters is that two different versions are named.

Cause: your Mac quietly started downloading a macOS update. Apple’s updates now modify the system volume during the download, before you ever agree to install. That leaves the OS in a liminal state between two versions — partly the version you are running, partly the version it is preparing to become.

The mismatch check is a safeguard, not a bug. OCLP is refusing to patch a system in that state because doing so would very likely leave you unable to boot. Do not look for a way to force past it.

Three ways forward:

1. Go forward. Complete the update to the version already staged, then patch. This only works if that newer version is currently supported by OCLP — check before committing.
2. Reinstall macOS. An in-place install without wiping may work, but can fail: the OS is partially on the newer version and will complain about a downgrade.
3. Clear the pending update. An experimental tool called PurgePendingUpdate removes the staged update so you can patch where you are. It is distributed through the OCLP Discord — look in support-forum under the “Information and known issues” post. You may need to chmod +x both the file and the application path before it will run. If it reports “purge failed”, you can ignore that.

Stop it happening again: disable automatic updates

Strongly recommended once you have recovered, because otherwise this recurs on its own schedule.

• Ventura and newer: System Settings › General › Software Update › the ⓘ next to Automatic Updates › turn off Download new updates when available.
• Big Sur and Monterey: System Preferences › Software Update › Advanced › turn off Download new updates when available.

One irritation to expect: from macOS Sequoia 15.4 onward, Apple prompts you to re-enable automatic updates after every completed update, with no option to decline permanently. You will need to turn this off again after each one.

“Privileged Helper Tool not found”

OCLP runs parts of itself as root through a Privileged Helper Tool. When that component is missing or broken, patching cannot start.

Fix: reinstall OCLP using the PKG installer. The PKG reinstates the helper tool; simply relaunching the app does not.

The awkward part is that you may need to download it on a machine whose Wi-Fi does not work yet, because Wi-Fi is one of the things root patches restore. Two ways around that:

• Connect by Ethernet instead — the wired driver is generally unaffected.
• Download on another computer and carry it across on a USB drive.

Note that in OCLP 2.3.0 and newer the PKG is the only supported install method — the older app.zip route has been discontinued. If you are following a guide that tells you to unzip an app bundle, that guide predates 2.3.0.

OpenCore Legacy Patcher will not launch

You click the icon, it bounces in the Dock, and nothing opens.

Launch it from Terminal instead, using its real path inside Application Support rather than the Applications shortcut:

/Library/Application Support/Dortania/OpenCore-Patcher.app/Contents/MacOS/OpenCore-Patcher

This starts the same application while leaving the Terminal window attached, so any error it prints on the way up is visible instead of silently discarded. Even when it launches fine this way, that output is the useful part.

SIP will not stay disabled from recoveryOS

You run csrutil in Recovery, set System Integrity Protection how you want it, reboot — and it is back to what it was.

This is deliberate. OCLP overwrites the SIP value on every boot, so that an NVRAM reset cannot leave you with a bricked installation. Your csrutil change is being overruled by design.

Set it in the right place instead: open the OCLP app, go to Patcher Settings, and toggle the specific SIP bits there. OCLP offers three states — SIP Enabled, SIP Lowered (Root Patching), and SIP Disabled. Whatever you choose there is what survives a reboot.

For context on why this matters: on Ventura and newer, every unsupported system needs SIP lowered permanently. Once you have root patched, re-enabling SIP can break the install.

The Mac reboots instead of sleeping (Sleep Wake Failure)

Close the lid or let the machine idle, and instead of hibernating it restarts, often logging a Sleep Wake Failure. This is a known issue on some models — which ones is not documented.

The available fix is a workaround rather than a repair: turn hibernation off.

sudo pmset -a hibernatemode 0

The Mac will still sleep, but stops writing memory to disk for hibernation — so it will not survive losing power while asleep. On a desktop that costs you nothing. On a laptop it means a flat battery loses your session.

Two things worth knowing before you patch

Patch over Ethernet if you can. Some Macs need an extra package downloaded on the first patching run — MetallibSupportPkg for Ivy Bridge, Haswell and NVIDIA Kepler on Sequoia, or the Kernel Debug Kit for AMD GCN cards on Ventura and newer. Patch over Wi-Fi and OCLP may install only the Wi-Fi driver on the first pass so you can get online, leaving you without graphics acceleration until you run patching a second time. A cable avoids the two-step dance entirely.

Every macOS update wipes your root patches. That is expected behaviour, not a fault. The tell is distinctive: the Mac feels dramatically slow and the Dock and menu bar lose their transparency. Open OCLP, run Post Install Root Patch, reboot.

Full detail on what root patching does per model — and which Macs get full acceleration versus which are permanently non-Metal — is in our supported Macs list.

Error strings, commands and menu paths on this page are compiled from the official Dortania troubleshooting documentation and reproduced exactly as published. We are an independent community resource and are not affiliated with Dortania or Apple. For the authoritative reference see the official documentation; if something here is out of date, let us know.