Go a page back or so and look at my benchmarks.. Speed fault my not be because of what you think.. I get double the score of a SATA ssd on a gen3 x1 slot ONLY when the drive is a slave tested from the system booted from a SATA drive

Not to beat a dead horse, when you say you don't have the same problem have you looked closely at your 4k benchmark scores? Sequential seems normal, my 4k suffers severely

Alright, I guess I'm in need of help here ... been banging my head against this all day yesterday.

First, I installed Clover to a USB stick using BDUtility v2.1.028.
That worked fine, and the stick is bootable.
However, keyboard is not working upon boot.
I switched it to using boot7 instead, and now keyboard works ... but it resets before getting to the Clover menu if I have a CD drive connected!
Alright, I can live without a CD drive for now...

I installed the Nvme driver to both the BIOS and UEFI directories, and made a GPT USB stick with Windows on it.
Booting to clover, clicking any of the device icons just resets the machine.
But if I drop to the EFI shell, I see fs0 (clover stick) and fs1 (windows installer).
manually running fs1:EFI\BOOT\blah does indeed run the Windows installer.
And Windows allows me to install on the NVMe drive (it doesn't if I don't boot through Clover) - success?

Then comes the first reboot ... and it gets me into Clover again.
Still any of the device icons lead to a reset.
And dropping to an EFI shell still only sees fs0 and fs1.

Do I need to do something for it to see the NVMe drive?
Any EFI commands I can use to diagnose if it sees the drive?
(I know the Nvme driver was loaded, but how do I know if it found any devices)?

Map -r in efi shell will map the nvme drive after loading the driver

I don't think it's even seeing the drive.

From digging into bdmesg.efi logs, I see that it DID see the WD SN750 NVMe card during boot:
1:486 0:000 PCI (00|05:00.00) : 15B7 5006 class=010802

It also loaded the NVMe driver:
1:517 0:000 Loading NvmExpressDxe.efi status=Success

But it doesn't see any block devices on it:
6:313 0:006 === [ ScanVolumes ] =============================
6:313 0:000 Found 2 volumes with blockIO
6:313 0:000 - [00]: Volume: PcieRoot(0x0)\Pci(0x9,0x0)\Pci(0x0,0x0)\USB(0x80,0x0)
6:315 0:001 Result of bootcode detection: bootable unknown (legacy)
6:315 0:000 - [01]: Volume: PcieRoot(0x0)\Pci(0x9,0x0)\Pci(0x0,0x0)\USB(0x80,0x0)\HD(1,MBR,0x0D4289F4,0x3F,0xECDFC1)
6:317 0:001 Result of bootcode detection: bootable unknown (legacy)
6:323 0:005 label : BDU
6:323 0:000 This is SelfVolume !!
6:323 0:000 Searching volumes for latest nvram.plist ...

I also tried debugging the "CD drive present = crash" issue ... by enabling Boot/Debug = true in the config file.
But it doesn't create any log file (and boots just as fast as before).

F3 key to access additional WIN10 install options in CLOVER UEFI bootloader

@hobi Post #663 and @swyyt Post #663

Thank you, your WIN10 install tips have saved me :-)
F3 key use to see hidden boot options worked on my old HP PRO 3330 SFF, i5-2400 3.1GHz gen2 CPU, 4GB RAM with a PCIex16 gen2 slot fitted with a generic NVMe PCIe adapter+ 1TB Samsung EV0-Plus NVMe.

@Uxorious Post #738 - you might like to try this...

What got WIN10 to install on the VNMe drive in my old PC was...

All files DLed on the HP PRO

DL Win10 64 bit MS media creation tool, generated iso and used Wintoflash to unpack iso to a bootable USB drive.
USB drive with Clover EFI bootloader generated using latest BDUtility (r5070)
nvme driver from OFF folder copied to BIOS and UEFI folders and 2 new folders named divers32uefi and drivers64uefi as specified by @sibliss.

Insert both USB drives with the EFI bootloader USB and the WIN10 install media
Set Clover EFI bootloader USB as primary in UEFI and BIOS legacy
Booting into Clover EFI bootloader USB gave a few options, arrow key used to move from that selected by default to any other to halt it being auto-loaded on timeout

