Contribute
Register

Help with Booting Windows 10 with Clover UEFI

Joined
Aug 4, 2015
Messages
8
Motherboard
X99 UD4
CPU
Intel 5820k
Graphics
Gigabyte GTX970
Mac
  1. MacBook Pro
Classic Mac
Mobile Phone
  1. iOS
Hi everyone! Current specs X99 UD4 - 5820k - GTX970 - 16gb ram -
I have sucessfully installed Windows 10 and Yosemite so far on 2 separate SSD drives. I have another drive too for LINUX (which I havent installed yet) In clover I go the the windows drive but it gives me a blank screen and I have to restart the computer by turning it off.
In order for me to boot Windows I have to disconnect my Yosemite drive from the motherboard as it just will not boot in clover.
I have tried installing the ntfs.efi in EFI/CLOVER/Driver64UEFI and that didnt work either..

Does anyone have any suggestions or perhaps a guide or video with step by step instructions?
Thanks
 
Joined
Jul 5, 2015
Messages
1
Mac
Classic Mac
Mobile Phone
I, too, am having this exact problem. Although you don't have to disconnect your Mac's SSD, you can just select where to boot from BIOS, or just exit Clover and it will start to boot in Windows just fine.

Only problem is that if you try to select Windows from within Clover, it gives a black screen and doesn't load. Any thoughts?
 
Joined
Nov 20, 2012
Messages
60
Motherboard
GA-Z77X-UP5 TH
CPU
i7-3770K
Graphics
GTX 660 Ti
I am having this issue with my MBR legacy install of windows on one system.
But my UEFI install of windows boots fine.
I had to use a path in the custom entry. \EFI\Boot\bootx64.efi
you may need a different path. For the volume I used the guid from the win efi partition.
 
Joined
Jan 4, 2011
Messages
61
Motherboard
Gigabyte GA-Z97X-UD5H-BK-F8
CPU
i7-4790K
Graphics
RX 580
Mac
  1. MacBook
  2. MacBook Pro
Mobile Phone
  1. iOS
In my case, the only way to get multiboot with Clover UEFI was:
  1. Repartition the HDD where's Windows will be installed as GUID (HFS+).
  2. Format the Windows partition as NTFS using GParted and left EFI partition intact.
  3. Than remove the others HDD and left only this one connected.
  4. Install Windows (DVD or USB) as UEFI using Boot options (F8 in ASUS mobo case).
  5. Plug the other HDD again and enter BIOS, applying again Clover as the first boot option.
  6. After restart install in EFI > CLOVER > drivers64UEFI this drivers: HFSplus.efi and Ntfs.efi
 
Joined
Jan 3, 2013
Messages
13
Motherboard
GA-Z390-M
CPU
i5 9500
Graphics
Nvidia RTX 2070
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
What alexramone said works, but there may not be any need to go through all that trouble.

Try this: open up Clover Configurator and nivagate to the 'Boot' section. In the top right you'll see the 'Legacy' section. This tells Clover how to deal with MBR partitions.
Try different options here and see wich one works for you. The regular 'PBR' boot helped me boot my MBR Windows 10 install.

Good luck!
 
Joined
Mar 26, 2013
Messages
24
Motherboard
Gigabyte Z77X-UD5H
CPU
Intel Core i7 3770k
Graphics
Gigabyte GTX 780
Mobile Phone
  1. iOS
