macOS 12 Monterey on Unsupported Macs Thread

[rweed]

Can I install Monterey and any special drivers, etc. on an unsupported Mac on an external drive (USB 3.0...fast enough in my experience) without affecting the internal drive of said Mac such that I can boot off that internal drive to run the prior OS?
Just looking to try it out without doing any permanent damage
Thanks, Rick

 

[hwojtek]

Can I install Monterey and any special drivers, etc. on an unsupported Mac on an external drive (USB 3.0...fast enough in my experience) without affecting the internal drive of said Mac such that I can boot off that internal drive to run the prior OS?

Yes, just put OC on the EFI partition of the boot drive and use OC boot picker to manage your external booting. Or, if you don't use OC yet and have a native bootscreen-capable GPU, put the OC on the EFI partition of your external drive and use the native bootpicker to start from this disk, the OC on the external will be then used.

 

[KeithJohn]

Hi, I wonder if anyone can help me, I have a Mac Mini 6.1 and updated to OS 12.4 a few days ago, today I switched it on and when I open Itunes then try to minimize it my Mac freezes for a couple of minutes then unfreezes to the login screen, this didn't happen before the update, its getting frustrating having to login all the time.

Thanks guys in anticipation

 

[le9508]

Issue / change of behaviour on my MBA 2014 after updating to Monterey.

Old behaviour: closing the lid and leaving for several hours disconnected from power then opening the lid brought up the lock screen straight away (and then sign-in automatically via Apple Watch)

Monterey behaviour: closing the lid and leaving for several hours disconnected from power then opening lid does not wake laptop. Power button must be pushed which leads to boot drive picker (only main SSD as an option) - when selected goes to login in screen where password must be entered and then resumes from when lid was closed (so not a reboot - perhaps a hibernation)

My wife's MBA 2015 natively supports Monterey so didn't need patching and doesn't display this behaviour. This doesn't occur when plugged in and has persisted through updates since i first installed Monterey 12.2. Have I missed or checked an option somewhere in OCLP that is causing this?

My Late 2013 MacBook Pro 15” has the exact same issue when on battery! It does behave as expected though when plugged in, which might be what the other guy was talking about. Have you managed to find a fix?

 

[JCsHands2]

My Late 2013 MacBook Pro 15” has the exact same issue when on battery! It does behave as expected though when plugged in, which might be what the other guy was talking about. Have you managed to find a fix?

Same here on my Mid-2014. I thought it was just how things worked on OpenCore.

 

[KevinClark]

Does someone have issues with 12.4 and Martin Lo 080 opencore Macpro 2010 12 cores ? Thanks

 

[hvds]

Well, this is not precise. It does need an extra fix unless you have upgraded your BT/WiFi.

You are right. The Github changelog from 17 May, for the commits relevant to BT, says "Applicable for BCM2046 and BCM2070 chipsets" (others I guess were unaffected by the change Apple made in 12.4).

 

[dorninko]

Hi all, I installed 12.4 on several macbooks and iMacs using OCLP 0.4.5. all very easy and successful. But on my MacBooks I cannot install Parallels (version 16.0.1) anymore (was also not possible with 12.3). It works on an iMac 12,2.
right after I start the installation it crashes without much information.
Any ideas?

 

[Ausdauersportler]

Hi all, I installed 12.4 on several macbooks and iMacs using OCLP 0.4.5. all very easy and successful. But on my MacBooks I cannot install Parallels (version 16.0.1) anymore (was also not possible with 12.3). It works on an iMac 12,2.
right after I start the installation it crashes without much information.
Any ideas?

A hunch:
Reading the change logs of OCLP you might have noticed the SIP settings have changed, which (possible) made it more difficult for third party extensions to load during runtime. You might check this and revert to more generous settings, i.e. disable more SIP components.

 

[roysterdoyster]

MBP4,1 successfully updated to 12.5b1 via TUI-OCLP 0.4.6n.

 

[dorninko]

A hunch:
Reading the change logs of OCLP you might have noticed the SIP settings have changed, which (possible) made it more difficult for third party extensions to load during runtime. You might check this and revert to more generous settings, i.e. disable more SIP components.

Hallo Ausdauersportler,

I'm not so familiar with the SIP settings which ones do you think I should disable?

 

[dorninko]

Hi again, I disabled all SIP components but still no luck...

 

[Ausdauersportler]

Hi again, I disabled all SIP components but still no luck...

When you read the change logs you can see which ones have been raised (the ones with kext in the name).
Are you sure you rewrote OpenCore and rebooted or do you have just clicked the GUI?
If it is still not working it was a miss, sorry.

 

[dorninko]

When you read the change logs you can see which ones have been raised (the ones with kext in the name).
Are you sure you rewrote OpenCore and rebooted or do you have just clicked the GUI?
If it is still not working it was a miss, sorry.

