@herrscher
I am glad to see you fixed it enjoy the super fast ssd. Out of curiosity is there a way I can make it more clear where the driver should be in my pinned post ?

Zitat von sibliss im Beitrag #571

---

@herrscher
I am glad to see you fixed it enjoy the super fast ssd. Out of curiosity is there a way I can make it more clear where the driver should be in my pinned post ?

---

@herrscher

This is interesting, did the BDU create the clover\drivers64 directories but not the clover\drivers directories ? typically it will create both for an x64 config i think.
you will note that my pin says to simply use which ever directories that BDU created and to copy the driver to BOTH the BIOS and UEFI directories under the drivers(64) directory

It seems you have highlighted the difference between 32bit and 64bit i am to assume from this that you are now using a 32bit UEFI configuration.

i have adjusted the below quote to show the correct configurations.

Zitat von herrscher im Beitrag #572

---

the following is just not correct with the current version:

this is x64 config
"
Copy \EFI\CLOVER\drivers64\Off\NvmExpressDxe-64.efi...

...Legacy BIOS: to \EFI\CLOVER\drivers64\BIOS
...UEFI: to \EFI\CLOVER\drivers64\UEFI
"

It seems it should be:

this is x32 config
"
Copy \EFI\CLOVER\drivers\Off\NvmExpressDxe.efi...

...Legacy BIOS: to \EFI\CLOVER\drivers\BIOS\
...UEFI: to \EFI\CLOVER\drivers\UEFI\
"

---

Hi!

I have a Lenovo D30. I am trying to solve it based on the description, but I am not able to reach success. The BDU ran successfully, the boot menu of Clover popping up, I could setup windows 10 for the NVME M2 SSD, but after restart of the computer, system does not find the windows, thus this does not load up. (of course I still do not see the NVME drive in the BIOS). So it seems the clover and win setup was successfully, but the computer does not boot from NVME. Could you please help me anyone?

Thanks in advance.

@evosonic
Hello and welcome to the forums, please be aware that you will never see see the NVME drive in the bios as a bootable device that is not how this method works clover can't modify your bios after all. But clover can make it possible to boot from the nvme via the clover bootloader.
The bios MUST be set to always boot from the usb or hard drive where clover is installed to (the legacy device that your bios can actually see) once booted into clover, clover should search for bootable volumes across all of the drives including the NVME drive and then allow you to hopefully boot to windows.

As we begin trouble shooting your issue can you please confirm a few things for us.
When you restart the computer that you boot to the clover device (ie the usb or hard drive you installed clover on to) and that clover does load to the clover menu correctly. ?
Does the windows volume or windows system volume appear in the clover menu list to boot from. ?
If the volumes from the NVME drive do not appear in the clover menu please ensure you have copied the drivers to all the locations mentioned in my pinned post.

good luck, happy modding and of course report back here when you either get it working or if you're still having trouble report back here and we can try to troubleshoot further.

Hi folks,

trying to get this to work.

