Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Monterey 12.6 up and running well on rMBP 10,1 mid 2012. It was an OTA full 11 GB update using sys prefs. The installer did a lot of auto-reboots, run time for the install was pretty long. OCLP auto-prompted to apply post install patches on login.

Also installed the Safari 16 OTA update. Silent Knight identified there was a newer version of XProtect available so I grabbed that from within Silent Knight. All good so far.
 
Last edited:
I have a A1278 / MacBookPro7,1 / Macbook Pro Mid 2010.
I installed 12.5.1 and i can’t fully disable sip. I’m using the Open Core Legacy Patcher, i opened it as admin and disabled sip from the app, when i restart i try to open an app (cDock) and it tells me to turn sip off. I ran cDock multiple times and i think it was after i used internet recovery mode (took like 5min) ran csrutil disable on it, and opened the app in admin mode but when i restarted it was the same issue.
is this happening for anyone else on monterey?
i just can’t seem to disable it.
 
Last edited:
I have a A1278 / MacBookPro7,1 / Macbook Pro Mid 2010.
I installed 12.5.1 and i can’t fully disable sip. I’m using the Open Core Legacy Patcher, i opened it as admin and disabled sip from the app, when i restart i try to open an app (cDock) and it tells me to turn sip off. I ran cDock multiple times and i think it was after i used internet recovery mode (took like 5min) ran csrutil disable on it, and opened the app in admin mode but when i restarted it was the same issue.
is this happening for anyone else on monterey?
i just can’t seem to disable it.
The problem isn't SIP, it is cDock. Look at the cDock home page, Monterey is not supported (support for up to and including Big Sur).
It is highly recommended to let OCLP determine the SIP settings, which will vary widely depending on the hardware.
Run OCLP, Build and Install, then write to disk. Then after a reboot, run OCLP again and try the Root patch, after installation, which is not required on newer hardware. I am fairly sure the volume root patches are required on that MBP 2010.
 
Last edited:
  • Like
Reactions: Ausdauersportler
The problem isn't SIP, it is cDock. Look at the cDock home page, Monterey is not supported (support for up to and including Big Sur).
It is highly recommended to let OCLP determine the SIP settings, which will vary widely depending on the hardware.
Run OCLP, Build and Install, then write to disk. Then after a reboot, run OCLP again and try the Root patch, after installation, which is not required on newer hardware. I am fairly sure the volume root patches are required on that MBP 2010.
I have always used settings to completely disable SIP. No problems.
 
Mac Mini 2012. Have latest OCLP 0.4.10 and post install patches installed, everything appears to be working fine except bluetooth. It's off, has a button to turn on, but nothing happens. Anyone know a fix? Thanks.
 
Mac Mini 2012. Have latest OCLP 0.4.10 and post install patches installed, everything appears to be working fine except bluetooth. It's off, has a button to turn on, but nothing happens. Anyone know a fix? Thanks.
Sometimes it needs one more restart.
 
Not settings, it is deeper in AFPS and the way the macOS system volume uses it (sealed), as far as I understand. It‘s the same with CCC which I use instead of SuperDuper.
CCC doc says the APFS replication utility ("ASR") won‘t copy the system volume alone and leave the data volume intact. CCC thus chose to make data-only clones normally, and erase left-over systems. SuperDuper may do the same.
So your procedure of installing with OCLP after cloning was quite right…
In CCC there is an option to clone both system and data, which makes sense if cloning to an empty drive.
Thanks for that. I'll give CC a try, then, with the system + data option. How are you on Ventura compatible CPU upgrades? I've already upgraded to a Xeon 5680, but have just learned that Intel processors since (I think) 2013 use pre-Haswell CPUs. The problem, evidently lies in Apple's use now of the AVX2 code instruction set on CPUs post-Haswell. (There are also Ventura probs associated with the GPU drivers, but AMD from RX400 on are compatible). Anyhow — will my board run a post-Haswell CPU, you think?
 
Intel processors since (I think) 2013 use pre-Haswell CPUs.
What exactly do you mean by "intel CPUs use pre-Haswell CPUs since 2013"? Up to when?

The problem, evidently lies in Apple's use now of the AVX2 code instruction set on CPUs post-Haswell. (There are also Ventura probs associated with the GPU drivers, but AMD from RX400 on are compatible).

It's not "post-Haswell". It's "Haswell and beyond". "Post" does not include the actual object.

Anyhow — will my board run a post-Haswell CPU, you think?
No.
 
I just updated macOS to version 12.6, via OTA, in my iMac 14,2 (late 2013)
with i7 CPU and nNvidia video card ("Kepler" series).
110% SUCCESS!
After rebooting, OpenCore Legacy Patcher asks me to install the Post Install Patch.
I agree, OCLP proceeds to patch the System and after the new reboot everything works perfectly.

macOS 12.6 iMac 14.2 & Kepler card.jpg

 
Last edited:
1. Installed the 11 GB update to 12.6 OTA (through the software update System preferences) on my MacBook Pro 11,3 which has the Nvidia Geforce card.
2. Came back a couple of hours later to a frozen startup screen with the startup "bar" halfway across.
3. Rebooted, same story.
4. Rebooted with shift key down (safe boot) and got a good reboot.
5. Started the OpenCore-Patcher.app and selected Post Install Root Patch.
6. Rebooted and now it is as before, running 2 external monitors so the Nvidia card (and everything else, apparently) is working.
7. Decided that the people who created this software are completely awesome.
 
