Windows 10: New NVME SSD - Windows Boot Manager

Hi all - I'm looking for a little bit of guidance.

I have a custom PC (Windows 10 (1909), Gigabyte Z370 HD3 motherboard) and I have just upgraded from a WD 1TB HDD to a 2TB Samsung 970 EVO PLUS NVME.

I used the Samsung Data Migration software to migrate from the HDD to the SSD - all went well. I then restarted the PC and re-ordered the Bios to boot from the SSD first, then HDD, then CDRW. However, when I did this and exited the BIOS, the PC then gave an error message "Reboot and Select proper Boot device". To troubleshoot, I disconnected the HDD and retried - hey presto the PC booted from the SSD no problem!

What I have noticed is that with the HDD connected, the BIOS lists the HDD as "Windows Boot Manager (WD etc.)" but the SSD just as the Samsung 970. i.e. the BIOS does not recognise it as a bootable device. However, with the HDD disconnected, the BIOS lists the SSD as "Windows Boot Manager (Samsung 970 etc)". What I would like is for both to appear as Windows Boot Manager and then set the order as SSD first.

I could just completely disconnect the HDD but I wanted to have it as a back-up just in case the SSD failed.

Can anyone shed some light on why I can't have both recognised as bootable devices?

Thanks,

Ian

:)

 

NVME SSD

Tried this, and windows still didn't see the nvme ssd. It was a brand new nvme ssd right out of the box. Nothing works.

 

Migrating Win10 to NVMe SSD

I am going to try what you suggested. I just tried using Linux Mint boot cd to hopefully erase the SSD. Unfortunately there seems to be some sort of encryption on the SATA SSD that prevents Linux from managing the SSD. Funny thing is I never used bitlocker on the SATA SSD.

 

Missing Boot record (Error code: 0xc000000e) after cloning OS from an NVMe SSD to a SATA SSD

Hi,

I'm having a bit of trouble following what you have done so far, but might suggest a trick that might work..

Your one picture says Disk 0 is the new cloned drive, but is showing a 256gb, not 1tb... Not a big deal, but I just wanted to make sure what I mention is correct..

Will the machine boot from the 256gb SSD with the NVMe and new 1tb removed ?

My impression is that you are now working with the new 1tb SSD that was a clone of the NVMe, and the NVMe that had the new 1tb SSD cloned back to it..

This is my suggestion that has worked for me in the past, but not always.. The way windows lays out the partitions in UEFI machines can be tricky.. Sometimes just 1mb of free space before the first partition can break the deal..

If your machine boots properly from the temp 256gb SSD, try this.. It will require that you make an image of the 256gb SSD and use bootable Macrium to restore part of it to the NVMe.. I chose the NVMe for this because it is a copy of a copy.. The best original
you have is now the new 1tb SSD..

Remove all other drives before attempting to boot with the NVMe after doing this..

After imaging the 256gb SSD, try recovering it's first Recovery partition to the NVMe and see what happens.. If that does not work, try Recovering both the Recovery and EFI.. If that fails, try all three of the partitions prior to the Windows partition..

If you still need to create the bootable media, don't even bother messing with the WinPE\Re version.. It is a real pain to create, and in my opinion, does not work as well as the Linux version.. The Linux version pretty much ignores any type of Windows fussiness,
and just does the job you request..

BTW.. Another method might be to wipe the NVMe and reinstall Windows... Then once installed and functioning, image the cloned 1tb SSD, then restore the windows partition to the NVMe overwriting what has just been installed..