Hello, my name is Thomas and I come from Germany. I registered here because I can find very little information about booting with Clover in connection with a PCIe NVME adapter in German forums. The topic is probably not widespread in Germany.
Please excuse my bad english. I don’t speak this language very well and so I use Google Translator.
I haven’t read all the posts in this thread yet. It is very difficult for me to understand everything.
I have the following problem:
I created a USB stick exactly according to the instructions described here. I first installed Windows 10 and then W10 started normally via Clover. The system was completely redesigned.
However, it happens very often that W10 suddenly “no longer starts”. I first see the CLOVER boot menu and then only a black screen for about 10 seconds. The computer will then automatically restart and try again. However, all attempts fail.
However, one thing is very strange.
If the computer is in the CLOVER menu, the preset time of 5 seconds expires. If I navigate to another drive with the arrow keys in these 5 seconds (it doesn’t matter which drives / partitions I navigate to) and I want to boot from this other drive, of course nothing happens.
And now the strange …
Since the computer cannot boot from the other partitions, of course, I have to switch the computer off manually (power off).
Then I restart the computer (Power on) and now select the correct partition W10.
Then, and only then, will W10 start.
I don’t know where this behavior comes from.
I have already tested all possible settings in the BIOS, unfortunately without success. I also tested several USB sticks and various USB slots in the computer. Unfortunately without success.
Here are some data about the computer:
Fujitsu m730 Power Workstation, 32 GB Ram, latest BIOS, XEON 2667 v2, Quadro K5000, PCIe NVME adapter, Samsung 970evo 1T, W10 with all current updates
I thank you for your valuable time.
Thomas
@THomas
have you ensured to place the NVMExpressdxe file in the correct places on the usb as mentioned in the updated link at the top of the first post ? you are required to always boot from the USB.
@sibliss
Hi, yes, I hope so. NVME file (NvmExpressDxe.efi) is in following folders.
Boot_Stick:\EFI\CLOVER\drivers\BIOS
Boot_Stick:\EFI\CLOVER\drivers\UEFI
Thank you very much
Thomas
@THomas
i would also try copying the driver this this folder it will do no harm
Efi\CLOVER\drivers32uefi
you may also like to run some repair utilities from within windows it seems that perhaps the windows bootloader needs fixing.
you could try tools like
Bootrec /fixboot
Bootrec /rebuildbcd
they may help, i will generally also advise doing an SFC /scannow aswell
beyond these though the issue must be in the clover config.plist somewhere it is hard to say what you will likely need alot of trial and error to figure it out.
@sibliss
Many thanks for your help. I just searched the "Clover_Stick", but I do not find a folder with the name "drivers32uefi"
Thomas
@THomas
if you read the additional and updated information i had pinned to the first post you will see that i did say you may need to create it if you don’t have it.
Oh shit, I probably didn’t read that.
I just saw that this note is at the top of Post #1.
I have now created both folders and copied the NVME file into these folders.
Until now, restarting the computer works fine.
I would like to thank you very much for your advice and your time. Thanks. You have helped me a lot.
Thomas 
Hello
MB: M5A97
disk is gpr
I followed the first post and the latest revision to add the driver into the drivers32uefi and drivers364uefi folders.
Somehow I cant start clover in uefi mode (I just got a black screen) so I used legacy clover.
if I use “Boot Maintenance Manager”->“Boot from file”->efi/boot/bootx64.efi I can install win10pro on my NVMe SSD with an adapter till the first restart. Then it boots back into the clover and won’t boot/find windows.
Maybe someone has an idea?
@temm
I would advise to place the driver in all 3 of the uefi folders anyway as it will not harm the configuration in anyway.
The use of legacy clover is perfectly fine for our purpose as once we hand of to the windows bootloader it will do it’s own thing anyway.
normally not being able to see the nvme drive in clover is because the driver is not being loaded correctly or the drive is not formatted correctly as you’ve already stated you are already running gpt i suspect driver.
Please note you can of course manually edit the clover config.plist further to change various clover behaviors such as which drives to show under clover and which ones to hide.
Hey guys! Just a little question 
Usbkey should I always keep inside?
What do you mean with "inside"?
attached to the usb socket😅
Hello everyone, need some ideas/help with NVMe boot.
Hardware:
Asus P6T Deluxe V2 (X58 with legacy BIOS only)
Samsung 950 Pro (Adapter M2 -> PCIe) - can boot on legacy (BIOS only) boards.
950 Pro can be set as bootable in BIOS; Win10 install directly on 950 Pro works fine and Win10 can boot from it w/o any issues.
After that -> GPT -> Clover with NvmExpressDxe.efi in both Efi\CLOVER\drivers\BIOS and UEFI.
If trying to boot from NVMe - it’s resetted (reboot) in 1-2 Sec (black screen, ther is no kinda [error] message)
Right now runs only with a workaround: boot Clover from ext. USB (very slow) and than can choose a bootable partition on 950 Pro.
Same Clover on 950 Pro can not be loaded (w/o an “external” help like USB).
Tested Clover from 4988 till latest one, tried Clover options boot0af/boot0ss and BiosBlockIO/SATA.
Are there anything more I can try to get rid of ext. boot USB with Clover and be able to boot Clover on 950 Pro?
Thanks for your ideas/help in advance!
@crystal
@Lantan
as stated at the start of this thread…
so yes the usb stick is always required because you install clover to the usb stick, unless you install clover to a separate dedicated sata drive.
clover must be installed to a device the bios can boot (typically a usb stick or a sata hard drive). this is because the boot process is to first boot clover from the legacy device such as usb stick or sata hdd, clover once booted then detects the nvme drive and calls the windows bootloader on the nvme drive to boot into windows… clover cannot boot straight from the nvme and canot boot without legacy device like use or dedicated sata hdd.
Thank you for this !
@sibliss u have been very helpful!
in a second moment I will try to modify the bios and start from pcie without usb! do you think it’s easy for me?
@lantan
Sorry for asking, but
what is the purpose to install Clover, if the 950 Pro can be selected as boot-drive?
@sibliss : thanks for clarifying, means no need to try/search further
@Thiersee : multiple boot with some options (kinda extent of legacy BIOS to UEFI)
That’s the point: if you installing a Win10 only - you don’t need any boot help (like ext. USB): select as a boot drive and Windows can boot from it.
My hope was, that Clover (like a swiss knife) can handle it.
Regards,
Lantan
i prefer boot from sata! 
Can i set timeout “0” ? or “1” is best?
a good idea is to delete the letter from the disk manager so as not to see anything on "computer" 