macOS 12 Monterey on Unsupported Macs Thread

[BeatCrazy]

You have to have a way to build a EFI. You could use a different computer, but OCLP should be run from the computer you want to install to so it knows what hardware it's dealing with. Actually, there's a setting to tell OCLP what Mac you want to build OpenCore for so it shouldn't matter what Mac you build it from.

If you don't have a Mac, then you would need to build the OpenCore EFI manually in Linux or Windows.

I have plenty of other Macs

I just wanted to see what is the 'cleanest' way to install Monterey on an unsupported model. As opposed to installing High Sierra (for example) and then Monterey on top, via OCLP. Seems like it would be better for a 100% fresh install of Monterey to a new SSD.

 

[johnsawyercjs]

Or log in to Safe Mode, download Beta 2 installer through OCLP and start it.

OCLP no longer lists Monterey 12.5 beta 2--only beta 3. The same is true of command line methods for accessing macOS installer downloads directly, unless there's a URL or method I don't know of (anyone know?). So if you didn't save a copy of the beta 2 installer, and you don't have a command-line method for downloading beta 2, one alternative is to downgrade to 12.4, which is the current release version of Monterey.

I'm seeing the same boot problem (hanging at the login window unless you boot into Safe Mode) as reported earlier by kennyz55, Tockman, MacRumors 3590, etc., after installing 12.5 beta 3 on my Late 2013 Macbook Pro 15 Inch (11,3), so I sure wish I'd saved my beta 2 installer, since prior to this, my Macbook ran fine with Monterey 12.5 beta 2. OpenCore Patcher 0.4.7 didn't fix this problem. I can boot 12.5 beta 3 on my Macbook in Safe Mode, but then I get a lot of little pauses and graphics glitches since there's no graphics acceleration for my NVIDIA Kepler GPU, and there's no sound.

Unfortunately when I try my own advice to downgrade to Monterey 12.4 (release), I can't because OpenCore Patcher, both 0.4.5 and 0.4.7, now complain when they try to install OpenCore to the installer USB flash drive (I tried four SanDisk 64GB flash drives, one of which was a different model from the other three, with the same result), displaying the same error that's been described by others here during the past week:

An error occurred!
0:188: execution error: Volume on disk0s1 failed to mount
If you think the volume is supported but damaged, try the "readOnly" option (1)

