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.
The instructions are the same.


When does this message appear? The guide describes a dism install, so if you can get to the command prompt, then the installer is effectively bypassed, and there is simply no opportunity for that message to appear. Perhaps your installer is different from the one in my tests. In that case, post #10,042 may be helpful.
Unfortunately I've already tried the suggestion in post #10,042 but without any success!
Maybe the last hope then is to do the upgrade from Windows 10 as described in post #63 of the thread "Bare Metal Windows on cMP".
Thanks!
 
Sorry but I have followed all the instructions in the section called Appendix but I can't find the solution and details on how to install Windows 11!
With Windows 10 no problem, but when I try to install the Windows 11 the installer shows this message "...it is not possible to install this version of Windows on this computer".
Thanks in advance for your help!

Dude.... Did you read my damn post to you or not?

I provided a direct link to a guide on how to do it (which is the same one that I followed).

You are getting that error because you did not disable TPM.

Maybe he has me on ignore (for whatever reason) ?

Let's not derail the thread now.
 
I just changed my boot drive to my new Samsung 970 Eco Plus - all good.
Updated MacOS to 12.2 and OpenCore via OCLP 4.1

Now I notice that the boot process gets stuck for about 15 seconds on

AMFIInitializeLocalSigningPublicKey: Failed to get Local Signing Public Key (e00002bc)

Then continues booting as normal

I look through the forums and it might be related to latebloom but....

Anyone else noticed this or got any thought as to the issue

Cheers

**** UPDATE **** It seems Bootroot might be the reason why its slow to boot

IMG_4622.jpeg
 
Last edited:
Dude.... Did you read my damn post to you or not?

I provided a direct link to a guide on how to do it (which is the same one that I followed).

You are getting that error because you did not disable TPM.

Maybe he has me on ignore (for whatever reason) ?

Let's not derail the thread now.
Of course I read your post #63 of the thread "Bare Metal Windows on cMP"!
I followed your instructions step by step but when I start installing Windows 11 to update Windows 10 at some point (as you see from the attached image) the installation system replies that:
1) The processor is not supported for this version of Windows
2) The PC must support TPM 2.0
3) The PC must support Secure Boot.

Could you give me more details of the procedure of each step?
Thanks for your help!

Installer from MCT.PNG
 
Of course I read your post #63 of the thread "Bare Metal Windows on cMP"!
I followed your instructions step by step but when I start installing Windows 11 to update Windows 10 at some point (as you see from the attached image) the installation system replies that:
1) The processor is not supported for this version of Windows
2) The PC must support TPM 2.0
3) The PC must support Secure Boot.

Could you give me more details of the procedure of each step?
Thanks for your help!

View attachment 1951302
You need to disable TPM while still in Windows 10, then go to update to install Windows 11.
 
  • Like
Reactions: NC12
Registry tweak, that you describe - is not workable in that case, to update win10 to win11 - you need a script "Universal Media Creation Tool" to disable TPM check.
I'm not going to argue with you in this thread and change the subjet from OpenCore to Windows....

If you want to read the instructions I gave to him (which includes MCT), follow the links I posted to him above.

I am going to try helping @DigitaLife get Windows 11 on his cMP via PM.

Back to OpenCore topic.
 
Last edited:
Trying to do a OTA upgrade from 12.01 > 12.2 on my 4,1/5,1 and the upgrade is not showing up in SW update - says I am up to date. I’m running Martin’s 0.7.7 package. I thought maybe VMM flag. I checked config (default package) and it looks like it was set to on which I thought was odd unless something has changed. I set it to off and still can’t get an upgrade. It seems like others have done the OTA upgrade without issue. I could just go from the full installer I guess. Any tips or Info would be much appreciated!
 
Trying to do a OTA upgrade from 12.01 > 12.2 on my 4,1/5,1 and the upgrade is not showing up in SW update - says I am up to date. I’m running Martin’s 0.7.7 package. I thought maybe VMM flag. I checked config (default package) and it looks like it was set to on which I thought was odd unless something has changed. I set it to off and still can’t get an upgrade. It seems like others have done the OTA upgrade without issue. I could just go from the full installer I guess. Any tips or Info would be much appreciated!
If you don't mind digging into your config.plist read the "macOS" section of the 1st post of the thread. It shows what settings you need to successfully do an OTA upgrade.
 
Trying to do a OTA upgrade from 12.01 > 12.2 on my 4,1/5,1 and the upgrade is not showing up in SW update - says I am up to date. I’m running Martin’s 0.7.7 package. I thought maybe VMM flag. I checked config (default package) and it looks like it was set to on which I thought was odd unless something has changed. I set it to off and still can’t get an upgrade. It seems like others have done the OTA upgrade without issue. I could just go from the full installer I guess. Any tips or Info would be much appreciated!

Martin's package is not setup for OTA upgrades. Also FYI - please note VMM flag is NOT turned ON by default in Martin's package. Follow Martin's instructions as to how to perform macOS updates/upgrades, he has a video that walks you step by step through the process plus additional comments in the readme file within his package folder. If you'd like to have OTA upgrades, you could 1) modify Martin's package (it would be a more advanced process, doable as long as you are/become familiar with the config file and OC in general) or 2) start from scratch and follow @cdf guide in the first post of this thread (also a more advanced process and the best way to learn about OC in general). If you decide to follow the guide on this thread (post #1), please note you will end up replacing Martin's package. Lastly, Martin has a thread for his package as you know, and you can ask questions there that pertain to his package and/or instructions. This thread is focused on post #1.
 
If you don't mind digging into your config.plist read the "macOS" section of the 1st post of the thread. It shows what settings you need to successfully do an OTA upgrade.
Yup that was it. Been awhile since I did an upgrade. FYI Option 2 did it for me.

