Windows 10: Cloning the NVME boot drive in a laptop with only one M.2 slot

I've researched this enough to know it's possible to clone the NVME boot SSD on my new Lenovo T14 to an external drive then somehow move that clone back onto a newer/bigger NVME SSD that I'd have swapped out into the T14. The boot drive has the latest W10 version (20H2, build as of a week ago).

OTOH, I have a desktop with two NVME M.2 slots. Would it be a better idea to put the laptop boot NVME in one of the slots and the new bigger NVME into the other slot and do the cloning there? Any advantages to doing it this way? BTW, I've already taken out the boot SSD from the laptop with the intention of doing it this way but just thought I'd ask.

I'll be using Macrium Reflect, which I haven't downloaded yet. I'm no stranger to building my own desktops but I've never cloned anything. Thanks.

:)

 

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...