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.
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
I originally installed Windows 10 as described in post #1 when I first installed OC (0.6.7 I think). I used brigadier for drivers and I use Magic Utilities for bluetooth mouse and keyboard.
I was able to do an upgrade rather than a clean install today to Windows 11.

I did these steps sequentially and did not back out of any one of them so I don't know if all are needed but I believe in "If it ain't broke don't fix it".

All steps from within Windows 10 booted through OC. Windows 11- system update indicated the PC was not compatible with Windows 11 and PC Health Check indicated as expected that there was no TPM, no secure boot and cpu unsupported.

Step 1. I did the registry edits described here.

After reboot, still same situation on Windows 11 compatibility.

Step 2. I tried the "How to Bypass Windows 11 TPM Check From Windows Update" section in

I ran the cmd script but after it installed, still no update possible.

Step 3. I created the update USB using Rufus 3.17.
Rufus here: https://rufus.ie/en/
windows image from here: https://www.microsoft.com/software-download/windows11

Using Rufus I loaded the Windows 11 image and created the USB selecting the option to "bypass TMP check and cpu check"

I then ran the setup script on the USB (double click) while in Windows 10 - ie not a reboot and launch installer from the USB. This did an upgrade to Windows 11 with no issues. I didn't need to install any drivers and Magic Utilities works fine.

Windows 11 updates are available within Settings and everything seems to be working.

Windows 11 seems much snappier than 10.

I hope someone else can reproduce this.
 
Last edited:
Good. At least OC is loaded. You could generate a debug log to find out more about the boot menu issue. See Maintenance > Debugging in post #1.
Debug text attached

I'm not sure what I'm looking for, so I searched the term failed and found below

26:296 00:114 OCSMB: SmbiosLookupHost failed to lookup SMBIOSv3 - Not Found

56:280 00:345 OCUI: Failed to load image (1/1) Resources\Image\Acidanthera\GoldenGate\Background.icns prefix:Acidanthera\GoldenGate icon:0 - Not Found
56:407 00:127 OCUI: Failed to load image (1/2) Resources\Image\Acidanthera\GoldenGate\Apple.icns prefix:Acidanthera\GoldenGate icon:1 - Not Found
56:745 00:338 OCUI: Failed to load image (2/2) Resources\Image\Acidanthera\GoldenGate\ExtWindows.icns prefix:Acidanthera\GoldenGate icon:1 - Not Found
57:042 00:296 OCUI: Failed to load image (1/2) Resources\Image\Acidanthera\GoldenGate\Other.icns prefix:Acidanthera\GoldenGate icon:1 - Not Found
57:155 00:112 OCUI: Failed to load image (2/2) Resources\Image\Acidanthera\GoldenGate\ExtTool.icns prefix:Acidanthera\GoldenGate icon:1 - Not Found
57:670 00:515 OCUI: Failed to load image (1/2) Resources\Image\Acidanthera\GoldenGate\ResetNVRAM.icns prefix:Acidanthera\GoldenGate icon:1 - Not Found
57:785 00:115 OCUI: Failed to load image (2/2) Resources\Image\Acidanthera\GoldenGate\ExtShell.icns prefix:Acidanthera\GoldenGate icon:1 - Not Found

Then I noticed this,

13:977 00:112 OCC: GOP exists on ConsoleOutHandle and has 0 modes
14:282 00:304 OCC: Looking for GOP replacement due to invalid mode count
14:392 00:110 OCC: Alternative GOP status is - Not Found
14:698 00:306 OCC: Missing compatible GOP - Not Found

Ive tried booting connected individually to each of the following, apple cinema display thru apple adapter dvi to adc, HDMI to LG monitor and Display port to LG monitor. No change.

Ive seen elsewhere in this thread with a different issue that even if the ConsoleOut Handle has 0 modes, an alternate GOP was found, trying to understand, am I on the right track

