Windows 10: Cloning an m.2 NVMe boot drive to another

Hi All, I have a rather interesting issue and all of the researching and trouble shooting steps have not produced any different results so I'm trying here to see if anyone has had the same experience. Here's what I've tried.

1. Backed up a 500gb nvme m.2 drive to internal HDDs using the windows 7 backup and restore functionality within windows 10.
2. Disassemble PC and install new 2tb nvme m.2 drive
3. Boot off windows 10 flash drive and use troubleshooting menu to restore an image.
4. I select the internal HDD as the source and it automatically selects the new 2tb drive as the source.
5. At the very end, the restore fails. The parameter is incorrect.
6. Clean the new disk and try again. Same issue.
7. Remove the windows 10 flash drive from the PC after loading the recovery instance and then try the restore, per the internet's suggestions. Same issue.
8. Disassemble the PC and put the original drive back in. create a new image (assuming the old one was bad), repeat steps 2-5. Same issue.
9. I load a fresh instance of windows 10 on the new drive and try to restore the image from within windows but it doesn't see a valid image (since the image is not for this disk) but at least I know the new drive is good as it takes the fresh install no problem.

Any ideas on what else I should try before putting the original drive back in and creating a new image with some other software? possibly Macrium Reflect?

submitted by /u/k20stitch_tv
[link] [comments]

:)

 

cloning hdd to NVMe m.2

Hi Crocodile_aligator

Yes, Windows will load the correct driver for the NVMe M.2. the first time you boot up Windows 10 from that drive after cloning your drive . . .

 

cloning hdd to NVMe m.2

if i clone my hdd to a nvme m.2 using something like macrium will windows use the right driver for nvme on boot or would i need to reinstall to get correct drivers

 

M.2 SATA to NVME clone: Windows 10 won't boot

Problem: Windows partition won't boot after cloning M.2 SATA drive to M.2 NVME. Simply returns to BIOS splash screen are restarts boot sequence.

Background: Cloning process was simple raw dd copy. Drive had EFI, Windows 10, and Linux partitions. Cloning preserved exact partition sequence, sizes, and UUIDs.

Linux partition needed minor tweaks to /etc/fstab due to the device names being different (/dev/nvme0n1px vs. /dev/sdax), but boots fine.

The disk is GPT, and I believe the original Windows 10 was UEFI - the Linux installation definitely was.

Boot sequence brings up Linux 'grub' menu first. Choosing the EFI partition then brings up Windows EFI boot menu. Fresh Windows install (see below) boots fine from here, old install fails.

Attempts at solution: I did a fresh Windows install in a spare partition and it boots fine. Using the new Windows installation, I've edited the BCD entry for my original Win 10 install. I have
the correct BCD device, osdevice, and path.

Questions:

• What else needs to be done to make Windows boot again?
• Are there any config file or registry changes that need to be made to account for the SATA to NVME move?
• How do I see boot error messages for a UEFI boot failure? No errors displayed and no log files that I can find in Windows or EFI partitions...