Here are some common errors that can occur when using this patcher:
- OpenCore Legacy Patcher does not start
- Stuck at This version of Mac OS X is not supported on this platform
- macOS won't boot without USB
- Boot into Infinite Recovery OS
- Restart when entering sleep mode (Sleep Wake Failure)
- Booting with a non-flash GPU
- How to boot Big Sur Recovery
- Stuck at "Your Mac needs a firmware update".
- No brightness control
- Wi-Fi in Monterey cannot be connected to legacy cards
- No graphics acceleration
- Black Screen on MacBookPro 11.3 in macOS Monterey
- No DisplayPort output on Mac Pros with NVIDIA Kepler
- Volume hash mismatch error on macOS Monterey
- SIP cannot be disabled in recoveryOS
- Stuck on "Less than a minute to go...".
- No Acceleration After a Metal GPU Switch on Mac Pro
#OpenCore Legacy Patcher does not start
If the application does not start (for example, the icon in the dock jumps), try starting OCLP from the terminal by typing the following command, make sure you have moved the application to
This version of Mac OS X is not supported on this platform
This means that macOS has detected an SMBIOS that it does not support. To fix this make sure to boot OpenCoreIn front ofthe macOS installer in the boot chooser. Reminder that the option is called
After starting OpenCore at least once, your hardware should now automatically start it until an NVRAM reset occurs or you remove the drive with OpenCore installed.
#macOS won't boot without USB
By default, the OpenCore patcher does not install OpenCore on its own internal drive during installation.transfer manually (opens a new window)Open Core on internal drive EFI or run option 2 of this patcher again and select your internal drive.
Keep in mind that once this is done you will need to re-select OpenCore in the boot selection so your hardware remembers that entry and automatically boots from there.
#Boot into Infinite Recovery OS
In OpenCore Legacy Patcher, we rely on Apple Secure Boot to ensure that OS updates work correctly and reliably with Big Sur. However, this installs NVRAM variables that will confuse your Mac if it's not running OpenCore. To fix this, simply uninstall OpenCore andreset NVRAM (opens new window).
- Note: Machines with modified root volumes will also result in an endless recovery loop until integrity is restored.
#Reboot when going into hibernation (
Known issue on some models (opens new window), a temporary solution is to disable hibernation by running the following command in the terminal:
sudo pmset -a hibernatemode 0
#Booting with a non-flash GPU
For Mac Pro, Xserve and iMac users with non-flash GPUs, you can still easily launch OpenCore and view the entire boot process. To do this, make sure SIP is disabled (to allow NVRAM write access) and run:
sudobless --verbose --file /Volumes/VOLNAME/EFI/OC/OpenCore.efi --folder /Volumes/VOLNAME/EFI/OC --setBoot
- Note 1: You need to replace
VOLNAMEwith the name of the volume of your USB or hard disk drive with OpenCore.
- Note 2: Once done, you can re-enable SIP.
- Note 3: The EFI partition where OpenCore was installed must be mounted. If it's not mounted, just run "Install OpenCore to drive" again.
As soon as you start OpenCore for the first time, LauncherOption installs itself as the top startup priority, which always starts OpenCore. Combined with
RequestBootVar, all boot options must pass through OpenCore, which ensures continued use even during operating system installation and upgrade.
#How to boot Big Sur Recovery
By default, the patcher tries to hide additional boot options, such as recovery, from the user. To view them, just press the button
space-barkey while in the OpenCore selector to list all boot options.
#Stuck at "Your Mac needs a firmware update".
Complete error: "Your Mac requires a firmware update to install on this volume. Please select a Mac OS Extended (Journaled) volume instead."
This error occurs when macOS detects that the current firmware does not have full APFS support. To fix this, go to "Patcher Settings" when installing OpenCore and enable "Moderate SMBIOS Patching" or higher. This ensures that the reported firmware supports the full capability of APFS.
#No brightness control
With OCLP v0.0.22 we added support for brightness control in many models. However, some users may have noticed that their brightness buttons are not working.
As a workaround, we recommend users to try the following app:
#Wi-Fi in Monterey cannot be connected to legacy cards
With OCLP v0.2.5, we added support for legacy Wi-Fi in Monterey. However, some users may have noticed that they are unable to connect to wireless networks.
To work around this, we recommend users to connect manually using the "Other" option in the Wi-Fi menu bar or manually add the network in the "Network" settings panel.
#No graphics acceleration
On macOS, GPU drivers are usually dropped with each major OS release. On macOS Big Sur, all non-metallic GPUs currently require additional patches to gain acceleration. Additionally, macOS Monterey removed graphics drivers for Intel Ivy Bridge and NVIDIA Kepler graphics processors.
If you are using OCLP v0.4.4, you should have been prompted to install root volume patches after installing macOS for the first time. If you need to do this manually, you can do it in the patcher app. After reboot, acceleration and brightness control for laptops will be re-enabled.
#Black Screen on MacBookPro 11.3 in macOS Monterey
Since Apple discontinued NVIDIA Kepler support in macOS Monterey,MacBookPro 11.3 GMUX is having trouble switching back to iGPU to display macOS properly. (opens new window)To work around this issue, boot your MacBookPro 11.3 in Safe Mode and, after installing macOS, run the OCLP post-installation root patches to enable GPU acceleration for NVIDIA dGPU.
- Safe mode can be started by holding
Prohibitedwhen selecting macOS Monterey from the OCLP boot menu.
#No DisplayPort output on Mac Pros with NVIDIA Kepler
If you have problems with DisplayPort output on Mac Pros, try enabling Minimal Spoofing in Preferences -> SMBIOS Settings and rebuild/install OpenCore. This will make the macOS drivers think you have a newer MacPro 7.1 and fix the problem.
#Volume hash mismatch error on macOS Monterey
A fairly common popup that some users face is the Volume Hash Mismatch error:
This error means that the operating system detects that the boot volume hash does not match what the operating system expects. This bug is usually cosmetic and can be ignored. However, if your system spontaneously crashes shortly afterwards, you should reinstall macOS without first importing any data.
- Please note that this error also affects native Macs and is not due to issues with unsupported Macs:OSX Daily: „Volume Hash Mismatch“-Fehler no MacOS Monterey (opens new window)
Also, it can be useful to disable FeatureUnlock in Settings -> Miscellaneous Settings, as this tool can be tiresome on systems with poorer memory stability.
#SIP cannot be disabled in recoveryOS
With OCLP, the patcher always overwrites the current SIP value on startup to ensure that users do not block an install after an NVRAM reset. However, for users who want to disable SIP entirely, this is easily possible.
Go to the GUI, go to Patcher Settings and toggle the bits you need to disable from SIP:
|SIP enabled||Reduced SIP (root patch)||SIP disabled|
For those who have issues with USB 1.1 devices (such as Bluetooth mice, keyboards, and chipsets): macOS Big Sur and newer have weakened OS-side reliability for the UHCI controller on older Mac Pros.
- UHCI is a USB 1.1 controller that plugs into your system's USB 2.0 ports. Whenever a USB 1.1 device is detected, the UHCI controller takes ownership of the device at the hardware/firmware level.
- EHCI is the USB 2.0 controller on older Mac Pros
For this reason, we recommend placing a USB 2.0/3.0 hub between your devices and the Mac Pro's port. UHCI and EHCI cannot be used at the same time, so when using a USB hub, the EHCI controller is always on.
- Alternatively, you can try to cold boot the hardware and see if macOS recognizes the UHCI controller correctly.
#Stuck on "Less than a minute to go...".
A common area for systems to "hang", i.e. units that do not have
AESLegacy CPU/Mobile Hardware instruction. A lot of heavy cryptography is performed during this phase, which can make systems appear to hang. In reality, they are working very hard to complete the installation.
As this step can take a few hours or more depending on the speed of the drive, be patient at this stage and do not manually shut down or restart your computer as this will interrupt the installation and require a reinstall. If you think your system is locked, press Caps Lock. If the light comes on, your system is busy.
If you've finished installing Monterey with the original card installed (to see the bootpicker, for example) and swapped your GPU for one supported by Metal, you might find that acceleration is lacking. To fix this, open OCLP and revert the root patches to get your metal-backed GPU working again.
Alternatively, you can remove AutoPkg-Assets.pkg from /Library/Packages on the USB drive before proceeding with the installation. To view the folder, enable hidden files with
This is because autopatcher assumes you are using the original graphics card and therefore performs non-metallic patching which involves removing some drivers for other cards. This causes metal cards to not accelerate after being swapped.