macOS 12 Monterey on Unsupported Macs Thread

[LordDeath]

I created a new APFS volume on my internal disk and installed Catalina on it. Unfortunately, my 2012 MacBook Air is still stuck with the old EFI version after installing the latest Catalina security updates. Do I really need to install Catalina on an external drive? I've read contradictory statements about this, which claim that the EFI updater only triggers with macOS installed on the internal drive.

 

[0134168]

I created a new APFS volume on my internal disk and installed Catalina on it. Unfortunately, my 2012 MacBook Air is still stuck with the old EFI version after installing the latest Catalina security updates. Do I really need to install Catalina on an external drive? I've read contradictory statements about this, which claim that the EFI updater only triggers with macOS installed on the internal drive.

You don´t even have to install nothing. Just boot from an USB installer. First thing it does is to update the firmware, if available. And you can cancel the installation after that.

 

[zfrogman]

Smooth update from 12.3. to 12.3.1, OCLP 0.4.3, and patch installs; very good performance of all apps. I also did an update FW to 426.0.0.0.0 from 425.0.0.0.0 on my MBP 2012 (9,1) via external drive partitioned for a Basic Catalina install with updated security updates that got me to 426.0.0.0.0. confirmed by Silent Knight. I tried the USB installer as suggested bt ******* but didn't update FW. Most likely human error on my part. I will try again on next FW update if any.

 

[Arnold2018]

In MS Word there is no transparency in selected area (only grey block). Any ideas how to solve the problem?

 

[makra]

In MS Word there is no transparency in selected area (only grey block). Any ideas how to solve the problem?

This means, your mac doesn't support metal graphics (pre 2012). The only solution for the time being is to install Word 16.49 (the most recent version that works).

Update history for Office for Mac - Office release notes

Provides IT Pros with information about the latest updates for Office for Mac, including links to download packages, and an update history

docs.microsoft.com

 

[Arnold2018]

This means, your mac doesn't support metal graphics (pre 2012). The only solution for the time being is to install Word 16.49 (the most recent version that works).

Update history for Office for Mac - Office release notes

Provides IT Pros with information about the latest updates for Office for Mac, including links to download packages, and an update history

docs.microsoft.com

Thank you. It is very strange, because on beta 12.3 it works properly.

 

[makra]

Thank you. It is very strange, because on beta 12.3 it works properly.

That's really strange, because these grey blocks had been around for months!

 

[Arnold2018]

That's really strange, because these grey blocks had been around for months!

Thank you! How about versions of iMovie and Keynotes?

 

[makra]

AFAIK:
iMovie 10.1.12
Keynote 10.0

 

[Arnold2018]

Thank you!

 

[xanderx007]

To be blunt, this is not for you.

You: one Mac only and can't afford down time
Most here: multiple macs and can experiment; skilled enough to recover if something borks

To be more blunt, No, it's for everyone here. You're not involved, and you're not helping, so don't involve yourself.

 

[xanderx007]

Well maybe, maybe not. Collectively we've assembled a lot of knowledge in these unsupported Mac threads. You could write a book on this whole topic, it's a way bigger topic than the forum thread format allows. Oftentimes, we're working our way through issues as they arise, as are the OCLP developers. Sometimes the intermediate fixes we come up with are not the eventual best solution.

Maybe we could develop a 'best practices' thread for people just getting into it. Or add it to post #1 of this thread. That would have helped me and many others when we started on this journey. 'Best practices' that come immediately to mind are:

• read this entire thread, that could take you days but do it anyway
• learn how to install macOS & OCLP on an external drive (SSD or USB pen drive)
• create a copy of your m/c's last supported macOS version on an external drive so you can get firmware updates, see previous discussions on this page
• install new versions of macOS on the external drive and test them before installing them on your internal drive
• don't install betas on your main internal SSD, only install public releases
• learn how to do a clean install, you can practice on an external drive
• do not expect everything to go smoothly. If it does, you're having a good day!
• contribute your experiences to this thread
• add your m/c and macOS version to your signature so others can help you easily
• helpful tools to have installed are gibMacOS & SilentKnight. Helpful websites are Mr. Macintosh, OCLP's Discord discussion group and https://dortania.github.io/OpenCore-Legacy-Patcher/
• have two backups handy

