@murat0606

I cannot guarantee any specific compatibility with anything.
If you want to see if there are chance to get UEFI with your board and CPU make the USB with DUET-REFIND and see if you can reach the graphical manager.
If you see something like in the below image then try to install WINDOWS 10 on some spare drive\disk\device in UEFI mode to check on board and CPU incompatibility with the OS.

OK thanks, I'll try.

Hi I'm new to the forum!

Maybe someone can help me over here.. Pulling my f*ck hair and smashed USB sticks.. I have a Gigabyte GA-EX58-UD5 and have bought an Akasa M.2 SSD to PCIe 3.0 Adapter and a Samsung 970 evo plus NVME (500GB) in hope of greater speeds.

I put the Akasa in a x4 slot and the NVME drive showed up in Windows 10 64-bit which made me smile a lot. Benchmark were superb on NTFS aswell, very well acceptable 1600mb/sek read and write for this setup and old mobo.. so I finally cloned my original Samsung SSD 850 to the NVME and have since tried booting from it. The original SSD is disconnected just to make sure.

I tried both Clover and Duet on a Cruzer USB stick. I've tried Duet 2017 and 2019 and different versions of NvmExpressDxe.efi. I don't find anything with "64" as people write about however, anywhere? I haven't seen NvmExpressDxe-x64.efi in these packages? I've downloaded the latest Duet and Clover aswell as BDU.

Clover finally showed the NVME drive when I had NvmExpressDxe.efi loaded (when I read instructions enough to put the file where it belong in the folder), but when clicking the OS it just went to a blinking black screen.

Duet 2019 version sometimes gives me "MD5 Error Mismatch" though I use the -disablemd5 switch running as administrator. Very very strange.

So my question: Is it even possible to get a NVME Samsung 970 Plus to boot on a GA-EX58-UD5 in any way or form? Anyone have done this? This is a legacy non-UEFI mainboard for those that now know - I'm running it on a 3.8GHz CPU and 24GB RAM and mainly doing music.

Or will I have to go back to the original SSD and use the M2 970 as a secondary disk?

Thanks!!
Bankas85

@Bankas85

On the first page download the 2015 version and follow it's tutorial, if it work you can try to use newer 2019 version, if doesn't try to change USB or make it again from the beginning.


HOW to MAKE THE USB flash drive ( bootable ) for DUET.

Booting the NVME drive from non-UEFI legacy board - DUET with optional REFIND - with USBSetup:

Thanks for replying!

I'm sorry but I simply cannot install Windows 10 64-bit once again.
This disk is full with music applications, licenses and configuration that I use for my work as Spotify artist and Youtuber.
The music libraries are also linked to a larger 2TB drive with sampling applications, plugins (VST, VST3:s) and more.

Zitat von noInk im Beitrag #634

---

To convert a pre-existent WINDOWS 10 MBR to WINDOWS 10 GPT you must run it\'s MBR2GPT utility.

---

@Bankas85

After successfully launching DUET you should be able to convert or repair the cloned NVME by using the WIN10 ESD-USB installer CMD\troubleshooter\recovery environment - see the "repair your computer" option under the big "install now" button.
Some board will auto-boot the legacy installer and require to attach the WIN10 ESD-USB installer after the UEFI environment is loaded, you'll notice the environment once within the REFIND graphical menu.
Within the REFIND graphical menu attach the WIN10 ESD-USB and refresh the USB list by hitting the ESC keyboard KEY to make the "Boot Fallbcak boot loader from ESD-USB" option appear.





I'm unable to guide you further since your data is your issue and I won't be responsible for any losses, if all of this is too difficult see @docdude post about cloning directly in GPT
Once you done with the MBR-to-GPT utility probably you can "install-in-place" anytime over by keeping the application and files.
The 2015 version might be more compatible but slower.

I've removed the 2017 link from the first page since anything should has been back-ported to the 2015 or included in the 2019 version.

I'll leave it here:

• OLD download link for DUET (UDK2017) with REFIND included - it was for an X58 ASrock.

Thanks alot for all info!

However:
I converted the disk to GPT using Easeus Partition Master and did the WIN-EBD installation to another USB stick. And it worked as expected. The NVME disk was listed as GPT under Disk Management afterwards.

However I can't see the disk identified in either DUET or CLOVER, only the Win-Ebd USB is the choice to boot and it doesn't see the drive. I tried several different versions of NvmExpressDxe.efi aswell. I can see that it is loaded by the system by typing "drivers" and going through the list. There is also a list before which states a GPT-drive. But it's not listed like the way a drive is listed in your picture.

I have looked for later versions of the NvmExpressDxe.efi aswell but haven't found anyone later than a one dated dec 2017.
This is a Samsung 970 500GB NVME Plus. However I still think it would work booting from it somehow since Windows 10 can see it when I boot from the original SSD. I must be doing something wrong?

Thanks again for all help!

@Bankas85


First page doesn't cover how to convert a pre-existent WIN10 installation from MBR to GPT for a reason.

With either diskpart or mbr2gpt if misused all your data could be lost.
See mine previous post directed at you and while there only the NVME drive attached boot the WIN10 ESD USB in DUET to the first full available CMD and type this:

MBR2GPT /convert /disk:0 /AllowFullOS
 
 

Where disk 0 is the NVME drive (see the diskpart & list disk and volume command on the conversion example)
If for some reason you cannot do it within the preinstallation environment, you can run the command on a live system or an WindowsToGo USB drive. Just be sure to select the NVME disk.