I allready have Clover running booting Catalina and Windows 10 (on separate SSD's)
I have now purchased a PCIe NVME card and some NVME drives, to increase speed of the system.
And I was planning to just use the existing SSD with clover as a boot device, rather than using a USB stick.

I am planning to do a complete reinstall, not move/copy the Windows 10 install from the SSD.

But i just cannot get clover to boot the Windows USB boot install media.

I get the error: boot0af , whenever I choose the USB Windows 10 install from Clover menu .

I have tried both using MBR and GPT partition on the usb stick, it doesnt matter.
I have tried both using Rufus and Microsoft official download tool to make a bootable UEFI USB install with EFI/UEFI folders.
The USB Windows install stick have all the EFI / UEFI folders, and needed drivers are put into folders.

The USB stick boots just fine when booting directly from it, I just cannot boot from it from within Clover (5107) on my SSD, or from a Clover (5117) boot usb made using BDU.
This is driving me nuts, been using the whole day now, cannot figure out why it will not boot the Windows install media from Clover.

The NVME card is the Asus Hyper V2. And the card/NVME is detected when starting install (boot directly from usb install media), but I cannot install on the NVME drive (GPT) because I need to boot/start the install USB from Clover to get UEFI capabilities.

My motherboard is a Gigabyte GA EX58 UD5 (v1).

What is causing the "boot0af" in this case??? All drivers are copied to the right places (I think). I have tried different USB slots, (but not all), should this matter?
I am even able to boot my Windows 10 legacy install (on another physical drive) from clover, ( I followed a tutorial and added EFI folder on the C: drive of the Windows drive)

I am so ready to install Windows on my NVME, but... the boot0af is stopping me :(

@ArcticLight
Hello what you are describing is a common issue and can often be solved in a number of ways...
firstly if you haven't already try using a different usb stick.
if you have an optical drive perhaps try that way.
Of course be sure the Windows 10 image/iso you are using is both x32 and x64 iso (Should in theory make it bootable regardless which architecture youre using). You can do this in the media creation tool downloaded from MS.
I hope this helps please report back if you're still getting the issue.and even if not as we'd love to hear how you fixed it.

Edit: I forget to mention worst case if you are lucky enough to have a blank spare hdd or ssd floating around try installing to that first the normal way then sysprep the install and simply copy the partitions to the nvme. Then try booting the nvme through clover.

@sibliss, thank you for your reply.

I will try another USB stick.

How can it matter if I have only x64 version of Windows on the install media, vs both x86 and x64 versions?

BTW It doesn't say anywhere weather the install media USB needs to be set up as GPT or MBR.
The target NVME drive must be GPT, shouldn't the install media also then be GPT?
(I watched a youtube video claiming this)

Will get back...

@ArcticLight the install usb shouldn't matter if it's mbr or gpt, however i believe the windows 10 media creation tool will automatically set what it thinks is appropriate.

i suggested to have both x32 and x64 on the usb as i am not sure if there may or may not be some funny business on the installation bootloader the media creation tool installs to the usb to facilitate the installation.
i suggested a different usb stick as i had to try about 3 before i got one to work myself.

@sibliss I have now tried 3 different USB stick, and tried again using MBR/GPT on the stick, I have also tried experimenting with file cluster size from 4096 to 512 (USB stick is automatically formatted using 4096, but some say Clover needs 512 ?), anyway no luck, same error boot0af:error, using both my installed Clover 5107, and BDU installed Clover on a separate stick 5117, same error, always.

I have also tried changing the PBR boot setting in my installed Clover 5107 config file/EFI, from (PBR, PBRtest, PBRsata, and legacyBIOS).
This does seem to do something, as with using PBRtest is just reboots when trying boot from the Window install media, and does nothing when having selected legacyBIOS, but still not able to boot.

I cannot believe I am the only one having this problem!?

You say this is a common problem, but I cannot read about anyone in this thread having this issue? And why is there noe solution if a common problem?

I am now trying making a bootable install media with both x86 and x64 versions of Window on, but I cannot see why that should mean anything.
EDIT:(tried, does not make any difference, still not working)

I would prefer not having to clone an installed image, as I would like to make a fresh install.

I can try making the NVME a MBR disk, and then try to install from a directly booted install-media, and the try to patch the install as I did on my SSD windows installation to be able to boot from Clover.
EDIT:(tried this, does not work, Windows install seem to detect that the NVME is not supported in BIOS and preventes me to install on it regardless if using MBR)

But would still like to be able to install directly onto the NVME, rather than cloning the partitions of another installation.
(I have bad experience with cloning installations)

Any other tips?

@ArcticLight
hmm all very interesting although i am not at all familiar with dual booting with clover for osx, i note a simple web search returns many results for the boot0af error including this one.

https://hackintoshmumbai.com/how-to-fix-the-boot0af-error-for-your-hackintosh/

i also note that some users have said they have fixed it by wiping the drive and re creating the partition tables.

while others have fixed it by removing other expansion cards and other non essential hardware.

it's been my experience that the nvme needs to be in GPT or it won't work.

i would still be interested to try a windows dvd as an install option.

i know you have said you've copied the driver ... to all 6 locations i mentioned in my pinned post?

i also note this https://www.tonymacx86.com/threads/how-do-you-fix-boot0af-error.109717/

i'm sorry i can't be of much help with this perhaps try over on the various hackintosh forums you may have more luck there.

@sibliss , I gave up on getting the USB media to boot from Clover. (for now)

I installed Win10 on an empty SSD, then started it up, prepped it for UEFI using (bcdboot C:\Windows /s C: /f uefi) (same way I got my Win10 on my SSD (MBR) to boot from Clover menu), ran Sysprep, cloned it to the empty NVME drive (tried both GPT/MBR). No luck. Booting into the system reserved partition just freeze the computer when on MBR, and gives me the good old boot0af:error when on GPT. Choosing to boot into the EFI windows partition gives me a Windows Recovery light blue screen with an error saying my PC needs to be repaired, and that C:\Windows\System32\winload.efi is missing. Except is it not, the file is definitely there.

So Clover is able to boot my old Win10 from my SSD (MBR), Clover is able to detect sysprepped Win10 on my NVME drive (MBR/GPT) but unable to boot it.

I thought the cloning should work, even if more work. But now the opposite, cloning even more work. And does not work. Maybe best to find out how to boot from USB install media. But how... :(

Spent two whole days on this now. And I fear I have many more to come before this is working. If ever...

Today I also tried booting via Clover; the sysprepped SSD which I installed a fresh copy of Win10 on (and made the clone copy to NVME drive from), just to see how that worked.

Well the booting started fine from Clover, but after a while an error message popped up declaring that "Windows setup could not configure Windows to run on this computers hardware". That is strange since the install was made on the same computer. Anyway, this leads me to the fact that; even if did get the Win10 cloned copy on the NVME to boot from Clover, I would likely be face with this same error.

I am guessing it could have something to do with how Clover is setup. Since Clover is emulating UEFI BIOS. I have no idea how to pursue this now, but will try to do some more research.

For those of you who have cloned the win10 install onto the NVME drive, what was your procedure? Clone whole disk, or only partitions? What software used? Did you get the NVME drive to boot without adding bcdboot mod? (bcdboot C:\Windows /s C: /f uefi) What clover version used?

ArcticLight

"Windows setup could not configure Windows to run on this computers hardware"
This can mean few things :
1) Not enough space to create necessary hidden partitions or copy installer files
2) Installer drive wasn't initiated via Clover EFI, but via BIOS/Legacy

For Clover to boot your Windows, you basicly need a EFI partition (the one usually created as hidden one during installation, you have to copy files from that to a seperate partition on your NVMe).
I did not tested this with hidden EFI partition files dropped on OS partition (can't say if it can work).

Windows needs to have UEFI files/support (of course).

I got it working, finally!

After having tried so many things, I exited Clover menu (on my allready running SSD Clover install), and entered UEFI "Boot Maintenance Manager", and "Boot From file", and then chose my USB stick, and entered EFI/BOOT menu and entered the file boot64x.efi. Voila! The USB stick booted using EFI and I was able to install onto the NVME drive.

Getting good speeds on my old system. 1800MB/s read 1600MB/s write.

So a good tips for those running into the boot0af:error when trying to load the Win10 USB stick from clover, is what I did:

1. Exit Clover (bottom right menu)
2. Boot Maintenance Manager
3. Boot From file
4. Choose your USB stick
5. Choose EFI/BOOT/boot64x.efi

Voila!