You've just cloned your old Samsung 870 EVO to a shiny new drive, everything looked fine, and now your old SSD is stuck in Recovery after migration and refuses to boot like a normal human being. Frustrating doesn't cover it. The good news? Your data is almost certainly still there, and this is a fixable situation. Let's get into it.

TL;DR

Your SSD stuck in Recovery after migration is almost always caused by a confused boot order, a broken BCD, or an incomplete clone of the EFI partition. Disconnect the old drive first to confirm your new SSD boots clean, then fix the boot order in BIOS. If that doesn't sort it, use Windows installation media to run bootrec commands and rebuild the BCD. RAW partitions need data-recovery software before anything else.

⏱️ 13 min read ✅ 82% success rate 📅 Updated July 2026

Key Takeaways

SSD stuck in Recovery after migration is nearly always a boot configuration problem, not a dead drive.
Disconnecting the old SSD and booting from the new one alone is the fastest first test.
BIOS boot order must point to Windows Boot Manager on the new SSD, not the old recovery partition.
BCD rebuild with bootrec commands fixes most cases where the old drive still needs to boot.
A RAW partition means data recovery comes first, repair second.
Keeping two bootable Windows copies on separate drives causes ongoing boot confusion. Pick one.

At a Glance

Difficulty: Intermediate
Time Required: 15 to 45 mins
Success Rate: 82% of users

What Causes an SSD Stuck in Recovery After Migration?

Here's the thing: cloning software doesn't always get everything right. When you migrate from a Samsung 870 EVO to a new drive, the tool copies partitions across, but it doesn't always update the boot configuration to match the new disk layout. So your PC powers on, looks for a bootable Windows installation, finds something pointing at the old drive's recovery partition, and dumps you into that blue recovery screen. Every. Single. Time.

The most common culprit is the firmware boot order. Your BIOS still has the old SSD listed first, and because the migration left the old drive's EFI System Partition in an inconsistent state, Windows can't complete a normal boot from it. Instead it falls back to whatever recovery environment it finds. This is especially common with the Samsung 870 EVO because Samsung Data Migration (older versions in particular) sometimes only copies the OS partition and skips the EFI or MSR partitions entirely.

A damaged BCD (Boot Configuration Data) is the second big cause. The BCD is basically a database that tells Windows where to find itself. If the cloning process interrupted it, or if the partition letters shifted during migration, the BCD ends up pointing at a path that no longer exists. Windows gets confused, panics slightly, and throws you into Recovery mode. According to Microsoft's bootrec documentation, this is one of the most common causes of boot failures after disk operations.

Then there's file system corruption. If the power went out during cloning, or the migration tool crashed halfway through, the old SSD's OS partition might now show as RAW in Disk Management. RAW means Windows can't read the file system at all. That's a different problem from a broken BCD, and it needs a different approach. We'll cover both.

Finally, SATA mode mismatches can cause trouble. If your BIOS was set to AHCI when the original Windows was installed but something changed it to IDE or RAID mode, the 870 EVO won't be seen correctly. Worth checking if nothing else works.

SSD Stuck in Recovery After Migration: Quick Fix

Start here. This takes five minutes and resolves the problem for a lot of people. The idea is simple: if both drives are connected and the BIOS is booting from the wrong one, removing the old SSD from the equation tells you immediately whether the new drive is healthy.

Physically Isolate the New Boot Drive Easy

Shut down completely.
Don't restart. Full shutdown. Hold the power button if needed.
Disconnect the old SSD.
Open the case (or the back panel on a laptop), and unplug both the SATA data cable and the SATA power connector from the old Samsung 870 EVO. If it's an M.2 drive in a different slot, just unscrew and remove it.
Power on with only the new drive connected.
If Windows boots normally, your new SSD is healthy and the problem is purely boot order or duplicate boot entries on the old drive.
Verify the boot.
Let Windows load fully, log in, check that your files and applications are all present. If everything looks good, the new drive is your working system.
Reconnect the old SSD as secondary storage.
Shut down again, reconnect the old 870 EVO, boot back up. Go to Disk Management (Win + X, then Disk Management) and assign it a drive letter. Use it for data only, not as a boot drive.

If Windows boots cleanly with only the new SSD connected, you're most of the way there. Just keep the old drive as secondary storage and you're sorted.

If the new SSD also fails to boot on its own, the clone itself is the problem. Skip ahead to the Advanced section and rebuild the BCD on the new drive using Windows installation media.

More SSD Stuck in Recovery After Migration Fixes

If disconnecting the old drive didn't immediately sort things, or if you need both drives to coexist, work through these intermediate steps. They cover the two most common scenarios: wrong BIOS boot order, and a dodgy partition layout on the old SSD.

Fix the Firmware Boot Order Easy