Code:
14:934 00:006 OCC: GOP exists on ConsoleOutHandle and has 0 modes
14:939 00:005 OCC: Looking for GOP replacement due to invalid mode count
14:944 00:005 OCC: Alternative GOP status is - Success
14:950 00:005 OC: Requested resolution is 0x0@0 (max: 1, force: 0) from Max
14:955 00:005 OCC: Requesting 0x0@0 (max: 1) resolution, curr 4294967295, total 7
14:960 00:005 OCC: Mode 0 - 1920x1080:1
14:965 00:005 OCC: Mode 1 - 640x480:1
14:971 00:005 OCC: Mode 2 - 800x600:1
14:976 00:005 OCC: Mode 3 - 1024x768:1
14:981 00:005 OCC: Mode 4 - 1280x1024:1
14:986 00:005 OCC: Mode 5 - 1400x1050:1
14:992 00:005 OCC: Mode 6 - 1280x960:1
14:997 00:005 OCC: Setting mode 0 with 1920x1080 resolution
15:005 00:007 OCC: Changed resolution mode to 0
15:010 00:005 OC: Changed resolution to 0x0@0 (max: 1, force: 0) from Max - Success
15:015 00:005 OCC: Switching to direct GOP renderer...
15:021 00:005 0: shl:0 shr:0 mask:FF0000
15:026 00:005 1: shl:0 shr:0 mask:FF00
15:031 00:005 2: shl:0 shr:0 mask:FF
15:037 00:006 Bytes per pixel: 4
15:043 00:005 0: shl:0 shr:0 mask:FF0000
15:048 00:005 1: shl:0 shr:0 mask:FF00
15:053 00:005 2: shl:0 shr:0 mask:FF
15:058 00:005 Bytes per pixel: 4
15:064 00:005 OCC: Using builtin text renderer with 1 scale
 

Attachments

  • opencore-2022-02-05-075119.txt
    256 KB · Views: 118
Last edited:
13:977 00:112 OCC: GOP exists on ConsoleOutHandle and has 0 modes
14:282 00:304 OCC: Looking for GOP replacement due to invalid mode count
14:392 00:110 OCC: Alternative GOP status is - Not Found
14:698 00:306 OCC: Missing compatible GOP - Not Found
Your card's firmware is apparently still problematic. Perhaps you could try finding another version to flash.
 
I think what happens is that the installer (for Ubuntu and perhaps other distros) is unable to write the needed boot files to the EFI partition on the disk that linux is installed on even though one has set things up correctly. On a PC, there is usually an error message that is displayed, but on a cMP, the installer just crashes at that boot loader install.

I eventually got my install to work by some round about method I'd rather not get into since it isn't an OC problem (unless OC is causing it somehow). I am not aware of this OpenLinux option, but I time has left me short for me to keep up with things.
Thanks for the advice. The same happened to me. I followed all the above instructions, with installations failing/stalling at the grub-install. Finally, Ubuntu appeared in the OpenCore Bootpicker and Ubuntu boots fine! I was using 0.75, now 0.77 (whether that had any impact?).
 
  • Like
Reactions: 0134168
Thanks for the advice. The same happened to me. I followed all the above instructions, with installations failing/stalling at the grub-install. Finally, Ubuntu appeared in the OpenCore Bootpicker and Ubuntu boots fine! I was using 0.75, now 0.77 (whether that had any impact?).
Nice! Runs fine?
 
Your card's firmware is apparently still problematic. Perhaps you could try finding another version to flash.
Strange, I made OC-CD, I wanted to disable OC and boot back into my W10 to look at other .roms, I restarted to the OC-CD, now I can see the OC boot picker?

Found this

 

Attachments

  • 455A8A93-AE0D-4EC6-808B-F438348C49FF.jpeg
    455A8A93-AE0D-4EC6-808B-F438348C49FF.jpeg
    169.5 KB · Views: 80
Last edited:
Strange, I made OC-CD, I wanted to disable OC and boot back into my W10 to look at other .roms, I restarted to the OC-CD, now I can see the OC boot picker?
Strange. So the CD gives you a boot screen but your main OC does not. Except for the recommended changes for the CD, are both configs the same?
 
Strange. So the CD gives you a boot screen but your main OC does not. Except for the recommended changes for the CD, are both configs the same?
They are the same, is there a way to compare the config files thou? I have three in my home folder, basic and complete setup version, debug version and OC-CD version.
 
