Cloned Windows 11 Boot Drive to a new 2TB NVMe SSD. Now getting BSOD

Caleb33

Hey guys, I'm losing my mind here. I just bought a shiny new 2TB NVMe M.2 SSD to replace my old lagging 500GB SATA SSD. I used a free tool I found online to clone the old drive to the new one. The software said "Success!", but when I unplugged the old drive and tried to boot from the new NVMe, Windows hit me with a BSOD: INACCESSIBLE_BOOT_DEVICE.

To make things worse, when I checked the drive via a live USB, the cloning tool left a 500MB "Recovery Partition" right in the middle of the drive, so my remaining 1.5TB of unallocated space is stuck at the very end and Windows won't let me extend my C: drive.

Did I just brick my system? How do I fix this boot loop and get my space back?

Sean2C

Caleb33
Ignore the nerds arguing about math, OP. Here is the real-world fix:

Create a bootable Windows Installation USB on another PC.
Boot into it, click "Repair your computer" -> "Troubleshoot" -> "Command Prompt".

Type bcdboot C:\Windows /s N: ,replace N: with whatever letter your EFI partition is currently assigned. This forces Windows to rebuild the boot configuration data on the new NVMe drive from scratch.
To fix the unallocated space without losing data, download some disk management tool.
Use it to right-click the Recovery Partition, select "Move", and drag it to the very end of the disk. Then go back to Windows Disk Management, right-click C:, and hit "Extend". Done.

Jaz

The INACCESSIBLE_BOOT_DEVICE error during a SATA-to-NVMe migration happens because of a storage controller driver mismatch. When Windows boots, it initializes the driver stack based on its registry state. Since your original install was on a SATA drive, the stornvme.sys driver wasn't flagged as a critical boot-start driver.

As for your partition layout issue: Windows creates the Recovery Partition sequentially. When you did a standard clone, it copied the exact block mapping. The layout is now [EFI System Partition] -> [C: Drive (500GB)] -> [Recovery Partition (500MB)] -> [Unallocated Space (1.5TB)]. Because Disk Management can only extend partitions into contiguous unallocated space directly to their right, that 500MB recovery block is physically blocking your C: drive from expanding.

Graze_042

Jaz
Visually accurate, but technically flawed explanation. Windows 11 has native NVMe drivers injected into the boot image by default nowadays. The driver stack isn't the root issue here.

The real culprit is almost certainly a broken BCD pointer. The GUID of the disk changed during the copy, and the Windows Boot Manager is looking for the old hardware ID. Also, calling what OP did "cloning" is generous. True cloning is a bit-by-bit block-level reproduction via dd or raw sector copy. OP clearly used a file-level migration wrapper masquerading as cloning software.

Zanxus

Graze_042
While you are correct about the BCD GUID mismatch, advising a sector-by-sector raw block copy, dd, for drives with mismatched logical sector sizes. Like, an older 512e SATA drive to a modern 4Kn native NVMe drive, is a recipe for disaster.

If you force a raw sector copy across different sector architectures, you will completely corrupt the file system metadata and alignment, resulting in massive performance degradation or an unreadable partition table.

VSS cloning is mathematically required when target geometries differ.

Luz1

Zanxus
dud, this is a Wendy's. I just wanted to read about a guy fixing his gaming PC and now I'm accidentally studying for a computer science PhD thesis💀

Watsson308

Sean2C
DO NOT MOVE PARTITIONS BLINDLY. I tried doing exactly what this guy suggested last month using a

third-party partition shifter. Power flickered for half a second right in the middle of the cluster relocation.

MFT got completely shredded. Lost 4TB of family photos, game saves, and "homework" archives. Back up your data to the cloud before you touch partition boundaries, otherwise, you're playing Russian roulette with your data.

Caleb33

Watsson308
Oh god, you are terrifying me. I didn't actually back up my original SATA SSD because I thought the whole point of cloning was making a backup copy. Now I'm scared to run any commands in CMD or use partition tools. What if I lose everything?

Flanren

Caleb33
Don't listen to the scaremongers. Third-party GUI software is just bloated adware that causes crashes. Do it natively.

Boot into your Windows USB, open CMD, and type: diskpart list disk select disk 0 (your new NVMe) list partition select partition 4 (the recovery partition blocking you) delete partition override

Boom. Obstacle deleted. Then just run extend on your OS partition. No bloatware, no GUI overhead, pure command-line efficiency.

JOH

Caleb33
Your original SATA SSD is completely untouched. That's the beauty of cloning—it reads data from the source drive, it doesn't delete it. If you completely screw up the formatting on the new NVMe drive, it doesn't matter. You can just wipe it and start over. Turn off your PC, plug your old SATA drive back in, unplug the NVMe, and your PC will boot up exactly like it did yesterday. You haven't lost anything.

jeremy_d

Flanren
Ah yes, telling a terrified beginner to use delete partition override in diskpart. What could possibly go wrong?

Why stop there? You forgot to tell him to run rm-rf / or throw his motherboard into a microwave just to make sure the electrons are properly aligned.

ZaynC_78

jeremy_d
Nobody here is even asking the real questions: Is OP's original drive encrypted with BitLocker?

If BitLocker is enabled, running raw diskpart commands or using sketchy proprietary cloning software closed-source tools will trigger a TPM tamper alert. The motherboard will think it’s a cyberattack and lock the drive permanently. Not to mention, half of these "free cloning tools" are essentially telemetry spyware phoning home to servers overseas with your exact sector data.

ell_Lyon

ZaynC_78
You actually raise a valid cryptographic point. BitLocker relies on PCR 7 inside the TPM to verify Secure Boot and partition validation.

Modifying or moving the recovery partition changes the disk geometry signature, which will trigger a BitLocker Recovery Key prompt on the next boot cycle. If OP does this, they absolutely must have their 48-digit recovery key saved in their Microsoft Account, or the data is cryptographically gone forever.

azur

ell_Lyon
Place your bets now, boys. OP definitely doesn't have that 48-digit key. It’s probably linked to a Microsoft Outlook email account they made in 2015 using a phone number they deactivated 5 years ago. Press F to pay respects.

blaick

azur
Exactly why local offline accounts and open-source encryption like VeraCrypt are mandatory. Relying on Microsoft's cloud to hold your data hostage via TPM keys is a dystopian nightmare waiting to happen.

Lyn

JOH
Wait... REALLY?! 💀 Oh my god, I am an absolute idiot.

I thought cloning "moved" the files like a cut-and-paste operation, and that my old drive was wiped clean during the process. Total dynamic brain fart moment. Let me shut this down, plug the old SATA drive back in, and see if it boots.

Yveen

Lyn
Be careful. Sometimes if you boot your PC with both the old drive and the newly cloned drive plugged in at the same time, Windows gets confused by the identical disk signatures. It can cross-talk and overwrite the boot sector of your original drive by accident. Happened to me last Tuesday. Total nightmare, had to reinstall everything from scratch.