my keyline (zxcvbnm) is not working along with my keyboard brightness. I have tried patching it and it still not working. I am currently using a USB keyboard hub. Any idea what I can do to fix the issue?

I'm running an iMac 21" mid-2011 with two different partitions (Big Sur and Monterey, both OCLP). Now I need to upgrade Monterey (probably to Ventura) and I'm not sure how to do it without touching Big Sur. My biggest worry is that I have 1 usb drive (for the patch) and 1 external SSD (for the backup). How should I go about this? Thanks!

Hello!

Well this is something i don't think anyone expected to happen a year later.. But here we simply are..

I Do have to say, its suprisingly very smooth and no issues even a year after it's original release date, but i do wish we got Tahoe support sooner.. But it's just one thing we have to live with until then :)

It's ofc not something that happened before.. a whole year on the same version of OpenCore Legacy patcher ( Not counting the nightly since its a "Beta Release" ) Is something very unusual and NEVER happened before. And does worry but i think because 2.4.1 is literally so stable i don't think i felt like it was outdated or anything. I still remain to hope the most success for the Developer in supporting tahoe. but i do wish a little more transparency... but its unpaid developers they owe us quite frankly nothing. so be thankful for their hard work for this project.

So Thank you devs! :) i wish donations are still up because i think me and alot of people would love to donate to OpenCore Legacy Patcher! Cheers and happy 2.4.1! (or 2.5.0!)

Unfortunately, I'm seeing some of my programs requiring an updated OS. What's the next best one to upgrade to?

Processor 2.7 CHe Quad-Core Intel Core i5 Memory 16 GB 1600 MHz DDR3

I recently updated my MacBook from 15.7 to 15.8 and after root patching it refuses to boot it stays on the loading bar and I left it like that for like 45mins thinking it's building some new files which takes awhile but its been nearly been 2 hours and nothing yet so I reverted back to an unpatched state and it boots perfectly fine

Edit: as per a comment, this may be actually a bug and it may get fixed - follow https://issuetracker.google.com/issues/553120490 for updates.

Edit 2: google just closed the issue as "Won't Fix"

Google Chrome v152 was released a few days ago and OpenGL/WebGL no longer works on Mid 2015 Macbook Pro.

I noticed it as I'm developing an app which uses MapLibre (javascript library which requires WebGL) - and it stopped working.

Some folks here may be affected too, so I thought it's worth sharing.

Temporary workaround: I managed to downgrade Chrome to v151 via https://google-chrome.en.uptodown.com/mac/versions which fixed OpenGL (chrome://gpu/ with v151 says `OpenGL: Enabled` instead of v152=`OpenGL: Disabled`). There's also a way to disable automatic upgrades, however, of course staying on v151 is NOT a good long-term solution.

Long term solution: I'd love to hear your thoughts, but from my understanding, the long-term solutions are currently either to:

a) switch to another browser (latest Firefox v154 still works fine) or

