- Joined
- Aug 17, 2014
- Messages
- 139
- Motherboard
- HP EliteBook 840 G6
- CPU
- i5-8365U
- Graphics
- UHD 620
FYI: I think this is also a fix for having to rename bootmgfw.efi to bootmgfw-orig.efi.
I haven't tested it, but my theory is... If you put Windows bootloader files on its own partition, separate from the EFI partition, when Windows updates kick in, they'll update the EFI/Microsoft on that partition and not the real EFI partition (which would contain only Clover files).
Two side effects:
- no need to rename bootmgfw-efi => bootmgfw-orig.efi
- and no worries about Windows updates causing BIOS to boot directly to Windows instead of Clover
I can confirm that this is correct because after installing OSX, I installed Windows 8 (using UEFI) then Windows 10 (through efi) this process did not mess up Clover Bootloader so I didn't have to rename bootmgfw.efi to bootmgfw-orig.efi.
EDIT: Oh! i don't think someone like me is totally free from future mess up because the second Windows installed the boot entries in the Real EFI. Microsoft folder is still sharing partition with Clover files.
So, If I create another small FAT32 partition and move the Microsoft folder for Windows 10 to it, I'll still be alright? I guess.