Anyway you shouldn't mix the DUET USB with the CLOVER USB or vice versa or use third party tool's made in specific for one on the other, if there are any.
If you are using DUET and you are sure the NVME is already GPT download and make again the DUET USB by following the how-to and don't change it's file. DUET has it's own NvmExpressDxe EFI driver.

Many thanks!

I finally got it working. I had to do it the following way since MBR2GPT had some kind of issues with my current version of Windows 10 (v1903) when I tried converting the NVMe disk. MBR2GPT always said, no matter which version or WinPE loaded (v1903 or other version, either from USB WinPE or from within Win10 OS as Administrator):

MBR2GPT: Attempting to convert disk 0
MBR2GPT: Retrieving layout of disk
MBR2GPT: Validating layout, disk sector is: 512 bytes
Disk layout validation failed for disk 0
MBR2GPT: Conversion failed

And I also had "MD5 Some files are missing" errors on DUET 2019 when I tried running the USBSetup as Administrator. It was always the same with the DUET2019 by some reason, downloaded it several times - put it into other folders in case of UAC/security issues or such.. I couldn't use the CreateUSB CLEAN console command from DUET 2019.

So I ended up doing this.

First of all to got the disk converted from MBR to GPT properly and kept all the data (I cloned the old SSD to the Samsung NVMe using Macrium Reflect from within Windows 10 on the old SSD) I downloaded Easeus Partition Master and created a bootable WinPE EaseUS USB disk. Read more here if anyone feel the need to: https://www.easeus.com/partition-manager...on-manager.html.

I booted the Easeus USB PE with only the Samsung 970 Evo Plus 500GB NVMe attached and chose the whole disk in the list and selected "Convert to GPT". I clicked "Apply" and it completed successfully within 10 seconds.

Since I got MD5 "some missing files are missing" errors when trying to run the USBSetup.exe of DUET2019 (while still using the -disablemd5 switch to ignore any md5 errors) - I went into the DUET2017 folder and performed the CLEAN from the USBSetup.exe (GUI) there and exited. I then opened up the command prompt as administrator and I went to the folder with DUET2019 and issued these commands:

CreateUSB FORMAT
(I then disconnected and connected the USB flash drive again as instructed by DUET)
CreateUSB DUET
CreateUSB REFIND

After this, I rebooted and the NVMe drive showed up for the first time in DUET and it booted up from DUET. No need for startup repair or anything.

Read/write speeds now from CrystalDiskMark 6.0.2 x64 are, Seq Q32T1: Read 1802.8 MB/s, Write 1614 MB/s (the old Samsung 860 EVO SSD was had read speed about 250 MB/s)

Hardware used if it helps anyone:
Gigabyte GA-EX58 UD5 (i7 920 @ 3.8 GHz, 24GB RAM)
Akasa M.2 SSD to PCIe Adapter card fitted at the PCIe x4 top slot of mainboard
Samsung 970 Evo Plus NVMe 500GB Drive
Old SSD: Samsung 860 EVO
Windows 10 64-bit v1903

Many thanks to noInk for help on this issue!

@Bankas85

Thanks for reporting back.
I'm not getting that error on the current 2019 version.
Maybe some file used by the process were missing from your system.
Can you run anyway the 2019 USBSetup.exe from the command prompt with the following case-senstive switch:

USBSetup.exe -GenDirMD5
 
 

On the newly generated MD5.txt you should find those line:

17087ebbab4bacc93bd62b983982991a Binaries 
2dd87bbe0a96bc73882ff8686fa8d8e8 BootSector 
19e6e690cc2bdbb6d17e89ad73cffa03 EFI 
3f8358f5cdc5004d919141366cabde63 Efildr 
a05972dbf549d0371e3a8afd3203db8a Refind 
 
 

Those MD5 should be the default for the 28-10-2019 DUET version

Hi! I did it. But I did get this MD5.txt file instead (by DUET_UDK2019_REFIND.zip linked in the thread):

17087ebbab4bacc93bd62b983982991a Binaries
2dd87bbe0a96bc73882ff8686fa8d8e8 BootSector
ae1de7b9cb236aef25b3d2d2d48be63e EFI
3f8358f5cdc5004d919141366cabde63 Efildr
b9f330056a258f6aa63ab0489d2f7827 Refind

@Bankas85

That's not the MD5 of the 28-10-2019 DUET content available on the first page.
Download again and check the location on which you are trying to download or unpack the archive in a new folder or see if something is modifying the files.

• Current download link for DUET (UDK2019) with REFIND included

Hi again!

Opening MD5.txt inside the DUET 2019 archive the MD5:s are the same I can see.

However.. If I do a "USBSetup -GenDirMD5" on DUET2019 (cmd/admin) it gives me this other output of MD5.txt:

17087ebbab4bacc93bd62b983982991a Binaries
2dd87bbe0a96bc73882ff8686fa8d8e8 BootSector
19e6e690cc2bdbb6d17e89ad73cffa03 EFI
3f8358f5cdc5004d919141366cabde63 Efildr
b9f330056a258f6aa63ab0489d2f7827 Refind

The MD5 for Refind changes. This output is also true when I test on Windows Server 2019 and other systems aswell, with both 7zip/WinRAR.

Might be some old string in the GenDirMD5 function? Just to help out :)

@Bankas85

YEa, nope. Should be the one I've posted.
Are you manually modifying something in those directory except for extracting the archive from the DUET_UDK2019_REFIND.zip?
The current MD5 for the 28-10-2019 DUET ZIP archive is: F633378448C9EA4648E268311A6A23F0

The case-sensitive command line parameter to disable the MD5 check is:

-DisableMD5
 
 

But if you are starting from a non-working prospective, try first to use it without modifying anything.