- Joined
- Dec 15, 2010
- Messages
- 682
- Motherboard
- Asus ProArt Z690 Creator WiF
- CPU
- i9-12900K
- Graphics
- RX 6900 XT
- Mac
OK! We are getting somewhere
I wonder if Windows adding boot entries is doing something... Can you try this:
Boot macOS, or some other OS except Windows (Linux, WinPE etc). You will then mount the windows EFI partition, then rename the file in /EFI/Microsoft/Boot/bootmgfw.efi to /EFI/Microsoft/Boot/bootmgfw-orig.efi. Clover will scan and find the file, and if you have made a custom entry for it, just alter the name to read like the renamed file.
You can also rename bootx64.efi in /EFI/Boot, this may or may not help. The actual bootloader for Windows is the bootmgfw.efi file, it is responsible for loading and executing the BCD store before handing control over to WinLoad.efi.
Years ago I tried looking for a way to just load Winload.efi directly, but it seems that bootmgfw.efi sets up certain variables and such, so it couldn't be done
I really hate Windows persistently adding itself to NVRAM's boot option, it's like it wants to be the only bootloader or the number 1... It's as if Microsoft isn't aware that there are other bootloaders that can chain to their's and boot Windows as well lol...
I had already renamed the Microsoft bootmgfw.efi file, but I have not tried renaming the bootx64.efi. I'll try that this evening. Something else I need to look at is how having an extra UEFI Drive (Windows) affects my Memmap dump. Theoretically, I'm getting the allocation error because something has changed memory wise. Maybe my slide parameter needs to be recalculated with the Windows drive in the mix? Will take a look at that this evening as well.