Bear in mind that in the past many issues have been fixed when a new version of OCLP drops; the war in Ukraine will slow that process down for the foreseeable future. Personally, I'm considering freezing my installation at this point (12.3.1)

Thank you for getting it. As this thread goes, a lot of information thrown in may or may not work for everyone, and one fix that worked before won't anymore the next time around (as with my 2011 dGPU, the hacks I did worked a few times, then one day do not). Some people seem to forget that these fixes do not work readily for all systems, regardless if they are of the same specs, as there are not a single straight-forward process when it comes to going beyond a simple OS install.

Even now, M1s that didn't come with Monterey are getting issues with Monterey installs.

If one <solution> fails, I move on to the next one as time allows.

 

[TimothyR734]

Maybe some might find this useful https://github.com/YuAo/MetalLibraryArchive

 

[ChrisOSX]

So I'm confused as to why I'm not receiving updates. I've reverted root patches, fully enabled SIP, restarted and it still won't see the 12.3.1 update. Thoughts? Thank you.


Weird bug I've just noticed. Trying to minimize Safari using the yellow button logs me out. This is with everything as mentioned above 🤷‍♂️

 

[mwidjaya]

it still won't see the 12.3.1 update. Thoughts? Thank you.

What is the spoofing level?

If I am not wrong, spoof-less at this point means you don't get updates - something about a bug with VM method of spoof-less.

Try setting to minimal spoofing and see if the update shows up.

 

[ChrisOSX]

What is the spoofing level?

If I am not wrong, spoof-less at this point means you don't get updates - something about a bug with VM method of spoof-less.

Try setting to minimal spoofing and see if the update shows up.

Never messed with the spoofing before, but I set to minimal, rebuilt and installed. Rebooted. Still nothing.

UPDATE: So I didn't change anything from last post. But it seems that i had to unenroll from the mac beta program in the software update screen. As soon as that went through I got the update.


Will report back.

Reporting back. So this is new 😂

 

[mwidjaya]

But it seems that i had to unenroll from the mac beta program in the software update screen. As soon as that went through I got the update.

You were on beta? And now you want to run latest public release?

Hmnn, have always thought you need to reinstall macOS going from beta to public release.

Could be wrong, someone else can comment on what works.

 

[ChrisOSX]

You were on beta? And now you want to run latest public release?

Hmnn, have always thought you need to reinstall macOS going from beta to public release.

Could be wrong, someone else can comment on what works.

I was in the beta program yes. I unenrolled, reverted all OCLP setting to default, minus showing picker.
Rebooted and now it’s processing the update now. Will report back once I go through the post install.

Maybe going from 12.3 RC to 12.3.1 is different?

UPDATE:
It appears we're all good here 👍

 

[hvds]

So I'm confused as to why I'm not receiving updates. I've reverted root patches, fully enabled SIP, restarted and it still won't see the 12.3.1 update. Thoughts? Thank you.
View attachment 1985201

Weird bug I've just noticed. Trying to minimize Safari using the yellow button logs me out. This is with everything as mentioned above 🤷‍♂️

just tried to reproduce this on my 12.3.1 installation, using OCLP 0.4.3 (default settings). But Safari behaved normally, no logout.

 

[ChrisOSX]

just tried to reproduce this on my 12.3.1 installation, using OCLP 0.4.3 (default settings). But Safari behaved normally, no logout.

Yah I dk it was weird. My only guess is it was because of the root patches not being enabled. on my non-metal machine, it gets super sluggish and borderline non-responsive. After its gtg.

Currently testing messages. opened it about 5 min ago with no crash.

 

[hvds]

I was in the beta program yes. I unenrolled, reverted all OCLP setting to default, minus showing picker.
Rebooted and now it’s processing the update now. Will report back once I go through the post install.

Maybe going from 12.3 RC to 12.3.1 is different?

UPDATE:
It appears we're all good here 👍
View attachment 1985255

Tried today to update from 12.3 release to 12.3.1 release on an external ssd with enrolment for betas. 12.3.1 did not show. Meanwhile updated to 12.3.1 from the InstallAssistant.pkg (to test also this).

