Force Legacy Bootloader?

[Injury]

So, when I install the legacy bootloader, for some reason when it installs, it shows a UEFI boot option in the BIOS. I was wondering if anyone knows how to fix this. If it helps, this issue is only occurring when the OS drive is set to GUID format. When the OS drive is set to Master Boot Record format, the issue does not occur.

 

[Injury]

So in even further testing, I don't even understand how this is possible, but with all boot options on this page set to Legacy as possible, it somehow managed to show the UEFI boot option after the OS and MultiBeast install. I have absolutely no idea.

 

[vulgo]

The options on that page are for using old hardware and operating systems that don't support UEFI. You can't turn off UEFI. What are you trying to boot?

 

[Injury]

The options on that page are for using old hardware and operating systems that don't support UEFI. You can't turn off UEFI. What are you trying to boot?

macOS/OS X

I'm trying to use the legacy bootloader on GUID drives. For some reason it's not working.

 

[vulgo]

macOS/OS X

I'm trying to use the legacy bootloader on GUID drives. For some reason it's not working.

Is Clover installed to the EFI partition? The Clover installer installs a copy at /EFI/BOOT/BOOTX64.EFI - as "the actions taken by the boot manager depend upon the system type and the policies set by the system designer" the presence of this file may determine UEFI booting before or instead of legacy booting. If you can explicitly set an option in the boot order for legacy booting on that disk it will work, otherwise:

• Rename the /EFI/BOOT directory folder to /EFI/BOOT-OFF
• Double check you selected one of the options boot0af or boot0ss during Clover install and follow instructions for that boot0 variant

 

[Injury]

Is Clover installed to the EFI partition? The Clover installer installs a copy at /EFI/BOOT/BOOTX64.EFI - as "the actions taken by the boot manager depend upon the system type and the policies set by the system designer" the presence of this file may determine UEFI booting before or instead of legacy booting. If you can explicitly set an option in the boot order for legacy booting on that disk it will work, otherwise:

• Rename the /EFI/BOOT directory folder to /EFI/BOOT-OFF
• Double check you selected one of the options boot0af or boot0ss during Clover install and follow instructions for that boot0 variant

When you say to rename the folder, you mean on the EFI partition, or the OS drive's partition where the EFI folder would be?

 

[vulgo]

When you say to rename the folder, you mean on the EFI partition, or the OS drive's partition where the EFI folder would be?

On the EFI partition

 

[Injury]

I think I've narrowed it down to my motherboard being the issue, because my Asus P9D WS is able to use the Legacy bootloader when installed to GUID OS drives, but my Z87-WS is not able to do the same.

So if there's a software fix for this, then, it seems like it wouldn't be normal behavior or there would be some type of patch required.