[Guide] NVMe-boot w/o modding the BIOS (Clover-EFI method)

I format each the target disk drive before starting the OS installation.

I want to add that yesterday I used Clover (BDUtility.exe) from the website:

but without success…

Today I used the experience of your colleague AUTHOR Morbius #833 - also without success.

@Edmundas-PC
There is no need to use the Clover method to get Win11 properly installed.
Look >here<.

Hi everyone!
After successfully installing a Samsung 990 4TB Nvme M.2 SSD disk in Win7, thanks to the drivers listed here and the help of Fernando! I’d like to be able to run my actual Win7 from the new fast ssd so this is what I did:

  1. I cloned the OS to the new disk using Macrium and in the end of operation it converts disk from MBR to GPT to have the whole 4TB available. (cloned 2 times thinking something was wrong but no, all seems OK with cloning…)
    After that I can see the disk listed in Device Manager as Nvme and I also have the correct Samsung Storage controller listed. The disk is now fully usable as storage!
  2. to try boot from it I’ve downloaded Clover-5161-X64.iso and create a bootable USB with Rufus, then placed the NvmExpressDxe.efi in the correct folders as explained in many guides
  3. restarted the system and modify the BIOS to boot from USB and then after booting I can see the Clover interface but under Windows logo it is written “Boot Windows from Legacy HD1” and many others HD2,3,4,5,6… and of course when trying to boot I just got the blinking underscore and nothing happens.

So… the problem/question is: should I manually create an EFI system partition in the new disk? in the beginning of the (new) cloned WIN7 OS? or it’s a non-sense and the problem is much bigger???
It seems that most of the guides and cases are for installing a new OS in the PCIe Nvme Disk but in my case the system is cloned from an existing Sata III SSD.
If I have to create that partition, something like AOMEI Partition Assistant can be a good option? and I won’t lose the data/OS in the ssd? I saw some guide and it seems safe but…

Thanks a lot if someone have some suggestion on how to proceed!

EDIT: Should I maybe “Convert Windows Installation from Legacy to UEFI” like explained on this post in superuser-com?

Still fighting all the day with this… :///
I think that finally the problem is that Macrium created the clone of WIN7 and well converted the MBR to GPT but the clone is finally wrong because in the conversion from MBR to GPT it does NOT create the 200mb boot record needed for UEFI boot!
I think I finally understood whats going on… but a confirmation from YOU! experts would be great!

Now I did manage to create a FAT32 200mb partition and just need to make it UEFI bootable… to be in the middle between CLOVER and my WIN OS installation, right???
I feel to be so close to the solution… just missing the last step!!!

Thank if someone can put a word on the subject!!!:slight_smile:

Not much knowledge about clover, but since Windows connects GPT to EFI boot and you changed your filesystem already it seems you want to boot WIndows (assuming a 64bit version) in UEFI mode.

So you need a FAT32 partition for the EFI bootloader/ bootmanager and then you need to rebuild your BCD.

There’s a lot of guides out there. Very often they recommend the automatic recovery, but this often doesn’t work since the EFI partition doesn’t have a driveletter.

Thank you lfb6!
Yep I’m on that point that “just” need to “rebuild the BCD”… on that partition of the GPT cloned OS disk! but unfortunately got to this point and have problems getting the job done to the end!
That “rebuild BCD” seems easy but I 'm finding it really problematic ://
Would need… some straight instructions… do this then this… etc
I’m really so close, I know!!!..

UPDATE: still not solved but I did manage to copy the WIN7 OS from the MBR disk to the NEW one in GPT and now I can see the 200mb FAT32 EFI partition! but still can’t boot from Clover

even if now I have the (probably) correct button that says “Boot Mircosoft EFI Boot from EFI” and another “Boot Windows from CLOVERCD”…
I will maybe try to put the disk UUID in the config file of Clover, as someone suggested elsewhere…

Finally manage to boot!!!
It was a problem related to Macrium NOT actually creating the EFI Partition + the old SSD still attached to the system but I did managed to make a perfect CLONE of WIN7 (but with GPT/UEFI) with Minitool Partition Wizard and the EFI partition is created correctly and after physically removing the OLD SSD from the SATA III port, and booting with CLOVER, wow, it simply started!!! Actually not finding it so much faster in normal operations but probably in long term use I will see the benefits and in any case was needing much more space so it is fine!!!

1 Like

Just have a question about this out of curiosity. If you had the nvme drive encrypted with say veracrypt. Would it work to use clover boot select the nvme then would it bring up veracrypt boot loader to input password?