Zitat von noInk im Beitrag #480

---

@Troika
This shouldn't happen if you make the USB directly with the MediaCreationTool.
Thanks for the report.

---

@Troika
I understand but RUFUS is a third party software with boot injection capability which doesn't make a standard layout, can't check on each release.
--
To make the ESD-USB appear in REFIND |
connect the USB key after the REFIND menu is visible ( if you can't reach it: the DUET key could be faulty and should be made again ), hit ESC and select the boot Fallback boot loader from ESD-USB to bring on the UEFI WIN10 installer.
--
Unless you can work out the issue by yourself, you better to stick with CLoVer cause DUET won't issue a reset at anypoint during the boot.
Also, I just made an WIN10 1903 USB stick with portable RUFUS 3.8 and the REFIND GUI boot the installer just fine once selected on mine legacy X58.
--
Since the issue might be related somehow with either the memory, or GPU or both's and kinda hard to get without the affected component.
attached an updated build with extended support for native GPU resolution (external card) which would probably still crash or stuck on certain hardware.

Efildr20_30092019


HOW TO USE
Replace manually the Efildr20 on the know to working DUET USB.

Hello to all!
Your UDK2019/2017 works great (on my spec).
Everything below is for interest:
Tried to change Your rEFInd Boot Manager (version 0.11.2 from UDK2019) -> to version 0.11.4 (from official site - https://sourceforge.net/projects/refind/files/ ) by replacing file
x:\EFI\Boot\Bootx64.efi (in DUET2019 USB flash) -> to refind_x64.efi (from refind-bin-0.11.4.zip \refind-bin-0.11.4\refind\ ) -> and renaming refind_x64.efi -> to Bootx64.efi
It's working! But.. using the keyboard only -> mouse pointer is not visible (( & but mouse keys respond -> so mouse working.. may be mouse icon - mouse.png (?). I've tried:
- change refind.conf for using not "Minimal theme" (icons) and something more;
- refind_x64.efi version 0.11.3 from official site -> the same problem ((
- refind_x64.efi version 0.11.2 from official site -> working good, but size of
refind.efi (declared version 0.11.2 from UDK2019 .zip, 189824 byte) =/= refind_x64.efi (version 0.11.2 from official site, 222024 byte) - Why? )) is it your own compilation?
Versions 0.11.4&0.11.3 have some bug-fix - http://www.rodsbooks.com/refind/revisions.html but if these versions (0.11.3/0.11.4) do not work good for everyone and therefore you left version 0.11.2 in UDK2019 -> I am in any case satisfied! Thank You!
PS. Maybe someone will check it on their hardware?!

Specs:
CPU: Intel i7 870
M/B: ASUS P7P55 WS
RAM: 16Gb DDR3 (4Gb*4, Samsung)
GPU: Gigabyte GeForce GTX 560 (1Gb GDDR5)
Mouse: Logitech RX1000 (USB)
Boot Drive: SSD Samsung EVO 970 Plus (250Gb, NVMe) & Intel 535 (120Gb, SATA)
OS: Windows 10 Pro х64

@Glu

The 11.2 custom build of REFIND included within the package on the first post implement some functionality changes (see change log) to speed up the responsiveness.

Hello all

Just joined the NVMe club my head on a wall...
Two months of attempting an windows 7, old hardware, and NVMe boot drive.
Clover, Duet, DELL install method (looks promising to clone using their software...), hunting down the ever-elusive win7 NVMe hot-fix updates, GParted the MBR into GPT, bumping into 007, reading the guides here (thanks a ton),
messing with startup.nsh, hunting down post Samsung 950 pro/sm951 achi >(MZHPV256HDGL) < part numbers> Kingston, HyperX Predator achi (SHPM2280p2)} Samsung driver for a modern 970 NVMe which exist only within an .exe file. While the 970 evme is waving at me...you can see but not touch me with an win7 install, ha ha.
Name it, I failed at it with Win7 x64. So I gave up on windows 7...for now. I am going back to attempt DUET with windows on the same multi-partition usb stick and go back to the dell win7 method after mid-term next week and I have three big tests this week.

I have successfully DUET usb an install of windows 10 onto a Samsung 970 evo plus, today...
So I know it will be just a matter of time to figure out the driver Win7 install issue. Perhaps figuring out the windows 10 nvme driver, that I think I have located to Nlite slipstream into my next win7x64.iso attempts.
Notice the screen shot on the left and the note I made on the right for the drivers that worked for windows 10, perhaps these drivers can be of use for a windows 7 install?
I was thinking that the Microsoft generic nvme > stornvme.inf < for windows 10 should be within the DUET efi\boot\driver folder?
Like 007 I have a plethora of old hardware to resurrect for some HW.bot hardware master suicide runs over the upcoming holiday break.

I am stuck, I followed the excellent youtube videos and after the windows install, i remove the rufus disk and leave it duet. It does not see a boot drive. I have tried every step multiple times. I have a HP z820 and a Samsung 970evo.

What do you mean it does not see your duet? That HP Z820 is a fairly new machine so it should be able to see USB drives just fine, especially bootable usb drives. But why would you be using duet on a new machine anyway? That machine is already UEFI compliant in the first place. So I'm not sure why you are here???? This DUET forum thread is for much older machines that are NOT UEFI compliant. You HP Z820 can already see that 970 EVO perfectly OUT OF THE BOX.

There is no uefi boot for drives in the z820 see https://h30434.www3.hp.com/t5/Desktops-A.../5974633/page/6

I did get it working by

1. coping C:\duet\EFI\NVME\NvmExpressDxe.efi to my duet drive \EFI\Drivers\NvmExpressDxe.efi

2. modifying the startup.nsh to be

echo step1
connect -r
set -v efishellmode 1.1.2
map -u
echo step 2
load fs0:\EFI\Drivers\NvmExpressDxe.efi
echo step2
map -u
echo step3
fs1:\EFI\boot\bootx64.efi

Zitat von laconic im Beitrag #488

---

There is no uefi boot for drives in the z820 see https://h30434.www3.hp.com/t5/Desktops-A.../5974633/page/6

I did get it working by

1. coping C:\duet\EFI\NVME\NvmExpressDxe.efi to my duet drive \EFI\Drivers\NvmExpressDxe.efi

2. modifying the startup.nsh to be

echo step1
connect -r
set -v efishellmode 1.1.2
map -u
echo step 2
load fs0:\EFI\Drivers\NvmExpressDxe.efi
echo step2
map -u
echo step3
fs1:\EFI\boot\bootx64.efi

---

No worries just wanted it documented for the next person

NoInk and Sk0rPn

Thank you for your excellent work on this subject. I used Clover to boot my NVME drive on a Dell Optiplex 9030 which has UEFI BIOS but doesn't boot NVME drives. I then stuffed up my OS drive and I have Windows 10 problems which can only be resolved by reinstalling Windows 10. I tried doing this, but I think because of the Clover boot method, the reinstall fails. The Windows reset method also fails.
I ended up cloning a working Windows 10 installation onto the NVME drive and in doing this I lost the ability to boot via Clover.

My question is can I use DUET/Refind to boot this existing Windows installation. I created a Refind boot USB and all I can do is go into the EFI Shell which shows the NVME drive. I have no idea whether I can edit anything from here so that Refind finds the existing installation. Before I keep researching I though I would ask the experts to see if this is even possible. Thank you for your help so far. This is an excellent resource.

Regards, Wayne

@WayneFB

If a recovery environment is accessible it should be possible to recreate the EFI partition or fix the EFI boot record, else from the USB OS installer launch the recovery environment or just re-install.
To do manually additional EFI software and partition driver must be provided. See PROPRIETARY FILE SYSTEM notice on the first page.

Hello Guys

someone can help


pc reboot when usb boot starts Mesage "entering dxe - duet udk2017"

Pc Z800 CPU 2x X5680

@bloodfor

I have read that people were able to use the 2015 release on the z800 by flashing the latests bios and configuring accordingly their setup by enabling/disabling some bios option etc, except than that, I'm no able to give support to specific type of hardware or bios configuration. So, make sure the WIN10 installation media is x64 UEFI (not legacy) and let us know in case of success.

thank you was successfull

ram does not see, but

48 gb ram sees 3 gb =(

seeing bios ram