Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
EFI Boot Option Not Working After Cloning SSD
#1
Hi everyone,
I recently cloned my Windows 10 system from a SATA SSD to a new NVMe drive using Macrium Reflect. The cloning process completed successfully, and I can see the NVMe drive listed in the BIOS. However, when I try to boot, it just skips to the old SATA drive unless I manually select the NVMe from the boot menu.
I used EasyUEFI to check the boot entries, and I noticed that the EFI boot option for the new NVMe wasn't automatically created. I tried manually adding it, pointing to the correct
Code:
\EFI\Microsoft\Boot\bootmgfw.efi
file, but it still won’t boot unless I use one-time boot selection.
Has anyone run into this before? Is there a better way to create a proper boot entry for a cloned NVMe system using EasyUEFI?
Thanks in advance!
Reply
#2
(07-10-2025, 09:08 PM)johnhsmith Wrote: Hi everyone,
I recently cloned my Windows 10 system from a SATA SSD to a new NVMe drive using Macrium Reflect. The cloning process completed successfully, and I can see the NVMe drive listed in the BIOS. However, when I try to boot, it just skips to the old SATA drive unless I manually select the NVMe from the boot menu.
I used EasyUEFI to check the boot entries, and I noticed that the EFI boot option for the new NVMe wasn't automatically created. I tried manually adding it, pointing to the correct
Code:
\EFI\Microsoft\Boot\bootmgfw.efi
file, but it still won’t boot unless I use one-time boot selection.
Has anyone run into this before? Is there a better way to create a proper boot entry for a cloned NVMe system using EasyUEFI?
Thanks in advance!

Have you set the newly created boot item as the priority boot option? Maybe you should try disconnecting the SATA SSD and just keep the NVMe.

Or try our cloning software:
https://www.easyuefi.com/disk-clone/disk...-home.html
Reply
#3
“Hey @johnhsmith, I’ve run into the same issue before after cloning to NVMe. Disconnecting the old SATA drive completely during first boot often forces the system to pick up the correct EFI entry. Also, double-check that your BIOS is in UEFI mode, not legacy. Hope that helps!”
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)