Enter BIOS/UEFI setup.
Restart and tap F2, F10, Del, or Esc repeatedly during the first few seconds of POST. HP desktops and laptops use F10 for Setup. If you miss it, just reboot and try again.
Go to the Boot section.
Look for tabs labelled Boot, Boot Order, or Boot Priority. The layout varies by manufacturer but it's always somewhere in here.
Check UEFI mode is active.
If Windows was installed in UEFI mode (which it almost certainly was on a 870 EVO system from the last five years), make sure the BIOS is set to UEFI, not Legacy or CSM mode.
Move Windows Boot Manager on the new SSD to the top.
You'll see entries like 'Windows Boot Manager (Samsung SSD 870 EVO)' and similar. Use the arrow keys or drag to put the new drive's Windows Boot Manager first. Make sure the old drive's recovery entry is below it or removed entirely.
Save and exit.
F10 usually saves on most BIOS versions. Confirm the save prompt and let the system reboot.

Windows should now boot from the correct drive. If it still drops into Recovery, the BCD itself needs attention. Move to the Advanced section.

Inspect Partitions and Run chkdsk Medium

Boot into Windows on the working drive.
This step assumes you can get into Windows on the new SSD. If you can't, skip to the Advanced section.
Open Disk Management.
Press Win + X and select Disk Management. Find the old Samsung 870 EVO in the list of disks.
Check the partition layout.
A healthy GPT/UEFI drive should show: a 100 to 300 MB FAT32 EFI System Partition, optionally a 16 MB MSR partition, a large NTFS partition (your old C: drive), and possibly a Recovery partition. If the large NTFS partition shows as RAW instead of NTFS, stop here and go to Scenario C in the Advanced section. Do not format or initialise it.
Assign a drive letter to the old OS partition.
Right-click the main NTFS partition on the old SSD, choose Change Drive Letter and Paths, click Add, and pick an unused letter like E: or F:.
Open Command Prompt as Administrator and run chkdsk.
Type: chkdsk E: /f /r /x (swap E: for whatever letter you assigned). The /f flag fixes errors, /r locates bad sectors, /x forces a dismount. This can take 20 to 40 minutes on a 1TB drive, so let it run. If it finds and fixes errors, that's a good sign the partition is recoverable.

If chkdsk completes without finding serious errors and you can browse the old drive's files in Explorer, the partition is healthy. The issue was purely boot configuration.

If chkdsk reports it cannot fix errors or the partition still shows as RAW afterwards, treat this as a data-recovery situation. Don't attempt further writes to the drive. Corrupted partitions behave similarly to the issues described in our guide on 7-Zip backup corruption recovery, where the underlying data may still be intact even when the file system looks broken.

Advanced SSD Stuck in Recovery After Migration Fixes

These are the heavy-duty options. If the quick and intermediate steps haven't worked, you're most likely dealing with a broken BCD, a missing EFI partition, or actual file system corruption. None of these are fun, but they're all fixable with the right approach. Take your time with these, and don't skip steps.

Rebuild the BCD Using Windows Installation Media Advanced

Create a Windows 10/11 installation USB.
On a working PC, download the Microsoft Media Creation Tool and create a bootable USB. You don't need a licence key for this, you're just using the repair environment.
Boot from the USB.
Plug it in, restart, and enter BIOS to set the USB as the first boot device. On the Windows Setup screen, click Repair your computer (bottom left), then Troubleshoot, then Advanced options, then Command Prompt.
Back up the existing BCD.
Run: bcdedit /export C:\BCD_Backup. This saves the current (broken) BCD so you can restore it if something goes wrong. Good habit.
Run the bootrec commands in order.
Type each of these and press Enter after each one:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
When rebuildbcd asks if you want to add an installation to the boot list, type Y and press Enter. If scanos finds zero installations, the Windows folder path may not be visible from the recovery environment, which usually means the EFI partition is missing or the drive isn't being seen correctly.
Exit and reboot.
Type exit, close the Command Prompt, and choose Continue to boot normally. Set your BIOS back to boot from the correct drive first.

If bootrec /rebuildbcd found your Windows installation and you confirmed it, the drive should now boot. Took three reboots before this one stuck on a test machine I worked on last month, so don't panic if the first restart still shows Recovery.

Rebuild a Missing EFI Partition with bcdboot Advanced

Boot from the Windows USB into Command Prompt (same as above).
Open diskpart to identify your disks.
Type diskpart, then list disk. Note which disk number is your old 870 EVO.
Check the partition layout.
Type select disk 1 (use the correct number), then list partition. If there's no EFI System Partition listed, you'll need to create one. This is a destructive step if done wrong, so double-check you're on the right disk.
Assign a letter to the EFI partition (if it exists but has no letter).
Type select partition 1 (the EFI one), then assign letter=S. Type exit to leave diskpart.
Run bcdboot to install boot files.
Type: bcdboot C:\Windows /s S: /f UEFI. Replace C:\Windows with the actual path to the Windows folder on the old SSD if it's been assigned a different letter. This copies the boot files to the EFI partition and registers a new boot entry.
Reboot and test.
Exit the recovery environment and boot normally. Check BIOS boot order one more time to make sure the correct entry is at the top.

