Jump to content

Asus X99 & Secure Boot - Multiboot Yosemite and Windows 8.1 with UEFI Clover


hooli
 Share

7 posts in this topic

Recommended Posts

I have an Asus X99 with two SSDs for Windows 8.1 (installed first) and Yosemite (UEFI Clover). Unfortunately the whole secure boot / CSM seems a bit unintuitive.

 

I can either 

1) Enable or disable CSM Legacy boot

2) Can't disable Secure boot directly, but can choose "Windows UEFI" or "Other OS"

3) I took the plunge and deleted the key stores and this shows Secure Boot as disabled (with an option to restore Default Keys), but makes no really difference.

 

From the boot list, Windows only shows up with Secure Boot "Windows UEFI" selected, but only as a plain SATA P2: , not a UEFI boot option (seems odd).

Clover is always there as (UEFI) P4: on the other SSD.

I can't boot Windows from Clover with either Secure boot enabled/keys deleted , or CSM enabled/disabled.

The odd thing is, I assumes Windows would appear as a UEFI boot device, but I can only boot it with secure boot on "Windows UEFI" or as a standard P2: disk with CSM enabled. I was hoping deleting the Secure Boot keys would allow Windows to be booted via Clover as UEFI. I've seem comments about a Windows watermark when booting without Secure Boot, and a patch to remove it.

 

It would be nice to use "Other OS" to boot Clove with CSM disabled, since the display defaults to hi-res and seems faster, but Windows does not boot.

I was thinking that I would just let Clover boot OSX in the boot priority, and choose Windows via the BIOS when required, which would need CSM enabled.

 

Does Secure Boot need to be disable BEFORE Windows 8.1 is installed on a HDD, or does that have no effect?

 

If there's a better solution (or any info on handling Secure Boot on X99), I would be grateful for any suggestions.

 

Thanks in advance...

Link to comment
Share on other sites

Thanks for the quick replies.

 

Yep, I assumed Windows would install itself as UEFI.. I was wrong :) It's installed Windows as a Legacy MBR on it's own SSD.

 

When I do boot clover, there are two options - "Boot Windows from System Reserve" or "Boot Windows from"  (the C: partition)

Both options just hang at a blinking cursor.

 

I've seen comments about /EFI/CLOVER/Driver64/Ntfs.efi but my Clover is just using Drivers64UEFI, and does not have the Driver64 directory.

Currently just trying things out booting from a USB stick with Clover.

 

If Clover is booted as UEFI, can it then launch a legacy MBR version of Windows or is it expecting an EFI partition?

Can it be configured to boot the legacy Windows, or should I re-install Windows as UEFI (which probably is the best solution in the long run)

Just wondering how it works.

 

Cheers

Link to comment
Share on other sites

I suggest you reinstall Windows UEFI and forget about legacy world completely. It's nightmare to look at and deal with their problems.

 

If you insisted on using Windows Legacy, just change Boot > Legacy in config.plist to LegacyBiosDefault.

 

Still, spending half an hour to reinstall Windows will save you tons of hours later.

Link to comment
Share on other sites

I suggest you reinstall Windows UEFI and forget about legacy world completely. It's nightmare to look at and deal with their problems.

 

If you insisted on using Windows Legacy, just change Boot > Legacy in config.plist to LegacyBiosDefault.

 

Still, spending half an hour to reinstall Windows will save you tons of hours later.

I would agree with pokenguyen, reinstall Windows using UEFI, it boots much quicker. The only slight niggle I have run into is updates to Windows seem to rename the bootmgfw.efi file so only boots to Windows until I rename the file. Admittedly this is a Windows 10 install, not sure if it is the same in Windows 7 or 8.                                                       

Link to comment
Share on other sites

 Share

×
×
  • Create New...