unfortunately no legacy beavis.
this is very bad.

-use a usb drive with nvmexpressdxe.x64.efi on it to install this with efi shell.
-bootx64 and windows will finish the installation.

I do not understand these steps, please help me.

you must approach the usb drive with the efi shell entering fs0: in my case and then enter load nvmexpressdxe.x64.efi. (I renamed it to nvm.efi in my case)
this will install the driver.
after that you do map -r
now the samsung appears and due to mapping it is fs0 so the USB is not fs0 anymore!
enter bootx64 and it boots.

Finally, it works, [SAMSUNG EVO 960 (pcie X4) + AMD M5A99X EVO r2.0 + FX 8320e] but not with your driver, use this NvmExpressDxe-64 (Extracted to CLOVER), your method is a very simple and fast way to run the M.2 . Thanks for everything.

Zitat von voideater im Beitrag #8

---

Yup. Ended up with an USB stick plugged in that got DUET UEFI shell and a startup-script that loads the NVMe modoule and then boots the OS from the 960 Pro. Not optimal, but don't se any other way as of now to solve this without having a stick plugged in for booting up the system. At least I don't reboot so often, so it's not a big hassle to either let it be plugged in at all times or just plug it in when I need to do a reboot.

---

Reviving an old topic, Because I use this today, and its working like a charm. I would like to include more information, for those in the future to use and maybe the OP can add it to the tutorial.

in addition, you can create a script, called startup.nsh
open in notepad.
copy and paste this
echo off
fs0:
load nvm.efi
shellx64


save and place inside folder efi/boot/ on your permanent usb bootdisk


when it loads the next shell
i made another startup.nsh using the "edit" command
and put in 2 lines
cd efi\boot
bootx64

so then i just type startup.nsh and windows loads!

Now my next question, maybe we can get some expertise. I'm looking for a way to boot the USB drive to the EFI shell without having to go into bios :) and having to type startup.nsh

Move USB in boot priorities list in BIOS to first, before any HDD/SSD, would that possibly work to auto-boot the USB?

Zitat von Lost_N_BIOS im Beitrag #16

---

Move USB in boot priorities list in BIOS to first, before any HDD/SSD, would that possibly work to auto-boot the USB?

---

Are you sure you're looking at the hard drive boot list (not, first, second, third device order)? I assume if bootable USB, which it should be, it will boot right to it.
It does this on my end with a efishell Grub setup USB stick, just tested to confirm. UEFI USB device by name has to be set first in boot priority list, not just USB Device by name (Same device)

I have even tried force booting from the drive, it won't boot from the usb, unless i manually specify to load efi from file system, the only other devices inside my PC are 2x 3TB seagates which have no operating system and are also in windows software raid 1. what is the contents of your bootable usb drive

mine has only 3 files

nvm.efi
shellx64.efi
efi\boot\startup.nsh

I know i'm missing something, and its probably stupid simple, and i've even read that you should just have a bootable usb drive with the shellx64.efi in the usb drive, is it suppose to be inside the efi\boot folder? I'll play around with a few more times

Try putting also Shellx64 into EFI\Boot\

Mine works like that, but only with file named bootx64.efi (If it's named shellx64.efi it does not boot, or boots to DOS on the USB if there)
Check your BIOS, when you hover or select the "Boot/Load to EFI" what does it say the filename it's looking for? Name it to that, and put as mentioned above.
All boards differ on this, some look for bootx64, others shellx64, others possibly another name, BIOS usually tells you when you hove that option on the exit screen.

SO I did what you said, it worked!

but still having issues with the startup.nsh

However Thank you thank you thank you!

so now i have 4 files

shellx64.efi (which is probably not needed anymore)
nvm.efi
boot\efi\startup.nsh
boot\efi\bootx64.efi

before i was trying to put shellx64.efi into the boot\efi folder but nothing.

so here is my current startup.nsh file and i'm getting stuck at the map -r it loads so fast that the nvm doesn't load before the map -r command is entered. the stall command isn't working as i believe its stalling loading the driver. so we need another solution, maybe you can help me with this, it is relative to this forum post still.

fs0:
load nvm.efi
stall 5000000
map -r
cd efi\boot
bootx64

as it sits, when i press the power button, it boots into efi, loads the startup script, loads the nvm driver, and fails the map -r command. then i can manually enter map -r then startup.nsh 9 steps down to 2. so close

Great and you're welcome! Glad it didn't end up only working on my end

Does that exact command set work properly when running manually? What if you double or quadruple that stall time, same outcome? How about putting a double stall, or map twice?
I'm not sure how to make it wait longer, other than add more time and I'm not sure if there is a limit to that. Are you sure that's the problem, it's not loading driver fast enough before attempting to map?

Zitat von Lost_N_BIOS im Beitrag #22

---

Great and you're welcome! Glad it didn't end up only working on my end

Does that exact command set work properly when running manually? Yes What if you double or quadruple that stall time, same outcome? No luck How about putting a double stall, or map twice? tried it no go.
I'm not sure how to make it wait longer, other than add more time and I'm not sure if there is a limit to that. Are you sure that's the problem, it's not loading driver fast enough before attempting to map?

---

Maybe, make end of script, call new script that has Map -r by itself? Or can your map -r be put into the startup.nsh? Or, can you somehow directly set the map location for the drive you want loaded?