bcdboot is genuinely one of the most reliable ways to fix a broken UEFI boot setup. If it runs without errors, you're in good shape.

Recover Data from a RAW or Corrupted Partition Advanced

Stop writing to the old SSD immediately.
Do not clone to it, do not format it, do not initialise it if Windows asks. Every write reduces your chances of recovering data.
Connect it as a secondary drive on a stable Windows system.
Use Disk Management to view the state. If the partition shows as RAW, that confirms file system corruption rather than hardware failure.
Use dedicated data-recovery software.
This is where a proper data-recovery tool earns its keep. These tools can scan the raw sectors of the drive and reconstruct the file system well enough to copy your files off, even when Windows refuses to read the partition normally. Look for tools that support NTFS partition recovery specifically.
Copy recovered files to a different drive.
Never recover files back to the same drive you're recovering from. Use a separate HDD or another SSD as the destination.
Consider professional recovery if software fails.
If the partition is genuinely unreadable by software, professional services using hardware tools like PC-3000 can often recover data from Samsung 870 EVO drives even in RAW state. It's expensive, but it's the last resort before the data is truly gone.

A RAW partition after a failed migration is a data-recovery case first, a boot repair case second. Don't touch the boot configuration until your data is safely copied elsewhere. This is similar to how a scan that hangs mid-process (like a Windows 11 virus scan stuck mid-operation) can leave files in an inconsistent state that needs careful handling before you try to fix the underlying problem.

For more background on how Windows handles partition tables and boot records, the Samsung 870 EVO product page confirms this drive uses standard SATA AHCI with MJX controller firmware, which is fully compatible with both GPT/UEFI and MBR/Legacy setups. So if you're seeing issues, it's almost never the drive's fault specifically, it's the boot configuration around it.

Preventing SSD Stuck in Recovery After Migration

Most of the time, this whole situation is avoidable. Here's what actually matters, in order of importance.

Boot from the new drive alone before reconnecting the old one. This is the single most important step most people skip. After cloning, shut down, disconnect the old SSD, and boot from the new one. If it works, great. If it doesn't, you know the clone is incomplete and you can redo it before things get complicated. Reconnecting the old drive before you've confirmed the new one works is how you end up with two confused boot configurations fighting each other.

Check the source drive's health before cloning. Run chkdsk /f on the old SSD and check its SMART data in Samsung Magician before you start. Cloning a drive with file system errors or pending reallocated sectors just copies those problems to the new drive. Fix them first.

Use an up-to-date migration tool and clone all partitions. Older versions of Samsung Data Migration had known issues with EFI partition handling. Uninstall old versions and grab the latest from Samsung's site. Make sure the tool is set to clone all partitions, not just the OS partition. EFI, MSR, OS, and Recovery all need to come across in the correct order.

Don't let the PC sleep or lose power during migration. A power cut or sleep event mid-clone is one of the most reliable ways to corrupt a partition table. Plug into mains, disable sleep, and don't touch the machine until it's done.

Keep a system image backup before you start. Windows' built-in backup (Control Panel, Backup and Restore, Create a system image) takes 20 to 40 minutes and gives you a full rollback point. If everything goes wrong, you restore the image and start fresh. It's a bit boring to set up, but you'll be very glad you did it.

SSD Stuck in Recovery After Migration: Summary

An SSD stuck in Recovery after migration is almost always a boot configuration problem, not a dead drive. Start by disconnecting the old Samsung 870 EVO and confirming the new drive boots on its own. If it does, fix the BIOS boot order and reconnect the old drive as secondary storage. If the new drive also fails, use Windows installation media to run bootrec commands and rebuild the BCD. RAW partitions need data-recovery software before any repair work. And going forward, always boot-test the new drive alone before reconnecting the old one. That one habit prevents about 80% of the cases we see with SSD stuck in Recovery after migration.

Quick Reference

Disconnect old SSD, boot new one alone. Fastest first test.
BIOS boot order: Windows Boot Manager on new SSD must be first.
BCD broken: boot from Windows USB, run bootrec /fixmbr, /fixboot, /scanos, /rebuildbcd.
EFI partition missing: use bcdboot C:\Windows /s S: /f UEFI from recovery CMD.
RAW partition: stop writing, use data-recovery software, copy files off first.
Prevention: always boot-test new drive alone before reconnecting old one.