Dear experts ! Tell me that there is a more correct option... upgrade or clean install ?
I always prefer to update and start from System Preferences; or I download the InstallAssistant.pkg, create the installation application and run it.
I always have, even the first time I went from Catalina directly to Monterey 12.1.
I used the USB Installer, however, only to remedy the problem caused by my nVidia “Kepler” series video card with macOS 12.5, before Khronokernel released the OCLP version with the new Post Install Patch. But in this case I had to do it to correct a mistake caused by me.
My iMac always goes to 110% and even if only once I installed everything from scratch, out of pure curiosity, I noticed that the Mac always goes the same way as the OTA installations: well and well and well
 
I always prefer to update and start from System Preferences; or I download the InstallAssistant.pkg, create the installation application and run it.
I always have, even the first time I went from Catalina directly to Monterey 12.1.
I used the USB Installer, however, only to remedy the problem caused by my nVidia “Kepler” series video card with macOS 12.5, before Khronokernel released the OCLP version with the new Post Install Patch. But in this case I had to do it to correct a mistake caused by me.
My iMac always goes to 110% and even if only once I installed everything from scratch, out of pure curiosity, I noticed that the Mac always goes the same way as the OTA installations: well and well and well
thanks !
 
  • Like
Reactions: OKonnel
Mac Mini 2012. Have latest OCLP 0.4.10 and post install patches installed, everything appears to be working fine except bluetooth. It's off, has a button to turn on, but nothing happens. Anyone know a fix? Thanks.
I seemed to have problems with bluetooth at first, causing severe slowdowns and device drops requiring a restart, updating my EFI to 429.0.0.0.0 appeared to solve the issue after a few tests..

Though I will say I am having a lot of slowdown with Safari 16.0 on this forum -- 100% CPU usage. :(
 
  • Like
Reactions: OKonnel
Though I will say I am having a lot of slowdown with Safari 16.0 on this forum -- 100% CPU usage. :(
I am good on a 2013 MacBook Air, updated OTA no problem. And yes, many thanks to all involved!

As for Safari 16, a while back I tried the pre-release version and was unable to close newly opened windows, or quit the app once it hung doing so.

Yesterday's release version fixed that but also hung on quit, and removed all of my pinned tabs...

Another restart resolved all of that. I have lately been thinking of moving away from Safari (I use FF and Chrome for different purposes, including when Safari just doesn't work) but still like Safari the best overall. Except when I don't ;-)
 
  • Like
Reactions: OKonnel
I am good on a 2013 MacBook Air, updated OTA no problem. And yes, many thanks to all involved!

As for Safari 16, a while back I tried the pre-release version and was unable to close newly opened windows, or quit the app once it hung doing so.

Yesterday's release version fixed that but also hung on quit, and removed all of my pinned tabs...

Another restart resolved all of that. I have lately been thinking of moving away from Safari (I use FF and Chrome for different purposes, including when Safari just doesn't work) but still like Safari the best overall. Except when I don't ;-)
I hear you. I'm getting the lovely banner "This webpage is using significant energy. Closing it may improve the responsiveness of your Mac" on EVERY tab (even though I only have two tabs open.) I've had eight tabs open on the previous Safari with no lag whatsoever.

Check this out. Typing this post takes about ten minutes because the typing appears one letter at a time very slowly.
Activity.png
 
  • Like
Reactions: OKonnel
I hear you. I'm getting the lovely banner "This webpage is using significant energy. Closing it may improve the responsiveness of your Mac" on EVERY tab (even though I only have two tabs open.) I've had eight tabs open on the previous Safari with no lag whatsoever.

Check this out. Typing this post takes about ten minutes because the typing appears one letter at a time very slowly.
View attachment 2060918
I'm not seeing any issues so far today. The "significant energy" error is common even on supported Macs. Long-time problem.
 
I am good on a 2013 MacBook Air, updated OTA no problem. And yes, many thanks to all involved!

As for Safari 16, a while back I tried the pre-release version and was unable to close newly opened windows, or quit the app once it hung doing so.

Yesterday's release version fixed that but also hung on quit, and removed all of my pinned tabs...

Another restart resolved all of that. I have lately been thinking of moving away from Safari (I use FF and Chrome for different purposes, including when Safari just doesn't work) but still like Safari the best overall. Except when I don't ;-)
All I can say is that I have reverted to my backups in 2 suported macs, Macbook Pro 16” I9 and Macbook 12” 2017, and an unsupported Mac Pro 5,1 after updating to Safari 16. It’s horrible.
 
All I can say is that I have reverted to my backups in 2 suported macs, Macbook Pro 16” I9 and Macbook 12” 2017, and an unsupported Mac Pro 5,1 after updating to Safari 16. It’s horrible.
See if the Technology Preview helps any. I had downloaded it during all of this and was about to migrate everything to it, but didn't. It was working better as far as closing windows though.
 
  • Like
Reactions: 0134168
Dear experts ! Tell me that there is a more correct option... upgrade or clean install ?
Just depends. I almost always try the upgrade first and rarely have problems. I've had macs that have been through 4 OS upgrades without re-installing with no problems. But sometimes there are problems. My vote is to be ready to reinstall if needed, but try the upgrade. How will you know if a fresh install is needed? If it feels too buggy or slow or other unexpected issues after the upgrade.
 
  • Like
Reactions: rehkram
Monterey 12.6 on an iMac 13,1 (late 2012) broke OCLP 0.4.10. Said there were some kexts missing. 12.5.1 works fantastic. I'd already moved back to 12.5.1 before I found this thread and I don't have the details. On a Mac Mini 6,2 it works great. Anyone else having issues with 12.6?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.