Last edited:
They are the same, is there a way to compare the config files thou? I have three in my home folder, basic and complete setup version, debug version and OC-CD version.
To compare the files, you could use FileMerge. It comes with Xcode. An easy way to rule out the config is to copy the one from the CD (which gives you the boot menu) to your main OC. Better yet, copy the entire EFI folder over. Just do this as a test (because if you've followed post #1, then RequestBootVarRouting will be disabled for the CD, and you really need it to be enabled for normal operation). If the boot menu still doesn't appear, then for some reason, your hardware setup and the location of your ESP are affecting OC's functionality.
 
MacPro 5.1 after Monterey Beta update 12.3 Beta,Airplay was disappeared ,using latest OLCP patcher 0.4.2 was used.
WIFI Card Broadcom Fenvi FV-T919 was using, it was showing Airplay before the beta 11.3 update, please tell problem was with unsupported Broadcom chip.
 

Attachments

  • 3.jpeg
    3.jpeg
    54 KB · Views: 63
  • 1.jpeg
    1.jpeg
    62.6 KB · Views: 71
  • 2.jpeg
    2.jpeg
    64.3 KB · Views: 65
I did some searching and couldn't find an answer, so sorry if this is already discussed. I have a preexisting Windows 10 Pro install on my Mac Pro from before Open Core. Is it possible to add it to the open core boot picker? The only way I can boot to windows at the moment is to select it in the Mac boot picker before Open Core is loaded.
Thanks!
 
I did some searching and couldn't find an answer, so sorry if this is already discussed. I have a preexisting Windows 10 Pro install on my Mac Pro from before Open Core. Is it possible to add it to the open core boot picker? The only way I can boot to windows at the moment is to select it in the Mac boot picker before Open Core is loaded.
Thanks!
Your current Windows 10 Pro, detected by the Apple Startup Manager, is legacy, whether 32- or 64-bit. OC can only detect a (64-bit) UEFI installation of Windows. In theory (this didn't work for me), you should be able to reinstall Windows 10 as UEFI on top of a legacy 64-bit version of the same OS.
 
Your current Windows 10 Pro, detected by the Apple Startup Manager, is legacy, whether 32- or 64-bit. OC can only detect a (64-bit) UEFI installation of Windows. In theory (this didn't work for me), you should be able to reinstall Windows 10 as UEFI on top of a legacy 64-bit version of the same OS.
No need to install again.

 
I did some searching and couldn't find an answer, so sorry if this is already discussed. I have a preexisting Windows 10 Pro install on my Mac Pro from before Open Core. Is it possible to add it to the open core boot picker? The only way I can boot to windows at the moment is to select it in the Mac boot picker before Open Core is loaded.
Thanks!

you can chainload rEFInd and start legacy Windows with it. Search the thread for it.

if your GPU has a native bootscreen you can start _legacy_ Windows by the native boot picker.

dont do this with Uefi Windows (starting with the native boot picker) as you get certificates in the boot rom without OpenCore protection. This is not needed but an important side note.
 
To compare the files, you could use FileMerge. It comes with Xcode. An easy way to rule out the config is to copy the one from the CD (which gives you the boot menu) to your main OC. Better yet, copy the entire EFI folder over. Just do this as a test (because if you've followed post #1, then RequestBootVarRouting will be disabled for the CD, and you really need it to be enabled for normal operation). If the boot menu still doesn't appear, then for some reason, your hardware setup and the location of your ESP are affecting OC's functionality.
I did copy the EFI folder to the USB and didn't show the boot picker, when I copied back the EFI file, it would no longer bless, so I used another USB started fresh, I also flashed a user uploaded bios from TPU.

Im going to format and reinstall again to the original USB drive, just to rule out it wasn't the USB drive causing the issue

Finally..... it works
 

Attachments

  • 9FCD2E26-D8F1-4BF6-A6C3-EEC371F0F438.jpeg
    9FCD2E26-D8F1-4BF6-A6C3-EEC371F0F438.jpeg
    149.4 KB · Views: 67
Last edited:
No need to install again.

Not for the faint of hearted, though. As a precaution, I'd physically remove the disk OC sits on. Also a Windows installer (important: of the same version, since i.e. 20H1 installer will not fix 21H2 installation) is handy when the boot errors occur.
 
Next step, Im in Mojave, want to do a clean install of Big Sur onto nvme drive Samsung 970 eve plus.

Ive downloaded the latest installAssistant package, installed into applications folder, checked SecureBootModel is disabled, not sure about setting VMM flag enabled, can't find it in the config.plist, and I thought I read it was required only for Catalina.

I initiate installer in the application folder, elect the nvme drive, I can observe in the activity monitor something happening, gets to restart, I select the os installer in the OC picker, it loads the progress window where it either stalls at the very beginning or about 40%.

Ive searched this thread for clues, is there a step I'm missing?


Do I need surplus to install big sur?
 
Last edited:
Many thanks, done :)
Thank you, and I'm not done yet :)

Next step I want to try install Windows 10 Pro UEFI to sperate nvme, if im not mistaken the guide is for a legacy install? I think i have some more researching to do, or is it a case of creating a USB installer, remove all other drives and install? Ive already done this before, I have a legacy install with bootcamp on sata SSD, its been giving me hassle lately not booting back to macOS, I'd like to see the W10 boot option in OC picker.

I already have a backup reconstructed mac boot rom for regular 90 day servicing.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.