Worked for me even simpler way. It didnt want to restart (was not fully downloaded, not enough space). So I didn't even bother to remove xmls (folder was absent). Started upgrade, it started download. Cancelled download progress and tried root patch without reboot, it worked.
I couldn’t find the update files on Library so I did what you did and that saved my life. It did work like a charm!!!! After cancelling the download the macOS told me to “go to system configuration to authorise the update” so I just ignored that and click reboot button on the OpenCore popup.
Mine didn't have Wi-Fi at all, without Ethernet port, I had to use iPhone USB for internet to enable Upgrade so I cancelled progress as you did. Thank you vey much, have a good one.
This worked for me as well! But my WiFi also got disabled so I used my iPhone + USB to connect to the internet to begin and cancel the download. Then I was able to patch without restarting. I'm hoping that my system is mended now as I had a problem.
It worked for me - not exactly as described: Pressing Restart and interrupting the reboot didn't work but also didn't brick my system. Choosing Upgrade and powering off as the progress bar started did work and I was able to root patch my system. I didn't immediately trash the files, I just moved them to another disk on my system and trashed them after I was able to successfully install the root patches. Everything else proceeded as described by Mr. Macintosh. You, Mr. Macintosh, and the team are truly awesome! My system: [ 2.0 GHz Core i7 (I7-2635QM) Early 2011 Macbook Pro 8,2 MC721LL/A Model A1286 EMC 2353-1 Serial # C02FX375DF8Y ]
1. Untick all system updates options. 2. Perform a system upgrade but the progress is partially done, should be at beginning of progress. 3. Restart the machine immediately while the update is still in progress. 3. Force power off the machine by pressing a button. 4. Power it on back and apply the patch. This is the summary of the fix and so far, it worked for me.
I've had this situation twice now. I have missed the fact that with every OS update, the setting to allow/dis-allow automatic updates is reset back to automatic. Just upgraded 2 machines yesterday and was horrified to see those settings enabled again. My only way out of this has been to upgrade to whatever new update is out there (to get around the "downgrade' complaint) or wipe the drive and reinstall from scratch. Thank you for explaining and addressing the issue and affirming my sanity. Two 2012 machines are still alive thanks to you!
I thought my Macbook pro was f*ked when it did the Sonoma 14.7.1 update. I'm running Sonoma on an old 2015 that originally had Monterey and everything has been fine since I installed Sonoma months ago. I never turned off the automatic update so when it did with 14.7.1 everything got jacked up and my computer super lagged. I made the mistake of reverting the patch and it made it even worse. I couldn't put the patch back because of the mismatch error with and my wifi wouldn't connect. So I had to plug in my iphone to do a hard link for a hotspot, and pressed update for Sequoia, which I do not want. Once it started downloading, I tried to update the patcher again and it WORKED!!!! It rebooted the system well before Sequoia downloaded, and it seemed to fix everything since my Mac book is running normal again. THANK YOU SO MUCH!!! If I learned anything, it's to TURN OFF AUTOMATIC UPDATES!!!
Apple is not a friend of its clients, particularly “unsupported Macs”. I turned off Software updates including Security updates some time ago. I only have notifications on, the rest is firmly off and entirely at my own judgment. Thanks for the video and update 👍
Thank you well explained . Turn software updates off . Didn’t find the folders on Library . Just went on to the actual general software update . Clicked download , immediately rebooted my Mac and my Mac was up and running like a charm . Such a life saver . 🙌🏼👏🏻
Again, a great informative video. My first step before working with OCLP is to shut off automatic downloads and installation of updates. That should be step 1 before installing OCLP. Manually updating thereafter works very well with my collection of Mac’s.
Many thanks for your important information. My automated system update option is still disabled. This is always the first thing I double-check after installation. So in my opinion there is no action on my Mac machines necessary..
Thanks for this. Of the three devices I used OCLP to update to Monterey, I only needed to punt out the Sonoma update snapshot on one device. Followed the video and it worked without issue. Ran the OCLP patched root patches successfully when I finished.
2 дні тому
Luckily this method also worked for me, when 15.1.1 broke my iMac late 2012 running 14.7.1. Many thanks for your great work and dedication!
I was having this issue trying to patch when updating to OCLP 2.0 on my early 2011 MBP running the newest version of Monterey. Happy to report this worked perfectly and enabled me to patch my system on OCLP 2.0 this afternoon.
First time using opencore. Thank god i followed your exact video tutorial when 1.5 was released. You had a warning to make sure to uncheck auto download & update if you're on ventura.
Yes, disabling automatic updates is actually my routine and in my opinion best practice for actually ANY* device I own - as it is best to inform oneself before updating if there are caveats or problems with said updates - this is true for my phone, my computer, my router, my cars entertainment system for ANYTHING! And I know this is not for most normal users as they most probably would never update if automatic updates are deactivated, but I guess anybody watching this channel is a bit more educated about such decisions...;-) *but of course this s and always has been of utmost importance for any Hackintosh or patched Mac I used/owned!
Thank you so much for this video. You saved me! had this happen to me back in June 2024 I had automatic updates turned on! So, thanks to you, I turn updates off, and I was able to delete the upgrade folders , fail the upgrade and update Opencore. Whats weird is that This week I tried to update opencore, and it failed again!. I checked and my automatic updates are still turned off, but sure enough. I had an upgrade snapshot, and an upgrade folder in the system files. Thanks to this trick, I did it again, following your steps, upen core is running Patcher 2.1.0. Your are a genius!
I was trying to update my OCLP installation to 2.0.1 and ran into the SystemVerion.plist error. I used this video to resolve the issue. My MacPro 5,1 is on Monterey and I don't really feel comfortable upgrading past there. Monterey is very stable for me and runs all of the software that I need to use.
I ended up upgrading to Sonoma in Mac Mini 2012 i7. I didn’t want to but, after doing it, I can’t say I regret it as the systems seems to be more responsive and snappier.
I had three machines with the mismatch issue: 21" iMac 2009 running Monterey; I guess it hadn't downloaded the update yet because I clicked 'Update Now' and got a progress bar, which I immediately canceled. I was then able to run the root patch and the machine stayed at Monterey. 27" iMac 2012 running Ventura; When I clicked the 'Upgrade Now' button the machine immediately restarted. I was afraid to interrupt it, so unfortunately, I let it upgrade to Sonoma. Bummer. Headless Mac Pro 2013 running Ventura; I clicked the 'Upgrade Now' button and the machine restarted, so I forced a shut down, but when it did come back up, although it hadn't installed the upgrade, the mismatch was still there. I applied YOUR fix from this video, and that worked! Now I need to downgrade the 27" iMac 2012 since I prefer it to be running Ventura for certain software compatibility. I guess I am going to have to erase the drive to reinstall Ventura, but I'm concerned because my Time Machine backups didn't appear to be available on the 27" iMac, so I'm concerned that the Mac Pro isn't going to see its backups either.
Awesome , thank you for this fix. I waisted 2 hours trying to delete the update to root patch. Thank you, thank you. Yes it went exactly as described. Went very smooth and fixed the issue immediately. Just as you showed the file was gone after reboot and then patched flawlessly. Also I noticed the system booted to desktop much quicker as well. Thanks again
Worked for me too on Monterey 12.7.5 MacBookPro 9,2. The only difference was that when I chose upgrade that it started downloaded theSequoia files... I cancelled that, deleted the folders, emptied the trash and then rebooted. Firstly it came up with the different users, I selected and then held down the power once it stared loading. After that it was text book as per your video - thanks a lot!
Thanks for this - worked a treat for me... my issue was with the Developer Beta updates being staged - followed this and forced the beta update and OCLP was able to run the Root Patches fine I was already on 14.5 - (note for others.... it didn't ask me to re-boot once I forced the update, it just failed trying to re-download the update as I'd deleted the files and switched off automatic updates, I then re-ran the command line and the staged update was gone!)
Well, I had only partly success accoreding to your hint, with no any progres seen under Terminal. So I decided to install lacking newer update, which had coused the mismatch (between 14.6.1 and 14.7). Thank you for your help and knowladge.
THANK YOU FOR THIS VIDEO! I’m currently running Sonoma on all of my unsupported machines, recently installed over the past week or two as I just got into the Intel Macs (coming from Windows and STILL a loyal windows guy that’s the main selling point for me as well as checking out MacOS and seeing what I can do with it), ALL of my machines still had auto updates flipped on by default. Already went through the process of turning them all off on every machine before Sequoia drops and we have the exact same issue! THANK YOU SO MUCH!! 👏🏻👏🏻👍🏻
Thanks a lot. For me it works only "Starting the Update" and then press the power button to "kill" the Mac. After this reboot I was able to install new OC Root Patches. A normal reboot did not work. I tried it for several times. I have 13.6.4 (22G513) running on an MacBook Pro late 2016. Thanks again Mr. Macintosh 🙂
Mr Macintosh, you ROCK! Followed your instructions to the letter and they worked perfectly on my MacPro 5,1. Couple of notes: 1) I clicked UPGRADE SONOMA and held the POWER OFF button on the cheese grater when the progress bar began and continued to hold it, even when prompted by RESTART, SHUTDOWN dialogue box, and the machine shut down. POWERED ON and it booted up as you described. 2) When installing OCLP 1.5.0, the INSTALLING COMPONENTS dialogue box will churn for 90 seconds or more before the main 1.5.0 dialogue box appears. Installing ROOT PATCHES worked as you described. Thanks for your service!
iMac 13,2 running Ventura 13.6.7. It worked for me, thank you. I had to reapply the root patches a couple of times for them to update, but all good now! My fault for not disabling automatic downloads in the first place! Thanks for your hard work on this, and getting me out of the poop!
This was exactly the situation I found myself in on one of my Mac Mini 2012 machines. Followed the process step by step and it was fully resolved. Your instructions were absolutely perfect and my experience matched exactly everything you talked through. Thanks for your time and effort to help with this
Worked great - followed step by step. Needed to launch the update twice as the first time after forcing it off, it didn't roll back. Second time, no problem.
great video - i had a slightly different error message but your fix worked for me - my error message from OCLP was failed to find SystemVersion.plist and the root patcher aborted. After working your video it patched using OLCP 2.0.1
So it didn't work after reboot (my system boots to choice of disks by default). So after restart, I select the EFI partition first, and then go to the boot drive, and Restart doesn't suffice to start the installer process (and hence isn't interrupted by forced shutdown). So despite me interrupting the reboot with a manual power down, the Snapshot is still there after second reboot. After reading @derricksteed3466's comment, I chose 'Upgrade' from the System Settings instead of Restart. However, now the System Installer is downloading a brand new version of 14.6.1! Panic -- it's going to reboot automatically *and* have a downloaded version of the OS (= bricked Mac). So I opened a Word doc, left some changes unsaved, that should hopefully do enough to prevent automatic reboot. I waited for the upgrade to download and then deleted the upgrade installer files as System Update was 'Preparing system for update'. That caused it to abort (and, in the background, remove the Update Snapshot). Boom! OCLP is now able to install the latest patches! Thanks for this video and the helpful comments.
Thank goodness! This seems to be the only fix out there. It work perfectly although I had to dig deep into my media cabinet to get to the power button on my Late 2009 MacMini.
So: it worked - thank you very much for the information / instructions! I had to do the start update / interrupt twice - the first time, I think I interrupted too soon, in any case, the two supporting files were generated but the upgrade data was not - but I still had the nasty upgrade snapshot in the list. On my second attempt, everything was fine and the patches installed without a hitch!
Took me a few tries to get timing of powering off correct. Successfully got 2011 MacBook Pro running Monterey root patched with OpenCore 1.5.0. Thanks!
I have tried but did not work for me. I made the mistake of reverting the root patches and got stuck with no wireless and the mismatch error. I do not see any way out.
@@darthooshyk9857 I fixed the problem today. You need to connect your Mac via cable to your wifi and download a newer version of your operating system. After that you can install Open Core. Just reply if you need help :)
Hi Mr. Macintosh, I'm experiencing a similar issue, but in my case, I believe my system may have already been updated. I'm encountering a version mismatch: 23G93 vs 23F79. I attempted to install OCLP 1.5.0, but I'm not seeing any files downloaded, nor is there an option to upgrade. My current version reads as Mac Sonoma 14.5 (23F79), and that's where I'm stuck. I can't even boot properly; it only shows a black boot screen. I'm currently booting in safe mode.
You saved my system. It went exactly as you showed on my iMac 24-inch early 2009. I want to keep on Monterey but had automatically downloaded Sonoma 14.5. Thank you!
Thank you so much for your effort and your explenation. I use a MacMini 5.1 from 2011, and with your help I am back on Monterey 12.7.5, which I Need for my Music Production Software Cubase
Important note for Monterey users! You don’t need to reset for it to work! You can simply delete the files like shown in the video and select “Upgrade Now” the installation will fail and you will be able to install the root patches no problem
A bit of a complication but it still worked. Running Monterey. Mismatch was between Monterey and Sonoma. However, Software Update offered to install Sequoia. I kicked off the update to Sequoia and it began to download. I powered off as you say. When I restarted, the snapshot was gone. Root patching completed without error.
Great content! I am currently on Ventura 13.6.7, upgraded OpenCore Legacy patcher to 1.5 and unfortunately got the same issue you relate on the vídeo. I disabled the automatic upgrade on System Preferences, but there are no files on the Mac Software Update folder. The snapshot is showing on terminal and OpenCore is not patching. Do you have a suggestion on How I can delete the snapshot?
Important information: After deleting the files in the new 15.00 update notification, when we say install the update, it will start downloading the files again. Cancel it, just select the standard restart option and cut off the power at the apple logo. I did it this way on my 2012 MacBook Air, but it worked, even though I thought it wouldn't work.
I didn’t have this problem, but when I updated OpenCore to 1.4.3 my late 2015 21” 4K iMac (3.3 GHz i7, 16GB) running Ventura would hang at boot. I wasn’t trying to update the OS. It took wiping the drive and reinstalling Ventura from my USB thumb drive to get everything back from my TimeMachine backup. I’m still at OC 1.4.2. When 1.5 came out I decided to install that and also Sonoma. The problem I ran into there was at one point during the patching process, and before the video drivers were installed (which made just trying to move the cursor around painful), it wants you to launch system preferences and allow two extensions. But doing that also rebooted the Mac while the patcher was still patching. That left the system hanging on startup. So again I had to wipe the drive and reinstall Ventura and my TM backup. If I try it again I won’t click the reboot button in the system settings. But that will have to wait. I’m still currently at OC 1.4.2. The only weird thing that happens is every couple of weeks if I click on a modifier key, the left/right arrow keys, or a menu in an app, including the Finder, that app crashes. I then have to reboot. I’m thinking it’s a memory leak but I can’t see anything in the Activity Monitor.
Any help with this? Determining Required Patch set for Darwin 24 Pulling metallib list from MetallibSupportPkg API Direct match found for 24A348 (15.0.1) metallib already installed (15.0.1-24A348), skipping - Verifying whether Root Patching possible - Patcher is capable of patching - Mounted Universal-Binaries.dmg - Running sanity checks before patching - SystemVersion.plist build version mismatch: found 15.0 (24A335), expected 15.0.1 (24A348) An update is in progress on your machine and patching cannot continue until it is cancelled or finished - Unmounting root volume - Failed sanity checks, cannot continue with patching!!! - Please ensure that you do not have any updates pending
I have Ventura 13.6.6, and it's set not to auto update. How should I update to 13.6.7 to keep that setting intact, if that's even possible? Should I update through system settings or with a flash drive? If keeping the setting intact is not possible, which method would give me the most time to change the setting before the download is done?
You are a life savor. Thank you a lot. I followed your steps and it worked perfectly. but one question shall I disable all the fields in the automatic updates. because I am scared that this will happen again to me. I mean shall I turn off the 'check for updates' and the 'install security response and system files' or those two wont make any problems?
Hello All. New to OCLP but happy I found it. I have a simple question. Should I only use the installers through OCLP when upgrading my OS? Ie. Going from 15.0 to 15.1. Thank you!
Hi, I have looked at your videos and new to this but very experienced Mac user. I could not do a new install with OCLP 1.5 so I think I have misunderstood the process. Is 1.5 only an upgrade? If so which version do I install first? I have a MacBook Pro 10.1 Thanking you in anticipation, André in Sydney
Thanks for the video. My automatic downloads was set to on but there was no file in the Mac update folder. I assume all is well. System is running fine as usual and up to date.
Thank you it worked for one of my macbooks. But the other macbook I can only get in in safe mode and I don't seem to see the sequoia update in safe mode, so I can't get it started.
Hi I'm getting this version mismatch error: SystemVersion.plist build version mismatch: 22G720 vs 22G630 and this solution didn't work for me. I'm having troubles to even recognize my GPU, HMDI not working and such. please If anyone could help me I would much appreciate it
Yes, I just encountered this problem today on my iMac 15,1 running 13.6.7, and discovered that I was still running off the OCLP version 1.0.1! Still, it prompted me to update the installation to version 1.4.3 with its root patches, which worked just fine. And there I think I'll leave it for now. And I don't have any reason to run Sonoma at the moment, I'll await an OCLP update that fixes this incompatibility issue without me having to force an installation failure!
My 2011 iMac 27 had already staged this update and it was rebooted (fully and uninterrupted) before I knew about any of this. My device is still on 14.4.1, I deleted the staged files, rebooted and shutdown improperly however the snapshot still exists. I assume this is due to the previous complete reboot. Any tips in this situation?
I ended up sorting it out. I clicked update again, it downloaded and re-staged the install then followed this vode and I'm back in action. Auto download disabled.
LMFAO caught in the nick of time! I am a new user and just installed Ventura and low and behold I had a 4.5gb download in the Assets folder! You saved my behind cuz this was on an important machine 🙏🏼
I'm already on Sonoma, the upgrade worked perfectly with OCLP. However, as I wanted to install OCLP 2.01 to get ready for macOS Sequoia, the sanity check tells me that it found 14.6.1 instead of the expected 14.5 Does your tip work for that as well?
Mine wasn’t downloaded and staged. It just had the XML in the update folder along with the snapshot. Now after removing the XML and rebooted, it’s stuck on loading my profile after entering my password. Ugh hackintoshs are a pain
I have a mid 2010 imac running Monterey on OCLP. I had the problem with the root patcher but I followed your instructions and now I have been able to update my root patcher. Everything went well in the process, however, I still show an update for Sonoma on the update place. Is this something I should be concerned about? I did turn off auto updates a while ago, but it still is there, but not downloaded. Looking forward to your reply. 🙂
This happened to me on Sonoma, the machine became so sluggish and graphics were crap. The first time I had to re-install as could not go past the loading screen progress bar after trying to re-install post-install root patches. It happened again and When it was still loading to the desktop, risked it and upgraded via the automatic update. Luckily Opencore updated the patches on completion, have had the auto-download off ever since and keep opencore updated.
Cool, thanks for the fix. Also, as for the monterey-supported macs like my 2016 macbook pro, is there a way to fix the SkipLogo issue on native bootloader (like without using OCLP) ? It seems to happen on High Sierra and above. I didn’t have this issue on El Capitan or Sierra.
I am using OCLP 1.0.0 on a 2009 Macbook 6,1. I. upgraded to Monterey. After using the machine for a few weeks I updated OCLP to 1.5.0. I now get this mismatch and can't run root patches for video. I removed the macosupdate file and folder as you suggested, then my machine froze. I had to hard boot and I'm back to Monterey and I can't update root patch again. I clicked on "Upgrade Now" and then turned off machine as you suggest. It didn't work. I never got this mismatch error to fix.
Thank you so much for this. I checked the terminal app on my late 2011 13-inch MacBook Pro, and I think It's okay. I have a question, though. How do you check your root patches on OCLP? Do you have to reinstall the root patches to see them? I have zero tech skills, and I couldn't figure it out.
Worked for me even simpler way. It didnt want to restart (was not fully downloaded, not enough space). So I didn't even bother to remove xmls (folder was absent). Started upgrade, it started download. Cancelled download progress and tried root patch without reboot, it worked.
I couldn’t find the update files on Library so I did what you did and that saved my life. It did work like a charm!!!!
After cancelling the download the macOS told me to “go to system configuration to authorise the update” so I just ignored that and click reboot button on the OpenCore popup.
You saved my life 🙏🏼 thank youuuuuuuu
Mine didn't have Wi-Fi at all, without Ethernet port, I had to use iPhone USB for internet to enable Upgrade so I cancelled progress as you did. Thank you vey much, have a good one.
This worked for me as well! But my WiFi also got disabled so I used my iPhone + USB to connect to the internet to begin and cancel the download. Then I was able to patch without restarting. I'm hoping that my system is mended now as I had a problem.
Thanks a lot my friend. My mac is running fine again following your advice
It worked for me - not exactly as described:
Pressing Restart and interrupting the reboot didn't work but also didn't brick my system.
Choosing Upgrade and powering off as the progress bar started did work and I was able to root patch my system.
I didn't immediately trash the files, I just moved them to another disk on my system and trashed them after I was able to successfully install the root patches.
Everything else proceeded as described by Mr. Macintosh. You, Mr. Macintosh, and the team are truly awesome!
My system:
[ 2.0 GHz Core i7 (I7-2635QM) Early 2011 Macbook Pro 8,2 MC721LL/A Model A1286 EMC 2353-1 Serial # C02FX375DF8Y ]
1. Untick all system updates options.
2. Perform a system upgrade but the progress is partially done, should be at beginning of progress.
3. Restart the machine immediately while the update is still in progress.
3. Force power off the machine by pressing a button.
4. Power it on back and apply the patch.
This is the summary of the fix and so far, it worked for me.
I've had this situation twice now. I have missed the fact that with every OS update, the setting to allow/dis-allow automatic updates is reset back to automatic.
Just upgraded 2 machines yesterday and was horrified to see those settings enabled again.
My only way out of this has been to upgrade to whatever new update is out there (to get around the "downgrade' complaint) or wipe the drive and reinstall from scratch.
Thank you for explaining and addressing the issue and affirming my sanity.
Two 2012 machines are still alive thanks to you!
I thought my Macbook pro was f*ked when it did the Sonoma 14.7.1 update. I'm running Sonoma on an old 2015 that originally had Monterey and everything has been fine since I installed Sonoma months ago. I never turned off the automatic update so when it did with 14.7.1 everything got jacked up and my computer super lagged. I made the mistake of reverting the patch and it made it even worse. I couldn't put the patch back because of the mismatch error with and my wifi wouldn't connect. So I had to plug in my iphone to do a hard link for a hotspot, and pressed update for Sequoia, which I do not want. Once it started downloading, I tried to update the patcher again and it WORKED!!!! It rebooted the system well before Sequoia downloaded, and it seemed to fix everything since my Mac book is running normal again. THANK YOU SO MUCH!!! If I learned anything, it's to TURN OFF AUTOMATIC UPDATES!!!
Wow this worked! 🙌🏼 tried other methods with no luck. Thank you for helping me. This community is awesome
Sonoma 14.5 is working flawlessly on my 10yo 2014 macbook pro! thanks to mr mac and all OCLP true playas!
Apple is not a friend of its clients, particularly “unsupported Macs”. I turned off Software updates including Security updates some time ago. I only have notifications on, the rest is firmly off and entirely at my own judgment.
Thanks for the video and update 👍
Why tutn off security updates?
I don’t turn off Security update notifications, but as a precaution I prefer to click install security updates myself. It’s just me I guess 😊
@@trumphy911 I agree
Thank you well explained .
Turn software updates off . Didn’t find the folders on Library . Just went on to the actual general software update . Clicked download , immediately rebooted my Mac and my Mac was up and running like a charm .
Such a life saver . 🙌🏼👏🏻
Again, a great informative video. My first step before working with OCLP is to shut off automatic downloads and installation of updates. That should be step 1 before installing OCLP. Manually updating thereafter works very well with my collection of Mac’s.
Many thanks for your important information. My automated system update option is still disabled. This is always the first thing I double-check after installation. So in my opinion there is no action on my Mac machines necessary..
Thanks for this. Of the three devices I used OCLP to update to Monterey, I only needed to punt out the Sonoma update snapshot on one device. Followed the video and it worked without issue. Ran the OCLP patched root patches successfully when I finished.
Luckily this method also worked for me, when 15.1.1 broke my iMac late 2012 running 14.7.1. Many thanks for your great work and dedication!
I was having this issue trying to patch when updating to OCLP 2.0 on my early 2011 MBP running the newest version of Monterey. Happy to report this worked perfectly and enabled me to patch my system on OCLP 2.0 this afternoon.
First time using opencore. Thank god i followed your exact video tutorial when 1.5 was released. You had a warning to make sure to uncheck auto download & update if you're on ventura.
You have been telling us for months to remove automatic downloads. Thank you!!
So true
Yes, disabling automatic updates is actually my routine and in my opinion best practice for actually ANY* device I own - as it is best to inform oneself before updating if there are caveats or problems with said updates - this is true for my phone, my computer, my router, my cars entertainment system for ANYTHING! And I know this is not for most normal users as they most probably would never update if automatic updates are deactivated, but I guess anybody watching this channel is a bit more educated about such decisions...;-)
*but of course this s and always has been of utmost importance for any Hackintosh or patched Mac I used/owned!
@@m.l.9385hey thanks. What about “Install Security Responses and system files” should we deactivate them too?
Thank you so much for this video. You saved me! had this happen to me back in June 2024 I had automatic updates turned on! So, thanks to you, I turn updates off, and I was able to delete the upgrade folders , fail the upgrade and update Opencore.
Whats weird is that This week I tried to update opencore, and it failed again!. I checked and my automatic updates are still turned off, but sure enough. I had an upgrade snapshot, and an upgrade folder in the system files. Thanks to this trick, I did it again, following your steps, upen core is running Patcher 2.1.0. Your are a genius!
I was trying to update my OCLP installation to 2.0.1 and ran into the SystemVerion.plist error. I used this video to resolve the issue. My MacPro 5,1 is on Monterey and I don't really feel comfortable upgrading past there. Monterey is very stable for me and runs all of the software that I need to use.
I ended up upgrading to Sonoma in Mac Mini 2012 i7. I didn’t want to but, after doing it, I can’t say I regret it as the systems seems to be more responsive and snappier.
I had three machines with the mismatch issue:
21" iMac 2009 running Monterey; I guess it hadn't downloaded the update yet because I clicked 'Update Now' and got a progress bar, which I immediately canceled. I was then able to run the root patch and the machine stayed at Monterey.
27" iMac 2012 running Ventura; When I clicked the 'Upgrade Now' button the machine immediately restarted. I was afraid to interrupt it, so unfortunately, I let it upgrade to Sonoma. Bummer.
Headless Mac Pro 2013 running Ventura; I clicked the 'Upgrade Now' button and the machine restarted, so I forced a shut down, but when it did come back up, although it hadn't installed the upgrade, the mismatch was still there. I applied YOUR fix from this video, and that worked!
Now I need to downgrade the 27" iMac 2012 since I prefer it to be running Ventura for certain software compatibility. I guess I am going to have to erase the drive to reinstall Ventura, but I'm concerned because my Time Machine backups didn't appear to be available on the 27" iMac, so I'm concerned that the Mac Pro isn't going to see its backups either.
Awesome , thank you for this fix. I waisted 2 hours trying to delete the update to root patch. Thank you, thank you.
Yes it went exactly as described. Went very smooth and fixed the issue immediately. Just as you showed the file was gone after reboot and then patched flawlessly. Also I noticed the system booted to desktop much quicker as well. Thanks again
Thank you so much for sharing your knowledge. This trick works to revert to Somona for Sequoia. I had to do it twice but the result is here.
Worked for me too on Monterey 12.7.5 MacBookPro 9,2. The only difference was that when I chose upgrade that it started downloaded theSequoia files... I cancelled that, deleted the folders, emptied the trash and then rebooted. Firstly it came up with the different users, I selected and then held down the power once it stared loading. After that it was text book as per your video - thanks a lot!
Thanks for this - worked a treat for me... my issue was with the Developer Beta updates being staged - followed this and forced the beta update and OCLP was able to run the Root Patches fine I was already on 14.5 - (note for others.... it didn't ask me to re-boot once I forced the update, it just failed trying to re-download the update as I'd deleted the files and switched off automatic updates, I then re-ran the command line and the staged update was gone!)
Well, I had only partly success accoreding to your hint, with no any progres seen under Terminal. So I decided to install lacking newer update, which had coused the mismatch (between 14.6.1 and 14.7). Thank you for your help and knowladge.
THANK YOU FOR THIS VIDEO! I’m currently running Sonoma on all of my unsupported machines, recently installed over the past week or two as I just got into the Intel Macs (coming from Windows and STILL a loyal windows guy that’s the main selling point for me as well as checking out MacOS and seeing what I can do with it), ALL of my machines still had auto updates flipped on by default. Already went through the process of turning them all off on every machine before Sequoia drops and we have the exact same issue! THANK YOU SO MUCH!! 👏🏻👏🏻👍🏻
Thanks a lot. For me it works only "Starting the Update" and then press the power button to "kill" the Mac. After this reboot I was able to install new OC Root Patches. A normal reboot did not work. I tried it for several times. I have 13.6.4 (22G513) running on an MacBook Pro late 2016. Thanks again Mr. Macintosh 🙂
Mr Macintosh, you ROCK! Followed your instructions to the letter and they worked perfectly on my MacPro 5,1. Couple of notes: 1) I clicked UPGRADE SONOMA and held the POWER OFF button on the cheese grater when the progress bar began and continued to hold it, even when prompted by RESTART, SHUTDOWN dialogue box, and the machine shut down. POWERED ON and it booted up as you described. 2) When installing OCLP 1.5.0, the INSTALLING COMPONENTS dialogue box will churn for 90 seconds or more before the main 1.5.0 dialogue box appears. Installing ROOT PATCHES worked as you described. Thanks for your service!
iMac 13,2 running Ventura 13.6.7. It worked for me, thank you. I had to reapply the root patches a couple of times for them to update, but all good now! My fault for not disabling automatic downloads in the first place! Thanks for your hard work on this, and getting me out of the poop!
Many thanks. Saves me a little more storage and potential future headaches for my pathced systems. Keep up the good work.
This was exactly the situation I found myself in on one of my Mac Mini 2012 machines. Followed the process step by step and it was fully resolved. Your instructions were absolutely perfect and my experience matched exactly everything you talked through. Thanks for your time and effort to help with this
Worked great - followed step by step. Needed to launch the update twice as the first time after forcing it off, it didn't roll back. Second time, no problem.
great video - i had a slightly different error message but your fix worked for me - my error message from OCLP was failed to find SystemVersion.plist and the root patcher aborted. After working your video it patched using OLCP 2.0.1
Man you are a GENIUS, you just saved me hours of restoring my whole MacBook Air to factory settings, you saved my day! Thanks for everything!
So it didn't work after reboot (my system boots to choice of disks by default). So after restart, I select the EFI partition first, and then go to the boot drive, and Restart doesn't suffice to start the installer process (and hence isn't interrupted by forced shutdown). So despite me interrupting the reboot with a manual power down, the Snapshot is still there after second reboot. After reading @derricksteed3466's comment, I chose 'Upgrade' from the System Settings instead of Restart. However, now the System Installer is downloading a brand new version of 14.6.1! Panic -- it's going to reboot automatically *and* have a downloaded version of the OS (= bricked Mac). So I opened a Word doc, left some changes unsaved, that should hopefully do enough to prevent automatic reboot. I waited for the upgrade to download and then deleted the upgrade installer files as System Update was 'Preparing system for update'. That caused it to abort (and, in the background, remove the Update Snapshot). Boom! OCLP is now able to install the latest patches! Thanks for this video and the helpful comments.
Thank goodness! This seems to be the only fix out there. It work perfectly although I had to dig deep into my media cabinet to get to the power button on my Late 2009 MacMini.
Man i needed this a week ago. well, I did a fresh install. all is good. Thanks
Thanks Mr M - had the issue on my Macbook Air 7,2 running Ventura - followed your guide (after a TM backup) and all good now - huge relief
So: it worked - thank you very much for the information / instructions! I had to do the start update / interrupt twice - the first time, I think I interrupted too soon, in any case, the two supporting files were generated but the upgrade data was not - but I still had the nasty upgrade snapshot in the list. On my second attempt, everything was fine and the patches installed without a hitch!
This fix worked perfectly for me. MacBook Pro Mid 2014 Retina. OS Ventura 13.6.7. Thanks very much!
I followed these steps and corrected the issue I was having. 100% great job!
Took me a few tries to get timing of powering off correct. Successfully got 2011 MacBook Pro running Monterey root patched with OpenCore 1.5.0. Thanks!
Worked on 2 machines.
Did it exactly as in the video. Great fix.
I have tried but did not work for me. I made the mistake of reverting the root patches and got stuck with no wireless and the mismatch error. I do not see any way out.
Same problem here, can anybody help?
@@Oskar-t9t same probleme here plz help us
Did u find any way?
I thought about connecting a cable instead of using wifi but im not sure it that would work
@@darthooshyk9857 I fixed the problem today. You need to connect your Mac via cable to your wifi and download a newer version of your operating system. After that you can install Open Core. Just reply if you need help :)
Took 2 or 3 tries, but finally worked. Thanks.
THANK YOU! Worked exactly as the video instructions!!! I lived dangerously and did it without backing up, once again THANK YOU!
THANK YOU!!! 2011MBP fixed and working great again.
it's crazy 13 year old machine with the latest!
Works I didn’t understand the restart/power off part but did the same as the video and it worked
Thank you so much for this. I thought i was going crazy when trying to root patch. Very informative for Monterey
Hi Mr. Macintosh,
I'm experiencing a similar issue, but in my case, I believe my system may have already been updated. I'm encountering a version mismatch: 23G93 vs 23F79. I attempted to install OCLP 1.5.0, but I'm not seeing any files downloaded, nor is there an option to upgrade. My current version reads as Mac Sonoma 14.5 (23F79), and that's where I'm stuck. I can't even boot properly; it only shows a black boot screen.
I'm currently booting in safe mode.
Your instructions worked perfectly on my Late 2012 Mac mini Ventura. Many Thanks!
Yes it worked for me on my 5,1 Mac Pro now all fine again running Monterey 👍🙏
it worked! Thanks. I missed emptying the thrash and it failed so I did it a second time and worked. Was able to patch.
Awesome! It actually also worked on my MacBook Pro (Retina, 15-inch, Late 2013) running OpenCore MacOs Ventura. Thanks!
You saved my system. It went exactly as you showed on my iMac 24-inch early 2009. I want to keep on Monterey but had automatically downloaded Sonoma 14.5. Thank you!
This worked great on my late 203 iMac running Ventura. Went pretty much along the exact lines of your instructional video. Thank you!
Excellent. Worked well. Power down at the right was the only issue. Sorted. Thank you.
Thank you so much for your effort and your explenation. I use a MacMini 5.1 from 2011, and with your help I am back on Monterey 12.7.5, which I Need for my Music Production Software Cubase
Important note for Monterey users! You don’t need to reset for it to work! You can simply delete the files like shown in the video and select “Upgrade Now” the installation will fail and you will be able to install the root patches no problem
Thanks for this video. I am still on Ventura and have no immediate plans to upgrade to Sonoma or later, should I still download OCLP 1.5.0?
This worked for me on a white MacBook 2009 running Ventura after updating to Opencore1.5
Thanks for the fix
It worked on Sonoma on My Mac Mini 2014 after a few attempts!!!. Thank you
A bit of a complication but it still worked. Running Monterey. Mismatch was between Monterey and Sonoma. However, Software Update offered to install Sequoia. I kicked off the update to Sequoia and it began to download. I powered off as you say. When I restarted, the snapshot was gone. Root patching completed without error.
Great content! I am currently on Ventura 13.6.7, upgraded OpenCore Legacy patcher to 1.5 and unfortunately got the same issue you relate on the vídeo. I disabled the automatic upgrade on System Preferences, but there are no files on the Mac Software Update folder. The snapshot is showing on terminal and OpenCore is not patching. Do you have a suggestion on How I can delete the snapshot?
Important information: After deleting the files in the new 15.00 update notification, when we say install the update, it will start downloading the files again. Cancel it, just select the standard restart option and cut off the power at the apple logo. I did it this way on my 2012 MacBook Air, but it worked, even though I thought it wouldn't work.
Saved the day with this video brother! Worked like a charm!
I didn’t have this problem, but when I updated OpenCore to 1.4.3 my late 2015 21” 4K iMac (3.3 GHz i7, 16GB) running Ventura would hang at boot. I wasn’t trying to update the OS.
It took wiping the drive and reinstalling Ventura from my USB thumb drive to get everything back from my TimeMachine backup.
I’m still at OC 1.4.2.
When 1.5 came out I decided to install that and also Sonoma. The problem I ran into there was at one point during the patching process, and before the video drivers were installed (which made just trying to move the cursor around painful), it wants you to launch system preferences and allow two extensions. But doing that also rebooted the Mac while the patcher was still patching. That left the system hanging on startup. So again I had to wipe the drive and reinstall Ventura and my TM backup.
If I try it again I won’t click the reboot button in the system settings. But that will have to wait.
I’m still currently at OC 1.4.2.
The only weird thing that happens is every couple of weeks if I click on a modifier key, the left/right arrow keys, or a menu in an app, including the Finder, that app crashes. I then have to reboot. I’m thinking it’s a memory leak but I can’t see anything in the Activity Monitor.
This 100 percent fixed my issue with my 2017 MacBook Air. Thank you so much!
thanks youuu :) Your instructions worked perfectly on my Imac 2010 Ventura.
Worked like a charm on my Macbook pro mid 2012 with Ventura :) Thank you!!
Any help with this?
Determining Required Patch set for Darwin 24
Pulling metallib list from MetallibSupportPkg API
Direct match found for 24A348 (15.0.1)
metallib already installed (15.0.1-24A348), skipping
- Verifying whether Root Patching possible
- Patcher is capable of patching
- Mounted Universal-Binaries.dmg
- Running sanity checks before patching
- SystemVersion.plist build version mismatch: found 15.0 (24A335), expected 15.0.1 (24A348)
An update is in progress on your machine and patching cannot continue until it is cancelled or finished
- Unmounting root volume
- Failed sanity checks, cannot continue with patching!!!
- Please ensure that you do not have any updates pending
I have Ventura 13.6.6, and it's set not to auto update. How should I update to 13.6.7 to keep that setting intact, if that's even possible? Should I update through system settings or with a flash drive? If keeping the setting intact is not possible, which method would give me the most time to change the setting before the download is done?
I did it through system settings. No problem.
You are a life savor. Thank you a lot. I followed your steps and it worked perfectly. but one question shall I disable all the fields in the automatic updates. because I am scared that this will happen again to me. I mean shall I turn off the 'check for updates' and the 'install security response and system files' or those two wont make any problems?
helped me fix my 2013 imac, Took a couple tries but managed to get it done
This was a lifesaver thank for this video worked perfectly
Thank you, always here to help Mac Users ! 👌🏻
If only a .xml file exists in the above folder this solution doesn't appear to work, which is the case for my macpro5,1. Does anyone what else to do?
I had the same problem. I deleted the .xml file and started the update. It worked for me on my MacBook Air 7,2.
I’m really appreciate your videos, so detailed …Really you are doing a great job.
Thanks man 😊
Just keep it up…Love from India ❤
Hello All. New to OCLP but happy I found it. I have a simple question. Should I only use the installers through OCLP when upgrading my OS? Ie. Going from 15.0 to 15.1. Thank you!
Hi, I have looked at your videos and new to this but very experienced Mac user. I could not do a new install with OCLP 1.5 so I think I have misunderstood the process. Is 1.5 only an upgrade? If so which version do I install first? I have a MacBook Pro 10.1 Thanking you in anticipation, André in Sydney
Thanks for the video. My automatic downloads was set to on but there was no file in the Mac update folder. I assume all is well. System is running fine as usual and up to date.
Thank you it worked for one of my macbooks. But the other macbook I can only get in in safe mode and I don't seem to see the sequoia update in safe mode, so I can't get it started.
Hi I'm getting this version mismatch error: SystemVersion.plist build version mismatch: 22G720 vs 22G630 and this solution didn't work for me. I'm having troubles to even recognize my GPU, HMDI not working and such. please If anyone could help me I would much appreciate it
Thank you very much. This worked on my old imac 14.2 for Monterey 12.7.5
Thank you very much! That worked perfectly! Exactly how you described it. Thank you again.
Yes, I just encountered this problem today on my iMac 15,1 running 13.6.7, and discovered that I was still running off the OCLP version 1.0.1! Still, it prompted me to update the installation to version 1.4.3 with its root patches, which worked just fine. And there I think I'll leave it for now. And I don't have any reason to run Sonoma at the moment, I'll await an OCLP update that fixes this incompatibility issue without me having to force an installation failure!
Thank you so much! This fixed the problem for me!! 👏👏👏
This worked perfectly for me. Thank you Mr Macintosh 😊
My 2011 iMac 27 had already staged this update and it was rebooted (fully and uninterrupted) before I knew about any of this. My device is still on 14.4.1, I deleted the staged files, rebooted and shutdown improperly however the snapshot still exists. I assume this is due to the previous complete reboot. Any tips in this situation?
I ended up sorting it out. I clicked update again, it downloaded and re-staged the install then followed this vode and I'm back in action. Auto download disabled.
Worked four me. I have Sonoma installed and Sequoia was downloaded.
Thank you so much. This saved my installation - and thus my day
Thank you Mr Macintosh this worked perfectly for me.
LMFAO caught in the nick of time! I am a new user and just installed Ventura and low and behold I had a 4.5gb download in the Assets folder! You saved my behind cuz this was on an important machine 🙏🏼
Tried this on my 27” iMac. Didn’t work. After I switched off after deleting the assets and clicking update the prepared snapshot was still there.
Aha! I clicked to start the update again then cancelled out of the download. Update snapshot disappeared. Rebooting.
Seems to work. Phew!
I'm already on Sonoma, the upgrade worked perfectly with OCLP. However, as I wanted to install OCLP 2.01 to get ready for macOS Sequoia, the sanity check tells me that it found 14.6.1 instead of the expected 14.5
Does your tip work for that as well?
Mine wasn’t downloaded and staged. It just had the XML in the update folder along with the snapshot. Now after removing the XML and rebooted, it’s stuck on loading my profile after entering my password. Ugh hackintoshs are a pain
Same for me
I have a mid 2010 imac running Monterey on OCLP. I had the problem with the root patcher but I followed your instructions and now I have been able to update my root patcher. Everything went well in the process, however, I still show an update for Sonoma on the update place. Is this something I should be concerned about? I did turn off auto updates a while ago, but it still is there, but not downloaded. Looking forward to your reply. 🙂
This happened to me on Sonoma, the machine became so sluggish and graphics were crap. The first time I had to re-install as could not go past the loading screen progress bar after trying to re-install post-install root patches. It happened again and When it was still loading to the desktop, risked it and upgraded via the automatic update. Luckily Opencore updated the patches on completion, have had the auto-download off ever since and keep opencore updated.
Cool, thanks for the fix.
Also, as for the monterey-supported macs like my 2016 macbook pro, is there a way to fix the SkipLogo issue on native bootloader (like without using OCLP) ? It seems to happen on High Sierra and above. I didn’t have this issue on El Capitan or Sierra.
I am using OCLP 1.0.0 on a 2009 Macbook 6,1. I. upgraded to Monterey. After using the machine for a few weeks I updated OCLP to 1.5.0. I now get this mismatch and can't run root patches for video. I removed the macosupdate file and folder as you suggested, then my machine froze. I had to hard boot and I'm back to Monterey and I can't update root patch again. I clicked on "Upgrade Now" and then turned off machine as you suggest. It didn't work. I never got this mismatch error to fix.
Thank you so much for this. I checked the terminal app on my late 2011 13-inch MacBook Pro, and I think It's okay. I have a question, though. How do you check your root patches on OCLP? Do you have to reinstall the root patches to see them? I have zero tech skills, and I couldn't figure it out.