Removed WIN10 install media USB drive, pushed F3 key a few times, inserted USB drive again and pushed F3 key a few times more (not sure why, but single pushes didn’t, but multiple did, bring up additional booting options including
‘Boot UEFI external from unknown HD’ or something similar specifying ‘external, unknown and HD’
SELECTED this and WIN10 began to install on the VNMe drive…. :-)

Win10 install will shut down PC for a restart to finish.
From memory, in rebooting, I had to leave Win10 media USB inserted, push F3 multiple times to get a bunch of CLOVER boot options, including
1. Boot UEFI internal to EFI
2. Boot Microsoft EFI boot from EFI
3. Boot UEFI external from \
4. Boot Microsoft EFI cdboot from \
5. Boot UEFI external from CLOVER

With Option 2. selected, Win10 install completed without any further shut downs.

From there, set up Win10 as I wanted, new drivers etc and it is bootable from the NVMe as C: drive using the CLOVER bootloader USB drive. Might streamline USB install sometime later. Also think I had to convert the NVMe drive from GPT to MBD for Win10 to install to it, but it’s now converted back to GPT to add more partitions and is working well as the primary drive….

Thanks to everyone here for sharing experiences and knowledge. I hope those of @hobi, @swyyt and me who have needed to use of the F3 key to see hidden CLOVER boot options might help others having similar Windows install problems.

Nice job.
Except for some directories paths incorrect, still works after this time.

@dahert
Yep some might be, or some might be extras due to me pushing F3 key multiple times, I don't really know. I was extremely flustered in this process and just scribbled them down as some sort of reference. Main aim of my post was to reinforce value in using the F3 key to show paths not shown by default, but critical to showing the one needed for Win10 to install to the NVMe drive. Happy for you to correct those paths I transcribed in error, if its important enough.

Can anyone benchmark and compare 4k scores with those found online or from your system booted from a sata volume/OS

Hi thanks very much for the guide. I followed the clover boot method, but I am having issues. I get to the stage of the clover boot and select the USB win installation media and when I do I get a black screen with nothing happens. I used the Rufus tool to put my windows 10 on it and made it gpt, perhaps there is something I'm doing wrong.
Not sure if this helps but I can run windows setup from my media stick and it picks up my NVM drive which I can install it on. Its just when setup reboots it goes straight back into windows setup again.

**Update the poster above who mentioned F3 is correct, this gives you more options. Boot from your USB with windows, and when you go into windows setup make sure you disconnect all other hard drives (well it wouldn't work for me as I was getting cannot create partition etc). Then when setup finished choose the same option as the poster said above Boot from Microsoft EFI and never touch it again!!

Thanks for putting all this together! I am getting close to making it work but need a little help getting across the finish line. I currently have a HDD and an SSD installed on my machine. The HDD has a partition containing Clover which I have no problem booting into. My SSD was cloned from a HDD with a functioning version of windows. I can get into Clover, but I cannot boot into windows. I have five icons to select from: Boot Microsoft EFI Boot from EFI, Boot Windows from Legacy HD1, Boot Windows from EFI, Boot Windows from Legacy HD5, and Boot Windows from Legacy HD6. I have selected each of these options but none of them boot into Windows 10. Is there a way that I can select the boot file on the SSD? What am I missing here?

@rtbcoop
You cannot just clone windows 10 it will never boot. If you read though all the posts in this thread and my pinned post. you will see I have detailed this before.

I'm having issues doing a clean install as well. If I bypass Clover, my windows installer drive loads the installer just fine. If I go through Clover, I have two USB options pop up: Boot Microsoft EFI cdboot from ESD-USB and Boot Windows from ESD-USB. The cdboot option comes up with a message that says "Press any key to boot from CD or DVD" and then does nothing. The Windows option just does nothing. What did I mess up?

I did see the suggestion to try different USB drives. I have tried three different drives and none of them can get me into windows installer.

^^ Same, I get "disk error" or "no mapping returned" on sandisk ultra flair and ultra fit. Trying a solution found by bootmaster400

Zitat von bootmaster400 im Beitrag #668

---

Working! If you run into the error "no mapping returned from cdboot.efi" I recommend trying the DUET-REFIND method (win-raid.c o m/t3286f50-Guide-NVMe-boot-for-systems-with-legacy-BIOS-and-UEFI-board-DUET-REFIND.html)

Pressed ESC to display the Installer USB, and everything installed and booted like a dream. Even works great with Veracrypt!

---