<< Solved >> MacOS Monterey install doesn't show up with secure boot enabled

[UnequalBiscuit]

Sorry if it's obvious, still relatively new to hackintoshing:
I'll start off by saying I triple boot with arch and windows, so I chainload OpenCore through rEFInd.
I had a perfectly working hackintosh up until I decided to get around to setting up secure boot (with shim, as to load MOK signed refind), signed all the .efi files (with the same MOK), and i can get to the boot picker, as well as boot to windows through it, but my macos install doesn't show up while secure boot is enabled in bios.
I tried with it disabled, using the same path (Shim->Refind->OpenCore), and the macos entry was there.
Is using opencore with secure boot in this way even possible?

 

[trs96]

Your Probook came with Windows installed. Secure Boot enabled will prevent macOS from booting as it's not a supported OS on that hardware. Obviously you'll need to disable Secure Boot to use your multi-boot system.

• All PCs sold today include keys that Microsoft controls.
• If you would like to enable UEFI Secure Boot for macOS, you need to replace your computer's standard keys with ones that you control.
• This is the really complicated part, not recommended, not worth the effort in my opinion.

Secure boot

Provides guidance on what an OEM should do to enable Securely booting a device

docs.microsoft.com

 

[UnequalBiscuit]

Your Probook came with Windows installed. Secure Boot enabled will prevent macOS from booting as it's not a supported OS on that hardware. Obviously you'll need to disable Secure Boot to use your multi-boot system.

• All PCs sold today include keys that Microsoft controls.
• If you would like to enable UEFI Secure Boot for macOS, you need to replace your computer's standard keys with ones that you control.
• This is the really complicated part, not recommended, not worth the effort in my opinion.

Secure boot

Provides guidance on what an OEM should do to enable Securely booting a device

docs.microsoft.com

Ah alright, I saw that as an option but didn't want to go through all of it, hence why i opted to use shim at first, either way, I have no real use for secure boot, as It's more of a personal challenge than anything so I'll be trying that method later :>

 

[trs96]

Looks like miliuco has posted on this topic recently so post in that thread when you try to enable Secure Boot again.

[GUIDE] OpenCore and UEFI Secure Boot using Windows Subsystem for Linux

Motherboard UEFI firmware has Secure Boot capability so that only digitally signed boot loader files with keys that are embedded in the firmware are allowed. With UEFI Secure Boot enabled: - Windows can boot as the firmware includes Microsoft certificates (sometimes also certificates from the...

www.tonymacx86.com

 

[UnequalBiscuit]

Looks like miliuco has posted on this topic recently so post in that thread when you try to enable Secure Boot again.

[GUIDE] OpenCore and UEFI Secure Boot using Windows Subsystem for Linux

Motherboard UEFI firmware has Secure Boot capability so that only digitally signed boot loader files with keys that are embedded in the firmware are allowed. With UEFI Secure Boot enabled: - Windows can boot as the firmware includes Microsoft certificates (sometimes also certificates from the...

www.tonymacx86.com

As it turns out, my original method would likely have worked, I just completely forgot I had SecureBootModel set to disabled, as after I tried importing my own keys, I got the same issue. Just changing SecureBootModel it back to default fixed the issue = - ="
Time and effort wise, you're right in saying it probably wasn't worth it
But the satisfaction alone made it worth it