Also FYI - please note VMM flag is NOT turned ON by default in Martin's package.
That's what I remember previously. I may be reading it incorrectly but it looks to me like it is on in the current release. Maybe I'm missing something. Apologies I always get lost in these two threads... Will post over there. Thanks.
 
  • Like
Reactions: NC12
When using Lilu with recent versions of macOS, board-id should be present in IODeviceTree:/efi/platform. We can fix this by setting DataHub>BoardProduct to Mac-27AD2F918AE68F61 (being consistent with the config detailed in the first post) and UpdateDataHub to true. Note that because we are not overriding the Data Hub protocol, all existing OEM values remain fixed, so spoofing is still effectively kept to a minimum.

Just catching up with this, thank you. Applied here and I'll keep an eye on things, see if the issue is resolved.
 
  • Like
Reactions: NC12
I just changed my boot drive to my new Samsung 970 Eco Plus - all good.
Updated MacOS to 12.2 and OpenCore via OCLP 4.1

Now I notice that the boot process gets stuck for about 15 seconds on

AMFIInitializeLocalSigningPublicKey: Failed to get Local Signing Public Key (e00002bc)

Then continues booting as normal

I look through the forums and it might be related to latebloom but....

Anyone else noticed this or got any thought as to the issue

Cheers

**** UPDATE **** It seems Bootroot might be the reason why its slow to boot

View attachment 1951443
Hi guys,

Anyone know why bootroot will be slowing down my boot. Stops for about 10-15 seconds then continue as normal

Any insight greatly appreciated
 
  • Like
Reactions: NC12
I'm experienceing some weird mouse behavior, dropping windows while dragging, for example.

Anyone have any thoughts on what might be behind it? Opencore on Big Sur and Opencore on Catalina both have the same behavior.
 
I'm experienceing some weird mouse behavior, dropping windows while dragging, for example.

Anyone have any thoughts on what might be behind it? Opencore on Big Sur and Opencore on Catalina both have the same behavior.
Is your mouse wireless and how old is it?
 
Is your mouse wireless and how old is it?
Brand-new Logitech G502.

This problem has gone on for ages. I initially thought it was to do with the USB extension cable I was using, so I replaced the cable with an active extender, then replaced the mouse, figured out a plist setting that was causing the computer to crash periodically, before finally admitting defeat.

I recently built a second Mac on Catalina because I also have an unrelated crash issue which I thought Catalina might solve, but it too suffers from the senile mouse issue, hence the question.
 
cMP with RX580, fresh install of Mojave onto SSD in bay 1. I’ve followed the guide in th first post, I’ve got to first boot and blessed the EFI volume and restarted, it didn’t boot straight into macOS, but back to recovery, is this ok? Do I select Mojave in the Startup picker and reboot?
 
Brand-new Logitech G502.

This problem has gone on for ages. I initially thought it was to do with the USB extension cable I was using, so I replaced the cable with an active extender, then replaced the mouse, figured out a plist setting that was causing the computer to crash periodically, before finally admitting defeat.

I recently built a second Mac on Catalina because I also have an unrelated crash issue which I thought Catalina might solve, but it too suffers from the senile mouse issue, hence the question.
The G502 comes in 3 different flavours, and the driver software differs; this might be helpful - https://logi101.com/logitech-g502-software/
 
cMP with RX580, fresh install of Mojave onto SSD in bay 1. I’ve followed the guide in th first post, I’ve got to first boot and blessed the EFI volume and restarted, it didn’t boot straight into macOS, but back to recovery, is this ok? Do I select Mojave in the Startup picker and reboot?
I put in a GT120 and did it that way
 
it didn’t boot straight into macOS, but back to recovery, is this ok?
Unless your video card has a broken GOP, you should have seen the OC boot menu, and from there, you should be able to select Mojave. If it just rebooted into Recovery, then it's possible that your ESP wasn't properly blessed.

Do I select Mojave in the Startup picker and reboot?
I put in a GT120 and did it that way
This is fine if you are referring to the OC boot menu. However, if you are referring to the native one, then you are actually bypassing OC.
 
Unless your video card has a broken GOP, you should have seen the OC boot menu, and from there, you should be able to select Mojave. If it just rebooted into Recovery, then it's possible that your ESP wasn't properly blessed.



This is fine if you are referring to the OC boot menu. However, if you are referring to the native one, then you are actually bypassing OC.
When I put the GT120 in, I could see the OC picker, I did control enter on the EFI. I got to the end of the basic setup, restated a few times always to OC, I put the rx580 back in and it doesn't go anywhere after the boot chime, had to restart to recovery and booted OS bypassing OC. I think it might be my RX580, how do confirm and fix a broken GOP on the card?

Many thanks
 
Updated OC to latest and now my Mac won’t boot. I assume this is because SurPlus is no longer installed (I modified the default config.plist according to the instructions)? I’m on the latest Big Sur.

If so, why isn’t this factor mentioned in the tutorial? I will update to Monterey, but need to boot first!
 
Updated OC to latest and now my Mac won’t boot. I assume this is because SurPlus is no longer installed (I modified the default config.plist according to the instructions)? I’m on the latest Big Sur.

If so, why isn’t this factor mentioned in the tutorial? I will update to Monterey, but need to boot first!
The Legacy settings spoiler describes different or additional settings needed for pre-12.2 versions of macOS.
 
  • Like
Reactions: JeDiGM and mode11
The Legacy settings spoiler describes different or additional settings needed for pre-12.2 versions of macOS.
Got it. The label is a bit ambiguous - I assumed the settings themselves were legacy (which in a sense they are I guess), so just ignored them. Not that they’re for a legacy OS.

‘For Monterey 12.1 or earlier’ might be clearer. Quite important, as booting without SP can cause disk corruption.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.