Yeah I think if you referring to what I think then I have tried it a few days ago.
autoload startup.nsh
fs0:
load nvm.efi
fs:\1.nsf

new file called 1.nsf with

map -r
cd efi\boot
bootx64

I may end up exploring a boot loader option and closing the 30 second gap to 1-2 seconds or instant load off a boot loader option(s) Going to have a buddy help me, if hes not too busy. Hes pretty familiar with it.

Yes, I meant something like that, I'm not too good at this kind of thing, surely there is a way and a good answer! I bet the team over at stackoverflow can help! https://stackoverflow.com/questions

hey, I have a dubt...every time I have to insert usb with clover to boot win10 from m.2 nvmE or just the first time Have I to use clover (following that guide) and the next times win10 boot automatically from nvmE drive?

@toonamix - I have not used, but I believe you have to leave it in there or create a similar partition on your SSD (or another internal drive) and then correct things so it knows where the new location of the clover files is located,

Zitat von z820man im Beitrag #13

---

Trying to get Windows Server 2016 to install on an HP z820 workstation using Clover.

The following things don't work:

Default: Windows server 2016 thumbdrive boots, finds the Samsung drive but refuses to install to it ("Your system doesn't support booting, enable driver in BIOS')

Modding the BIOS as described elsewhere on these forums-- modded BIOS won't flash (presumably because unsigned.)

Clover method: Using method described in this thread, including the NVME driver, the system will boot to Clover and load the driver; BUT
the USB thumbdrive for Server 2016 doesn't work: Clover only recognizes "Legacy HD1", which appears and disappears like my thumbdrive, but attempting to boot it only displays a (grey, non-Microsoft looking) Windows logo and hangs. Changing USB ports (2/3) makes no difference. FWIW, the USB is NTFS formatted because it has to be based on the size of the files on the iso.

I did find one post mentioning that DVD boot works using this method and tried it (with a Win 7 DVD): that seemed to work: Clover could boot the DVD (I didn't actually install the OS). The windows server ISO is too large for a DVD though (5.2 GB > 4.7).

HP zX20 workstations are common and so are Samsung 960 Evo's-- I can't be the first to encounter this. Any advice much appreciated.

---

Hello everyone and many thanks to Fernando and all the participants who help us.
In fact.
I have an old Asus Rampage Extreme 2 motherboard now. And I bought the Samsung 970 Pro 512 GB (a few days before I bought the Plextor M9Pe (Y) 256 GB and handed it back because I couldn’t make it a boot disk. At that moment I only found out about the existence of this resource. and tried to change the BIOS, but as it turned out to be impossible for me with this motherboard).
I studied three starting branches for a week
NVMe Support for old Systems
and eventually tried as recommended here.
The only thing I did was boot the USB method
HOW to MAKE THE USB flash drive (bootable) for DUET.
from this thread
[Guide] NVMe-boot for systems with legacy BIOS and older-UEFI (DUET-REFIND)
I copied to it Nvm.efi from here.
After that, I booted from it, went to the EFI shell and downloaded Nvm.efi. After a successful boot message, I typed exit and ended up on the start screen of the bootable USB. I went into the boot manager and chose to boot from the EFI CD drive.
Download and install Win 10 on SSD. After unpacking and installing the files and after rebooting, the EFI Win10 icon appeared in the startup window of the bootable USB. After pressing it, the installation continued with a successful end.
Thank you very much.
So now, the Win10 boot process from ssd is next. I boot from usb, choose EFI Win10 icon and continue.

Zitat von tele2 im Beitrag #1

---

there are still a...
here I boot windows with the help of a USB drive with the nvmexpressdxe.x64.efi on it.
No other drives are attached other then the samsung 960 NVMe and the USB drive with only nvmexpressdxe.x64.efi.
the USB drive I take off directly after loading the driver.
.....EDIT by Fernando: Thread stickied and title customized

---