I rewrote the OCLP and rebooted.
But thanks for the hint.
I also tried the newest version of parallels (Testversion), same problem...
Strange that it works on one iMac but non of my MacBooks...

 

[Macschrauber]

I had boot loop problems with 860 Evo and botched APFS on Mac Pro 5.1, oclp 0.4.5 and clean 12.4

after firmware updating the 860 evo and re-formatting and re-installing from createinstallmedia stick it was stable.

see https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-31111445

 

[macpro_mid2014]

I rewrote the OCLP and rebooted.
But thanks for the hint.
I also tried the newest version of parallels (Testversion), same problem...
Strange that it works on one iMac but non of my MacBooks...

Parallels latest version working here without a problem.
(Monterey 12.4/Parallels 17.1.2/SIP enabled (all switches)).
I don't have any root patch, though. Maybe, some Kext injected during the root patch is conflicting with Parallels System Extension causing the problem.

 

[dorninko]

Parallels latest version working here without a problem.
(Monterey 12.4/Parallels 17.1.2/SIP enabled (all switches)).
I don't have any root patch, though. Maybe, some Kext injected during the root patch is conflicting with Parallels System Extension causing the problem.

Thanks for the info, yes, maybe the iMac needs different Kext. The iMac has a metal graphic card, the MacBooks possibly don't (2010, 2011). Maybe that is the reason.

 

[headlessmike]

We all know this problem and the only way to get around (at least for me) this was a mix of this:

1. reinstalling using a newly created APFS container created by the disk utility version included into the (Monterey/Big Sur) installer
2. avoid at any cost booting into High Sierra (which is known to overwrite the Big Sur/Monterey PreBoot partition) while having the Big Sur/Monterey disk connected to the same system
3. avoid cross macOS updates, i.e. from Catalina to Big Sur and to Monterey when still facing this issue.
4. moving on to Monterey (clean installation, too)

The last installation I had with this particular problem was on an external test SSD possibly attached to too many different systems in too many different scenarios. Did the new (Big Sur latest) installation some days ago and since then (fingers crossed) the dying app phenomena went away. I deleted all High Sierra installations from all of my iMacs.

The other idea was disabling FeatureUnlock from your OC config manually, but this is/was a hunch, only.

I basically did all four steps that you mentioned and still get the error message on my late 2013 MacBook Pro. I’ve never seen it on my 2012 mini, so I wonder if there’s any correlation with model of Mac and the appearance on the mismatch.

 

[amishallin]

Works great with no issues updated OTA from 12.3.1.

 

[Ausdauersportler]

I basically did all four steps that you mentioned and still get the error message on my late 2013 MacBook Pro. I’ve never seen it on my 2012 mini, so I wonder if there’s any correlation with model of Mac and the appearance on the mismatch.

Unlikely, this last case I had was on an external SSD containing on Monterey installation (not affected) and one Big Sur installation (highly affected, could not even start system preferences and no third party app). The problems happend on all of my iMacs (iMac10,1, iMac11,1, iMac11,3, and iMac12,2).
Okay, one could claim all these models are affected. Unfortunately I not own a different unsupported Mac (model).

Should have kept the installation to investigate it on a rainy Sunday

 

[furdi]

Hi everyone, just finished updating OTA my MBP 9,2 mid 2012 non-retina to macOS Monterey 12.5 Beta 1 using OCPL 0.2.5 and everything works great! Have a great one!

 

[roysterdoyster]

Looks like some APFS file system extension problem (at least what´s reported). Root cause could be anything from
- memory instability (might be a timing issue that is not seen under 12.3)
- SSD/Trim problem (your special kind/brand of SSD behaving differently under 12.4 now?)
- incompatible system extension(s)

Grand thanks to you, @Larsvonhier : what brought my 12.4 an d 12.5b1 installation down to it's knees and led to permanent system crashes, was a third-party maintenance app. After removal, all is well with 12.5b1

 

[davidlv]

Grand thanks to you, @Larsvonhier : what brought my 12.4 an d 12.5b1 installation down to it's knees and led to permanent system crashes, was a third-party maintenance app. After removal, all is well with 12.5b1

Just for my personal info. what 3rd-party maintenance utility was that? Disk Warrior or something else that installed a kext file or agent?

 

[roysterdoyster]

Just for my personal info. what 3rd-@arty maintenance utility was that? Disk Warrior or something else that installed a kext file or agent?

I sent you a direct message / opened a conversation.

The app had 2 invisible daemons, these weren't removed by uninstall routine, had to search, find, remove them manually

 

[jgleigh]

Just for my personal info. what 3rd-party maintenance utility was that? Disk Warrior or something else that installed a kext file or agent?

DiskWarrior seems dead. They still don't fully support Big Sur (let alone Monterey). They don't support APFS. They don't support Apple Silicon. The promised update for Big Sur has been waiting for about 18 months now.

And Apple will be announcing macOS 13 this summer.