(where's this "readOnly" option?)

One of the SanDisk 64GB USB flash drives that I tried tonight, was the one I originally successfully used to install an earlier version of Monterey 12.5 beta (version 1?) about two or three weeks ago, so I don't know what's changed. I can't try my batch of non-SanDisk flash drives since they all contain either older installers for unsupported Macs, which I'd like to save, or backups of other items, so I guess I'll buy a different manufacturer's flash drive in the next couple days and see what happens. I'll probably try a PNY flash drive next, since that brand has worked properly for me in the past under a few circumstances where other manufacturers' flash drives didn't.

I even got the "failed to mount" error when I tried using OpenCore Patcher to create a bootable Monterey 12.4 installer on one of my SanDisk flash drives while my Macbook was booted from Big Sur 11.6.6, which I found on a 512GB USB flash drive which contains an older backup of my Macbook's internal Apple-original 500GB SSD, prior to my updating it to Monterey. Since OpenCore Patcher, on my MacBookPro11,3 can no longer write OpenCore builds to some USB flash drives that it previously worked with, even when the Mac is booted from Big Sur 11.6.6, does this mean 12.5 beta 3 changed something in the Macbook's firmware that's causing this problem with OpenCore Patcher? If so, I doubt if it was a deliberate move by Apple. I reset my Macbook's PRAM, NVRAM, and its SMC, and tried again to get OpenCore Patcher to write an OpenCore build to one of my USB installer flash drives, but once again OC Patcher reported "0:188: execution error: Volume on disk0s1 failed to mount".

Ausdauersportler reminded me earlier today, when I posted about this problem on the OpenCore Legacy Patcher channel at https://discord.com/channels/417165963327176704/835336708173463602, that we shouldn't be using OpenCore Patcher to install macOS betas on Macs that, if they don't boot after the installation, would be a problem. He said that each Monterey beta has thrown new challenges at the OCLP development team, and that if you want to try Monterey betas with OCLP, you should create a new container on your startup drive and install the beta onto it, instead of onto your main startup volume/container.

EDIT:
Ausdauersportler pointed out to me in the Discord channel that the "failed to mount" problem is seen when you use OpenCore Patcher while your Mac is booted into Safe Mode. OC Patcher has to mount, as writable, the EFI partition on the USB flash drive installer that it's creating, in order to be able to write the OpenCore build to it, but macOS won't mount this partition (at least as writable) when the Mac is booted in Safe Mode--as Ausdauersportler explains: "You cannot mount vFAT partitions in safe mode for security reasons. Apple blocked it."

I was mistaken in my description above in which I thought I was still seeing the "failed to mount" error in OC Patcher while my Macbook was booted in normal (not Safe) mode too--I was actually seeing a different problem, caused by mistakenly trying to use one of the Apple Silicon builds (21F2082) of Monterey 12.4 to make an installer USB flash drive--apparently you can't make an Apple Silicon installer using an Intel Macbook? Or at least an older one like mine.

 

[walterwhite1]

Successfully installed 12.4 on a 2011 Mac mini 5,1 thanks to OCLP 0.4.7. Thanks guys!

Just so I'm clear, there's no way to use/install OCLP + Monterey from a "completely erased" SSD right? You always have to have a base OS loaded so you can build a patched EFI root volume with OCLP?

I downloaded and built OpenCore on my mac mini 5,1 and saved to usb. Then when booting by usb ufi installer, I selected utilities and erased the disk. Then went back to menu and installed Monterey. It worked fine at that point in a blank ssd

 

[johnsawyercjs]

Didn't you try to boot into Safe Mode and turn Auto-login on?

My experience has been that whenever you boot into Safe Mode, you get the login window even if you've selected "Automatic login" in the Users & Groups prefpane. Does it work differently for you?

 

[Tockman]

He said that each Monterey beta has thrown new challenges at the development team, and that if you want to try Monterey betas with OCLP, you should create a new container on your startup drive and install the beta onto it, instead of onto your main startup volume/container.

That's right. Installing beta on your primary working machine is a big and (not always) conscious risk.

 

[Tockman]

My experience has been that whenever you boot into Safe Mode, you get the login window even if you've selected "Automatic login" in the Users & Groups prefpane. Does it work differently for you?

Yes, exactly. But in that case you enter your password, and all works well.
May be some other way in your situation because that is a model-depended bug.

 

[TOM1211]

Ausdauersportler pointed out to me earlier today, when I posted about this problem on the OpenCore Legacy Patcher channel at https://discord.com/channels/417165963327176704/835336708173463602, that we shouldn't be using OpenCore Patcher to install macOS betas on Macs that, if they don't boot after the installation, would be a problem. He said that each Monterey beta has thrown new challenges at the OCLP development team, and that if you want to try Monterey betas with OCLP, you should create a new container on your startup drive and install the beta onto it, instead of onto your main startup volume/container.

If you don’t know betas are a risk you shouldn’t be installing betas , when my Mac was new I would wait for a few weeks after official release before installing in case others reported problems there was a photos bug in one where some people lost photos I remember reading too much of a risk if your data is important. is the log in bug across all hardware or mostly earlier models? . I’m new to this with my Mac and was surprised OCLP provided any beta support when alot of developers keep there cards close to them awaiting official release . If it’s beta remember OCLP are seeing the release the same time as you expecting it to work out of the box would be pure luck more than anything especially as Apple moves more into its own Apple chipset.

 

[johnsawyercjs]

If you don’t know betas are a risk you shouldn’t be installing betas , when my Mac was new I would wait for a few weeks after official release before installing in case others reported problems there was a photos bug in one where some people lost photos I remember reading too much of a risk if your data is important. is the log in bug across all hardware or mostly earlier models? . I’m new to this with my Mac and was surprised OCLP provided any beta support when alot of developers keep there cards close to them awaiting official release . If it’s beta remember OCLP are seeing the release the same time as you expecting it to work out of the box would be pure luck more than anything especially as Apple moves more into its own Apple chipset.

Sure, I realized all that before I installed Monterey 12.5 beta 3, but I figured I'd "get lucky". Or just stay lucky, since my Macbook had run Monterey 12.5 betas 1 and 2 properly under OCLP 0.4.5 and 0.4.7. A few people are reporting here that their Mac models (different from mine) run Monterey 12.5 beta 3 properly under OCLP 0.4.5 and 0.4.7, so I was hoping I'd be in that privileged class.

 

[johnsawyercjs]

Interesting thing: though as I describe above, OpenCore Patcher is failing to write OpenCore builds to my USB flash drives after I use OpenCore Patcher to make them into Monterey installers, I was still able to boot my MacBookPro11,3 from the installer flash drive on which I had OpenCore Patcher install the Monterey 12.4 installer. I was then able to launch the Monterey 12.4 installer without any complaints from it about being run on an unsupported Mac, but when I tried to install 12.4 on top of 12.5 beta 3, a message appeared saying I couldn't downgrade. Oh well.

It's starting to look like I'll have to erase my Macbook's internal SSD before I can install 12.4 onto it, but I'm not sure a Monterey installer flash drive that's been only partly patched by OpenCore Patcher to allow it to work on an unsupported Mac, will complete the installation properly. If not, I might have to go back to Big Sur, which isn't a big deal, but I'd prefer to at least be able to run Monterey 12.4 on this Macbook.

Anyone know if it's possible to just wipe the System container, leaving the Data container intact, then install Monterey? Or will the Monterey installer want to see an entirely erased drive?

 

[chrickers]

I loved the TUI. I have read that you can compile it by yourself, but no idea how to do it.

"Developers can still compile TUIs from source,…!

Me too, but I don't know if it's worth to compile it myself… Too bad the TUI is discontinued.

 

[cab_007]

OCLP no longer lists Monterey 12.5 beta 2--only beta 3. The same is true of command line methods for accessing macOS installer downloads directly, unless there's a URL or method I don't know of (anyone know?). So if you didn't save a copy of the beta 2 installer, and you don't have a command-line method for downloading beta 2, one alternative is to downgrade to 12.4, which is the current release version of Monterey.

I'm seeing the same boot problem (hanging at the login window unless you boot into Safe Mode) as reported earlier by kennyz55, Tockman, MacRumors 3590, etc., after installing 12.5 beta 3 on my Late 2013 Macbook Pro 15 Inch (11,3), so I sure wish I'd saved my beta 2 installer, since prior to this, my Macbook ran fine with Monterey 12.5 beta 2. OpenCore Patcher 0.4.7 didn't fix this problem. I can boot 12.5 beta 3 on my Macbook in Safe Mode, but then I get a lot of little pauses and graphics glitches since there's no graphics acceleration for my NVIDIA Kepler GPU, and there's no sound.

Unfortunately when I try my own advice to downgrade to Monterey 12.4 (release), I can't because OpenCore Patcher, both 0.4.5 and 0.4.7, now complain when they try to install OpenCore to the installer USB flash drive (I tried four SanDisk 64GB flash drives, one of which was a different model from the other three, with the same result), displaying the same error that's been described by others here during the past week:

An error occurred!
0:188: execution error: Volume on disk0s1 failed to mount
If you think the volume is supported but damaged, try the "readOnly" option (1)

(where's this "readOnly" option?)

One of the SanDisk 64GB USB flash drives that I tried tonight, was the one I originally successfully used to install an earlier version of Monterey 12.5 beta (version 1?) about two or three weeks ago, so I don't know what's changed. I can't try my batch of non-SanDisk flash drives since they all contain either older installers for unsupported Macs, which I'd like to save, or backups of other items, so I guess I'll buy a different manufacturer's flash drive in the next couple days and see what happens. I'll probably try a PNY flash drive next, since that brand has worked properly for me in the past under a few circumstances where other manufacturers' flash drives didn't.

I even got the "failed to mount" error when I tried using OpenCore Patcher to create a bootable Monterey 12.4 installer on one of my SanDisk flash drives while my Macbook was booted from Big Sur 11.6.6, which I found on a 512GB USB flash drive which contains an older backup of my Macbook's internal Apple-original 500GB SSD, prior to my updating it to Monterey. Since OpenCore Patcher, on my MacBookPro11,3 can no longer write OpenCore builds to some USB flash drives that it previously worked with, even when the Mac is booted from Big Sur 11.6.6, does this mean 12.5 beta 3 changed something in the Macbook's firmware that's causing this problem with OpenCore Patcher? If so, I doubt if it was a deliberate move by Apple. I reset my Macbook's PRAM, NVRAM, and its SMC, and tried again to get OpenCore Patcher to write an OpenCore build to one of my USB installer flash drives, but once again OC Patcher reported "0:188: execution error: Volume on disk0s1 failed to mount".

Ausdauersportler reminded me earlier today, when I posted about this problem on the OpenCore Legacy Patcher channel at https://discord.com/channels/417165963327176704/835336708173463602, that we shouldn't be using OpenCore Patcher to install macOS betas on Macs that, if they don't boot after the installation, would be a problem. He said that each Monterey beta has thrown new challenges at the OCLP development team, and that if you want to try Monterey betas with OCLP, you should create a new container on your startup drive and install the beta onto it, instead of onto your main startup volume/container.

Have you tried erasing one of the flash drives and starting fresh install on it OCLP? I've encountered problems in the past with inability to mount when the drive was APFS format previously, could be something about it being protected and the only way to utilize it was to erase beforehand.

 

[cab_007]

I agree with the folks experiencing problems with 12.5 beta 3 (21G5046c), in addition to VMware Fusion having issues (even with new/fresh guests) and LS making it a challenge to log back in (I've had to remove LS manually from another instance). I fixed the LS issues by installing that first using default rules and building upon that and then reinstalling Fusion only to have Fusion still broken. I can attach the crash file but it would be probably be better suited for VMware discussion group. Fingers crossed the next beta resolves these issues as beta 2 and previous were more stable.

I did have issues on a earlier OSX beta that I encountered similar issues with Fusion not working, subsequent OSX beta resolved that.

 

[BeatCrazy]

I downloaded and built OpenCore on my mac mini 5,1 and saved to usb. Then when booting by usb ufi installer, I selected utilities and erased the disk. Then went back to menu and installed Monterey. It worked fine at that point in a blank ssd

Very helpful, thank you.

 

[webg3]

Interesting thing: though as I describe above, OpenCore Patcher is failing to write OpenCore builds to my USB flash drives after I use OpenCore Patcher to make them into Monterey installers, I was still able to boot my MacBookPro11,3 from the installer flash drive on which I had OpenCore Patcher install the Monterey 12.4 installer. I was then able to launch the Monterey 12.4 installer without any complaints from it about being run on an unsupported Mac, but when I tried to install 12.4 on top of 12.5 beta 3, a message appeared saying I couldn't downgrade. Oh well.

It's starting to look like I'll have to erase my Macbook's internal SSD before I can install 12.4 onto it, but I'm not sure a Monterey installer flash drive that's been only partly patched by OpenCore Patcher to allow it to work on an unsupported Mac, will complete the installation properly. If not, I might have to go back to Big Sur, which isn't a big deal, but I'd prefer to at least be able to run Monterey 12.4 on this Macbook.

Anyone know if it's possible to just wipe the System container, leaving the Data container intact, then install Monterey? Or will the Monterey installer want to see an entirely erased drive?

just create a new Cointainer (+) APFS and install 12.4, then copy your data then remove (-) 12.5 beta

 

[johnsawyercjs]

Have you tried erasing one of the flash drives and starting fresh install on it OCLP? I've encountered problems in the past with inability to mount when the drive was APFS format previously, could be something about it being protected and the only way to utilize it was to erase beforehand.

I did use Disk Utility to erase the flash drives, but it didn't make any difference whether I erased them as APFS or Mac OS Extended (Journaled), especially since OCLP erases the target installer flash drive as Mac OS Extended (Journaled) anyway. But the real cause of the "failed to mount" error reported by OCLP was, as Ausdauersportler points out, the fact that my Macbook was booted into Safe Mode while I was running OCLP, but for security reasons, Safe Mode doesn't allow the vFAT EFI partition on the installer flash drives to be mounted during the installer creation process. See my edited original comment.

 

[johnsawyercjs]

just create a new Container (+) APFS and install 12.4, then copy your data then remove (-) 12.5 beta

Thanks, I might try that. Creating the new container is done in Disk Utility, but using its option to create a new volume? I don't see an option to create a new container, and I thought "volume" and "container" aren't necessarily interchangeable terms.

 

[webg3]

Thanks, I might try that. Creating the new container is done in Disk Utility, but using its option to create a new volume? I don't see an option to create a new container, and I thought "volume" and "container" aren't necessarily interchangeable terms.

Disk Utility on USB Installer

 

[macpro_mid2014]

I loved the TUI. I have read that you can compile it by yourself, but no idea how to do it.

"Developers can still compile TUIs from source,…!

It is simple to compile it. You have to download the Source instead of the app. Unzip it and use the command
% ./Build-Binary.command --build_tui
From inside the unzipped folder. You have to have Python and some other dependencies installed. Python should install them for you, though. I am using Python3 from brew without any problem. I had some conflicts with Python in Xcode and Python in brew during my first try. I had to purge brew and reinstall it to have this fixed.

The OpenCore-Patcher.app is inside the newly created dist folder.

Spoiler: Build TUI Output

OpenCore-Legacy-Patcher-0.4.7 % ./Build-Binary.command --build_tui
- Starting build script
- Current Working Directory:
/Users/marcos/Downloads/OpenCore-Legacy-Patcher-0.4.7
- Starting preflight processes
* NOTE: home(brew) python3 detected; using (sys.exec_prefix, python_path) ==> ('/usr/local/opt/python@3.9/Frameworks/Python.framework/Versions/3.9', '/usr/local/opt/python@3.9/bin/python3.9')
- Deleting extra binaries...
- Downloading required resources...
- Downloading Universal-Binaries.zip...
- Moving into payloads
- Building TUI binary...
- Starting postflight processes
- Adding TUI launcher
- Patching LC_VERSION_MIN_MACOSX
- No commit data provided, adding source info
- Adding commit data to Info.plist
- Build script completed in 65.26 seconds

If you don't use the option --build_tui, the GUI version is compiled:

Spoiler: Build GUI Output

OpenCore-Legacy-Patcher-0.4.7 % ./Build-Binary.command
- Starting build script
- Current Working Directory:
/Users/marcos/Downloads/OpenCore-Legacy-Patcher-0.4.7
- Starting preflight processes
* NOTE: home(brew) python3 detected; using (sys.exec_prefix, python_path) ==> ('/usr/local/opt/python@3.9/Frameworks/Python.framework/Versions/3.9', '/usr/local/opt/python@3.9/bin/python3.9')
- Deleting extra binaries...
- Downloading required resources...
- Universal-Binaries.zip already exists, skipping download
- Generating DMG...
- DMG generation complete
- Found OpenCore-Patcher.app, removing...
- Building GUI binary...
- Starting postflight processes
- Patching LC_VERSION_MIN_MACOSX
- No commit data provided, adding source info
- Adding commit data to Info.plist
- Build script completed in 47.93 seconds

I have one suggestion for the GUI version, though:

The Set TeraScale 2 Accel is greyed out AND ticketed in the Developer Settings. After speaking with a developer, they explained that if it is greyed out, it means that it is not applied to my hardware. Unfortunately, this is not obvious. I thought that it meant "you need it so you cannot untick it", which does not make any sense because my hardware DOES NOT need the TeraScale 2 Kext. The same thing happens with Enhanced SSD Support.

So please, remove the tick on these two options. I understand now that they are not applied if greyed, but this conclusion is not obvious when someone sees it ticketed. It can mean exactly the opposite.

Thank you,

 

[0134168]

It is simple to compile it. You have to download the Source instead of the app. Unzip it and use the command
% ./Build-Binary.command --build_tui
From inside the unzipped folder. You have to have Python and some other dependencies installed. Python should install them for you, though. I am using Python3 from brew without any problem. I had some conflicts with Python in Xcode and Python in brew during my first try. I had to purge brew and reinstall it to have this fixed.

The OpenCore-Patcher.app is inside the newly created dist folder.

Spoiler: Build TUI Output

OpenCore-Legacy-Patcher-0.4.7 % ./Build-Binary.command --build_tui
- Starting build script
- Current Working Directory:
/Users/marcos/Downloads/OpenCore-Legacy-Patcher-0.4.7
- Starting preflight processes
* NOTE: home(brew) python3 detected; using (sys.exec_prefix, python_path) ==> ('/usr/local/opt/python@3.9/Frameworks/Python.framework/Versions/3.9', '/usr/local/opt/python@3.9/bin/python3.9')
- Deleting extra binaries...
- Downloading required resources...
- Downloading Universal-Binaries.zip...
- Moving into payloads
- Building TUI binary...
- Starting postflight processes
- Adding TUI launcher
- Patching LC_VERSION_MIN_MACOSX
- No commit data provided, adding source info
- Adding commit data to Info.plist
- Build script completed in 65.26 seconds

If you don't use the option --build_tui, the GUI version is compiled:

Spoiler: Build GUI Output

OpenCore-Legacy-Patcher-0.4.7 % ./Build-Binary.command
- Starting build script
- Current Working Directory:
/Users/marcos/Downloads/OpenCore-Legacy-Patcher-0.4.7
- Starting preflight processes
* NOTE: home(brew) python3 detected; using (sys.exec_prefix, python_path) ==> ('/usr/local/opt/python@3.9/Frameworks/Python.framework/Versions/3.9', '/usr/local/opt/python@3.9/bin/python3.9')
- Deleting extra binaries...
- Downloading required resources...
- Universal-Binaries.zip already exists, skipping download
- Generating DMG...
- DMG generation complete
- Found OpenCore-Patcher.app, removing...
- Building GUI binary...
- Starting postflight processes
- Patching LC_VERSION_MIN_MACOSX
- No commit data provided, adding source info
- Adding commit data to Info.plist
- Build script completed in 47.93 seconds

I have one suggestion for the GUI version, though:

The Set TeraScale 2 Accel is greyed out AND ticketed in the Developer Settings. After speaking with a developer, they explained that if it is greyed out, it means that it is not applied to my hardware. Unfortunately, this is not obvious. I thought that it meant "you need it so you cannot untick it", which does not make any sense because my hardware DOES NOT need the TeraScale 2 Kext. The same thing happens with Enhanced SSD Support.

So please, remove the tick on these two options. I understand now that they are not applied if greyed, but this conclusion is not obvious when someone sees it ticketed. It can mean exactly the opposite.

Thank you,

Thank you so much for your kind answer.

 

[davidlv]

OCLP no longer lists Monterey 12.5 beta 2--only beta 3. The same is true of command line methods for accessing macOS installer downloads directly, unless there's a URL or method I don't know of (anyone know?).

See this site, it has the b2 install pkg:

macOS 12 Monterey Full Installer Database. Download Directly from Apple!

Download macOS Monterey full installer with one click straight from Apple! Every version of Monterey Beta & Final available all in one place!!

mrmacintosh.com

 

[Tockman]

See this site, it has the b2 install pkg:

macOS 12 Monterey Full Installer Database. Download Directly from Apple!

Download macOS Monterey full installer with one click straight from Apple! Every version of Monterey Beta & Final available all in one place!!

mrmacintosh.com

I already gave John a link from there

 

[iMac-Oldschool]

Beta 3 on iMac 13.1 (21.5 inch, Late 2012).
Same problem with password loop as reported in posts #6493, #6494, $6511, #6514 and #6539.
Rebuilt the USB installer and reinstalled macOS on the external SSD. Password was accepted when system was rebooted into Beta 3. However, after applying the Post install Root Patch from OpenCore-Patcher version 0.4.7, the problem reappeared.
Beta software is only run on the external SSD, so other systems are not impacted

 

[rehkram]

Thanks for the screenshot, I have made a note to allocate 50 GB. Is your Monterey Install on your internal Aura Pro Drive, I assume when you know there is a firmware update you boot into the ExtSSD External Drive?

Monterey is on my internal drive, yes. As the others have said, the simplest way to know when the firmware needs updating is by installing and running SilentKnight, here's a link.

I never boot the external Catalina drive except to update Catalina to get new firmware. Running SilentKnight on the Monterey internal drive tells me when a firmware update is available.

Then I boot up Catalina on the external drive and install the update OTA. When done I power-off, reboot Monterey and run SilentKnight again to check firmware has updated. Once you get your head around it you'll find it works every time.

 

[borp99]

I managed to update my test partition of 12.5 from b2 to b3 on my cMP5,1 by using OCLP 0.4.8n (20 June build with USB1.1 update). Under the recently released 0.4.7, the installer hung consistently at early USB negotiation (for me, anyway).

Edit: Newer OCLP test builds are often found by reading through the Actions section of its Github page. I'm not advocating that anyone else use these as their regular bootloader...over the planned and well-tested OCLP releases. However, my many failed attempts to install beta 3, with 'verbose' messages showing, did all hang at the USB negotiation stage on my computer, so my feedback 'noise' (as chastised by another member below) was only well-intention-ed, in trying to help anyone else stuck in this situation eg. wasting frustrating amounts of time trying to test the next beta - to see if their unsupported hardware is still likely to run that next full final release. 12.4 is still my day-to-day operating system, but 12.5b3 (once installed and booted) is running extremely well for me.

 

[serafin79]

Can anyone recommend a replacement for iMovie, on a MBP8,1 and was using iMovie 10.1.12.
I'm on MacOS 10.4 and latest GitHub OCLP and it install but won't run when I click on it. says incompatible.

Thanks,