Contribute
Register

Bios keeps putting Windows Boot Manager as priority over Clover Drive

Status
Not open for further replies.
Joined
Mar 3, 2014
Messages
5
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Hey guys, I seem to have everything up and running with a dual boot system, except that my bios keeps putting the windows boot manager as the first priority boot option by itself, even though I have it set it to be Clover. It will be fine until it's shut down for a long while, then puts it back to windows boot manager. Any ideas as to how I can fix it? Thanks :)
 
Hey guys, I seem to have everything up and running with a dual boot system, except that my bios keeps putting the windows boot manager as the first priority boot option by itself, even though I have it set it to be Clover. It will be fine until it's shut down for a long while, then puts it back to windows boot manager. Any ideas as to how I can fix it? Thanks :)
Is your dual boot setup from TWO separate Disks or from two partitions on a SINGLE disk?
 
/efi/boot/bootx64.efi is the fallback path, most firmwares will boot /efi/microsoft/bootmgfw.efi first. Add /efi/clover/cloverx64.efi to your EFI boot menu and adjust the boot order e.g. with EasyUEFI from Windows.
 
Hi here, I have the exact problem like redversus. Anyone could help?
Hi there. I recently set up my win10/hackintosh multiboot machine. And it worked great, except there're some minor bugs when booting win10 with clover (ex. touchpad's two finger scrolling malfunction etc). So normally I change BIOS boot option to win10 ssd when it's need rather than using clover bootloader. Now, the problem is that every time when I switched BIOS boot option to my win10 ssd, it successfully enter windows, but when I shut down the computer and start it again, the boot drive became the hackintosh ssd as the boot option in BIOS changed by itself. However, if I press restart in Win10, it return to win10 as expected. So I am wondering why it seemed that clover has kidnapped my BIOS setting:crazy::crazy:. And suggestion is appreciated. Thank you very much.
 
Hi here, I have the exact problem like redversus. Anyone could help?

For people like myself looking for an answer in this context — likely you found a solution — here is the relevant section from the long and excellent article [Guide] Booting the OS X installer on LAPTOPS with Clover:

"After a Windows update, Windows may re-create bootmgfw.efi with updated code. To fix after a Windows update:
- on the EFI partition, remove EFI/Microsoft/Boot/bootmgfw-orig.efi
- rename EFI/Microsoft/Boot/bootmgfw.efi to bootmgfw-orig.efi

You can also use 'efibootmgr' in Linux to add a Clover entry and fix the boot order.
(Linux is free. Ubuntu can be run directly from a USB without installing)"
"
 
Status
Not open for further replies.
Back
Top