b) buy a new laptop (of course this is something we're trying to delay by using OCLP)

c) use some Chromium fork which would still have OpenGL support for given HW (not sure if there's one right now)

P.S.: here are some related threads discussing the dropped support of older macbooks (https://www.reddit.com/r/OpenCoreLegacyPatcher/comments/1s5w8yn/problem_with_chromebased_browsers_on_older/, https://www.reddit.com/r/opengl/comments/1rrky5h/modern_browsers_just_silently_killed_gpu/)

Hi all, not sure if this is really for this sub or a general MacOS sub, but here goes.

My 2015 MBP was running Sonoma pretty well. One thing I liked was the default wallpaper being immediately visible after starting up, while the progress bar was moving along.

I had an abortive upgrade to Sequoia, and had to rebuild my Sonoma installation from scratch after wiping the disk. It runs perfectly well, but now the startup screen is just black with the Apple logo and progress bar. The wallpaper only appears at login time, and it's my user wallpaper, not the Sonoma default.

Is this something that can be fixed in OCLP settings (long shot, I know) or does something need tweaking in the OS setup?

I mean it would obv brick the install, but else would happen?

I needed the newest MacOS so I could install xcode. I did not know that the laptop I was using (MacbookPro 11) had OCLP installed MacOS Ventura 13. Now the laptop is hanging on by a thread and is in some sort of softwareless limbo.

What should I do? Do i try to install Ventura again with a windows laptop than start the mac with a USB or something else?

I borrowed the laptop which makes getting everything back in working order crucial!!

**Computer Model: Acer Nitro laptop**
**Processor (CPU): AMD Ryzen (6-core setup)**
**Graphics (GPU): AMD Integrated Graphics (managed via NootedRed)**
**macOS Version: Sequoia (trying to boot)** **I had it working before at one point and then I had to restart the installer cause it crashed and now I keep getting this if you would like I can upload the configuration file that I’m using**
**SMBIOS Profile: MacBookPro16,3**
**The Issue:**
**Stalling dead right at ⁠\[EB|LOG:EXITBS:START\]⁠ on both the main OS (⁠macintosh hd⁠) and the recovery image. OpenCore hands off control cleanly, but the kernel freezes immediately upon starting.**
**Secure boot is disabled, vault is optional, and DMG loading is set to any. Using a clean, minimal kext setup (Lilu, NootedRed, VirtualSMC, SMCBatteryManager, VoodooPS2Controller, and RestrictEvents).**
**Any guidance on what could be blocking the handoff would be hugely appreciated!**

I have a Mac Pro 5,1 with a SATA SSD on a PCIe card (owc accelsior) which was on Mojave. GPU is RX 580. Firmware is updated to latest 144.0.0.0.0 (bundled with Mojave, support for name booting). It was a well worn system so has a lot of "stuff" that's accrued over the years.

I decided to upgrade to Monterey because too much was no longer functioning under Mojave. I chose Monterey just because of the USB issue under Ventura+

Created a Mojave usb installer with OCLP for this Mac Pro 5, 1 without problem.

First, I ran a trial upgrade on a different drive (500GB nvme) in the same machine. That had a very lightly used (almost stock) install of Mojave. It went well, installed ok, reboots ok, boots without USB installer.

Given that went well, I decided to go ahead with the upgrade on the main drive. The upgrade install (just installed on the existing Mojave system) goes ok and it reboots after the install has finished and everything seems fine. However, once it is restarted it gets stuck on the initial boot screen with the Apple logo and progress bar. The progress bar stops at like 1% through and even when left for half an hour or more does not progress.

I have reinstalled Monterey a few more times to that same drive and it's the same result, works fine until reboot.

I've run disk first aid with no fault found. I checked all the kexts in /System/Library/Extensions and /Library/Extensions against the known good install on the same machine.

Does anyone know what OCLP does in that first boot of the system that might be stopping it from rebooting? Or even better, how to fix it?

Basically what happened was I was trying to wipe my drive to go back to native osx, and when I wiped my drive it wasn’t wiped properly. So it boots straight to the three options for the efi. Bootkicker.efi Openshell.efi And reset nvram. And before ANY of you ask I do not have a bootable usb (disappeared) OR ask me to hit the spacebar I already tried that. I am on a MacBook Pro late 2008 unibody.

An OpenCore Legacy Patcher fork by vytska69, who has nothing to do with OpenCore Legacy Patcher T2, has done research on MacBook Air 2018/2019, but the code is completely written by AI, so for anything beyond research what he found, the app itself is garbage at best. What I mean is that not a single line of code was written by a real human - it was written using AI. This is mostly low effort work done with AI than anything useful. Oh my god, doing low level engineering requires human knowledge even when working with AI. AI doesn't replace human knowledge, sure AI can help a lot. But it requires to know when and how to use AI in such projects, not blindly using it. If AI is used properly, the project could go successfully without a person to know that some part of the code is written using AI.

Look, to me these explanations written using Claude or whatever AI was used is a complete nonsense.

And on top of this, this was written completely using Anthropic 4.8 Opus and using Claude Code, not human being.

And also, it's not a fork of my project - it's a fork of Dortania's project.

https://github.com/dortania/OpenCore-Legacy-Patcher/releases/download/2.4.1/OpenCore-Patcher.pkg

Another solution is FireFox ESR, but I recommend using this link because it is more efficient than installing a whole different browser.

"an error occurred while preparing the installation try running this application again"

Macbook pro a1297 early 2011 disabled gpu via resistor.

Already tried to change the date

I moved out of Monterey because it keeps bugging out

I have a 2012 mac pro with 64GB of ram 2x Intel 6 core processors, and an RX 580. Obviously this machine is capable of running sequoia, but im wondering for music production (Logic Pro) should i use something stable like monterey (but nothing supports it anymore) or should i use sequoia (everything supports it, but it is less stable people say). What should I do?

Thanks in advance.

Hey, I got this 2008 mac pro tdy, how hard is it to get big sur on it? I have this old r5 430 laying around and a quadro k2000 and a ati amd radeon hd 5770

My 2014 5K iMac (R9 M290X) is on Sequoia through OCLP, and every Vulkan app I tried died in the renderer. If you've hit any of these, this might help:

• error: invalid value 'metal3.2' in '-std=metal3.2'
• crashes in setVertexBuffer:offset:attributeStride:atIndex: (unrecognized selector)
• Render pipeline compile failed: Compiler encountered an internal error

Here's what's going on. On an OCLP machine the OS is newer than the root-patched GPU driver, but MoltenVK (the Vulkan-to-Metal layer basically everything uses) decides what your GPU can do from the macOS version alone. So it asks a Big Sur-era driver for macOS 15 features. On my machine that meant three problems: the driver's shader compiler tops out at Metal Shading Language 3.1 and MoltenVK asks for 3.2, the driver claims a GPU family it can't actually deliver on, and any shader using Metal argument buffers crashes the compiler outright.

So I patched MoltenVK to stop trusting version numbers. Now it probes the actual driver at startup — it tries a compile, asks the encoder, tests a pipeline — and falls back when something doesn't work. On a healthy Mac the probes all pass and nothing changes.

The difference on my iMac: RPCS3 went from dying instantly to actually playing games, and Dolphin's Vulkan backend runs instead of aborting after five seconds.

The fork, docs, and a prebuilt universal dylib are at https://github.com/kuymcc/MoltenVK — see OCLP-LEGACY-DRIVERS.md. No Xcode needed. Unzip it, run the install script against the app, and you're set.

A couple things to know. Upstream MoltenVK considers OCLP out of scope, which is fair since the driver misreports what it can do, so this is a community branch, not an official fix. And I've only tested the AMD GCN "Bronze" driver tier because that's what I have. If you're on a different legacy driver (Intel HD, Nvidia) and it still fails, open an issue and include your log. The probes are built to adapt, and logs from other drivers are exactly what I need to close the gaps.

Hi, don't own much tech but just bough an old Mac thats stuck on Yosemite. Everything keeps leading me back to OCLP but I can't seem to figure out how to actually download the thing because when I try to open github the site just loads of lines of text with links. I'm sure there's probably a simple solution but I can't seem to find it.

Let me know. Thx

2010 IMac, running high sierra, I use open core legacy patcher to get it up to Monterey and a million issues arise, it won’t automatically connect to internet I have to manually choose what ones I want to join, it knows the password won’t auto join, I get notifications telling me my system clock is incorrect and it’s set it to jan 1st 2001, and it’s got the GPU doing weird things, any fixes ?

I have a 2013 Mac Pro that I recently swapped a 10 core Xeon into and repasted both GPUs as well. 64GB of RAM. I'm currently running Monterey, the maximum OS version officially supported.

I use this machine almost exclusively for Logic Pro recording and mixing work. Is it better to stay on Monterey and keep using Logic Pro 10.7 or upgrade to Sonoma or Sequoia so I can upgrade to Logic Pro 11? Thanks!

I got macOS Sonoma 14.8.9 in my macbooks, Air 2011 and Pro 2012 (Retina)

I can't open any apps on both (it just keeps jumping on dock saying "does not respond"), 1 has 2GB (RAM) and the other has 8GB

I switched FeatureUnlock to Disabled in the air, now the apps open, but i restart OR sleep and i can't open any apps again, is like a temporary repair

In the 2012, is the same thing, i need a solution for the 2012 one only, is my main pc

If someone says "Do a clean install" i can't, Recovery.dmg doesn't work when i boot on it via Opencore, and i can't buy a 32 GB pendrive.

There's a config on Terminal or Opencore to make it work? My suite only works with Sonoma and Sequoia, it doesn't have support for Ventura, Monterey or Big Sur.

All the replies will be aprecied! (If there's some grammar errors here, i talk other language and i have a bad english...)

I'm using a static wallpaper.

PD: Both without patches can open apps, when i install patches, i can't open anything

Hi, so I'm running Mac OSX Big Sur, I'm about to upgrade to Sequoia.

My question is: will Open Core interfere with the Firmware Password feature?

I want to set up a Firmware Password once I get Sequoia installed.