All solutions didn't worked for me. I have the same problem. I didn't paid attention when I was installing windows 10 and in installed on MBR partition.
El Captain and Clover are installed as EUFI.
I tried PBR, PBR test (crashed my El Captain no sound, no ethernet, bas resolution.. i'm currently reinstalling it), but still enable to boot windows 10. I just have a white dash blinking on the top left of my screen..
Any more ideas? Is there any other possibilities existing than re-installing windows 10 but on EUFI?
 
Joined
Sep 4, 2015
Messages
40
Motherboard
Asus P8H61-M Pro
CPU
i7-2600
Graphics
Intel HD2000 / Asus Nvidia Geforce EN210
Mac
Classic Mac
Mobile Phone
I found a solution to this without any re-partitioning. I am assuming that this affects NTFS formatted Windows partitions as both of mine are NTFS formatted on an MBR drive and I have the same problem. This solution should work for Windows 8, Windows 8.1 and Windows 10. It will also work for Windows 7 but requires a little extra work and access to some binaries from Windows 8 or higher.

Firstly, let me explain that ideally one would want to install Windows for UEFI boot on a GPT formatted drive. Windows will automatically create the required EFI directory structure and populate the necessary files. Clover would then automatically recognise the Windows bootx64.efi file in its expected place and the bootable UEFI Windows partitions should appear in Clover. However, as myself and evidently others have discovered, if Windows has been installed for booting from the MBR, then this file is not present and although the NTFS partitions show in Clover as legacy drives, they cannot be booted.

However, it is possible to work around this problem and create the C:\EFI directory structure and the required files post-install using the Windows bcdboot tool. It is not usually advisable to use an MBR partition for UEFI boot, but so long as the required Windows EFI files and BCD structure exist, Clover will recognise them and and boot into the Windows partition. I cannot take credit for this solution because I found it on a Linux forum where it was applied to the GRUB bootloader, but I tested it on my machine and it does also work with Clover. I will eventually convert my Windows HDD to a GPT formatted disk but for now, this appears to solve the problem for me.

The process is actually quite simple, but before proceeding, the usual disclaimer applies. I will not be responsible for any damage caused to your system! Back up your Windows partition before proceeding and use the process at your own risk!

As a pre-requisite, the NTFS.efi driver will need to be present in your Clover EFI/CLOVER/drivers64UEFI directory. I have seen recommendations to have HFSplus.efi or VboxHfs-64.efi there as well, but these are probably not necessary for a Windows boot from NTFS.

I have a dual boot Windows setup on one HDD and OSX on another HDD. This process did not affect the MBR or the standard Windows BCD boot loader. If you have Chimera + OSX, then it will not affect Chimera either. You will probably also have the Clover bootloader configured to boot OSX or be using a bootable USB drive with Clover to boot the machine from. It is useful to have some other way of getting into your OSes. It might also be useful to have a Windows install DVD or USB drive handy just in case it becomes necessary to repair the Windows startup in the event that something goes wrong.

Boot into Windows 8/8.1/10 and check whether a C:\EFI folder already exists. If Windows is being booted in legacy mode from an MBR, there shouldn't be one. If there is one then Windows may already be configured for UEFI boot and the partition should already be recognized in Clover. If there is no C:\EFI folder, then it is probably safe to proceed. Open a Command window with Run as Administrator. Issue the following command:


bcdboot C:\Windows /s C: /f uefi

Most likely Windows is on drive C: otherwise substitute the appropriate drive letter. This command does two things: (1) Creates the C:\EFI directory structure and populates it with the appropriate files and (2) creates a BCD database for UEFI boot and an NVRAM entry for the partition.

Explanation as follows: C:\Windows - we want to boot the Windows installation at C:\Windows; /s - we want to write the EFI folder to system partition identified as drive C; /f uefi - we want to write a UEFI BCD to C:/EFI rather than an MBR BCD to C:\boot for MBR booting.


Once this has been done, there should now be a C:\EFI folder. Under this there will be a Boot and a Microsoft folder. Under Boot you will find bootx64.efi, and under Microsoft will be further boot files including the BCD. If C:\EFI has been created and populated then reboot into Clover and the partition should now appear as an EFI bootable Windows disk in Clover.

If you are dual booting Windows 8, 8.1 or 10, then other partitions can be made available to Clover in the same way by booting into the appropriate version of Windows and performing the same command, but taking care to use the appropriate drive letter for the Windows system in question. While booted into it will usually be drive C: though.

The bcd boot command in Windows 7 does not support the /f parameter so this will not work under Windows 7. However, if you have access to Windows 8 or 10, then I found that it was possible to copy the BCD tool files from the later version of Windows and use them while booted into Windows 7. I copied the following files, which are found under C:\Windows\system32 into a new folder that was also accessible to Windows 7. I guess they could also be copied to a USB drive:

bcd.dll
bcdboot.exe
bcdedit.exe
bcdprov.dll
bcdsrv.dll

Do NOT copy them into C:\Windows\system32 under Windows 7 but create a separate folder to hold them. You will need to boot into Windows 7, open a command prompt with Run as Administrator and navigate to the directory where you copied the files and execute the same command as above from that directory.

Now that Clover is booting our legacy partitions using UEFI, we no longer need the legacy partition entries. To tidy these up, use the Clover Configurator. Backup your config.plist, then load it in Clover Configurator. In the Gui section there are some settings under the 'Scan' heading. By default this will be set to 'Auto=yes'. Change it to 'Custom' and then check Entries and Tool. Leave Legacy unchecked. By default Clover includes all kernels so there is no need to set anything under Kernel.

This worked fine on my system and I can now boot into OSX Yosemite, El Capitan as well as Windows 10 and Windows 7 using Clover.




 
Joined
Oct 31, 2015
Messages
3
Motherboard
GA-Z97M-D3H
CPU
intel i5-4690k
Graphics
onboard gfx
Mac
Classic Mac
Mobile Phone
I found a solution to this without any re-partitioning. I am assuming that this affects NTFS formatted Windows partitions as both of mine are NTFS formatted on an MBR drive and I have the same problem. This solution should work for Windows 8, Windows 8.1 and Windows 10. It will also work for Windows 7 but requires a little extra work and access to some binaries from Windows 8 or higher.

Sir, you just saved my day! Thank you very much for this solution!
 
Joined
Aug 13, 2014
Messages
4
Motherboard
GA-Z68AP
CPU
Intel Core i5
Mac
Classic Mac
Mobile Phone
Is there anyway to access those Windows 8/10 files without actually having it installed? I currently have Windows 7 and this UEFI/Legacy fiasco is driving me crazy! Haha

Thanks in advance!
 
Joined
Jun 11, 2011
Messages
1
Motherboard
gigabyte B150-HD3P
CPU
i5-6600
Graphics
R9 280
Mac
  1. iMac
Mobile Phone
  1. iOS
Sir, you just saved my day too !
Thank you very much for this solution!

I worked on it since several weeks .

For Jakeykins i was in the same situation and so i download Waik tool (please find attached)

I just run the cmd line bcdboot C:\Windows /s C: /f refi inside the amd64 folder for me and it s works ..

KR
 

Attachments

  • Waik_4.7z
    1,018.7 KB · Views: 1,765
Top