Before, did the upgrade from 12.3 to 12.3.1 on the internal SSD which has no enrolment to betas, and there the 12.3.1 showed, so updated this OTA.

Both with OCLP 0.4.3, standard settings.

So this confirms your observation, but I don't remember it was like this with earlier updates.
Anyway - 12.3.1 runs very well, the best Monterey version for me so far.

 

[ChrisOSX]

Well, Messages finally crashed. Partial Report below. Don't know if any info should be kept to myself for a blind copy/paste.

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Messages [1822]
Path:                  /System/Applications/Messages.app/Contents/MacOS/Messages
Identifier:            com.apple.MobileSMS
Version:               14.0 (6000)
Build Info:            Messages_iosmac-1174080101001022~111
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               

Date/Time:             2022-04-02 08:49:23.8574 -0400
OS Version:            macOS 12.3.1 (21E258)
Report Version:        12
Anonymous UUID:       


Time Awake Since Boot: 2300 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGKILL)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace FRONTBOARD, Code 2343432205
<RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-create watchdog transgression: app<application.com.apple.MobileSMS.1152921500311914986.1152921500311914995(501)>:1822 exhausted real (wall clock) time allowance of 1199.95 seconds
ProcessVisibility: Foreground
ProcessState: Running
WatchdogEvent: scene-create
WatchdogVisibility: Foreground
WatchdogCPUStatistics: (
"Elapsed total CPU time (seconds): 1430.630 (user 822.250, system 608.380), 30% CPU",
"Elapsed application CPU time (seconds): 20.752, 0% CPU"
) reportType:CrashLog maxTerminationResistance:Interactive>

 

[macpro_mid2014]

Tried today to update from 12.3 release to 12.3.1 release on an external ssd with enrolment for betas. 12.3.1 did not show. Meanwhile updated to 12.3.1 from the InstallAssistant.pkg (to test also this).

Before, did the upgrade from 12.3 to 12.3.1 on the internal SSD which has no enrolment to betas, and there the 12.3.1 showed, so updated this OTA.

Both with OCLP 0.4.3, standard settings.

So this confirms your observation, but I don't remember it was like this with earlier updates.
Anyway - 12.3.1 runs very well, the best Monterey version for me so far.

Guys, this is also happening with iOS and WatchOS!

I have both my iPhone XR and Watch 6 enrolled in Public Betas. Neither iOS 15.4.1 nor Watch OS 8.5.1 are showing for me.

 

[K two]

Well, Messages finally crashed. Partial Report below. Don't know if any info should be kept to myself for a blind copy/paste.

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Messages [1822]
Path:                  /System/Applications/Messages.app/Contents/MacOS/Messages
Identifier:            com.apple.MobileSMS
Version:               14.0 (6000)
Build Info:            Messages_iosmac-1174080101001022~111
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:              

Date/Time:             2022-04-02 08:49:23.8574 -0400
OS Version:            macOS 12.3.1 (21E258)
Report Version:        12
Anonymous UUID:      


Time Awake Since Boot: 2300 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGKILL)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace FRONTBOARD, Code 2343432205
<RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-create watchdog transgression: app<application.com.apple.MobileSMS.1152921500311914986.1152921500311914995(501)>:1822 exhausted real (wall clock) time allowance of 1199.95 seconds
ProcessVisibility: Foreground
ProcessState: Running
WatchdogEvent: scene-create
WatchdogVisibility: Foreground
WatchdogCPUStatistics: (
"Elapsed total CPU time (seconds): 1430.630 (user 822.250, system 608.380), 30% CPU",
"Elapsed application CPU time (seconds): 20.752, 0% CPU"
) reportType:CrashLog maxTerminationResistance:Interactive>

The 1,200 second Catalyst crash is a feature built into OCLP043 for non-Metal Macs. Reverting to OCLP042 Offline variant, cold-boot bless is the temporary fix for now. OCLP developers see no fix for 043 in sight. Raising the issue on Discord not advised. They are well aware.

 

[K two]

OCLP_042ov atop 043, re-blessed. Messages 1 hour plus and it's still working. Confirmed on two machines.