sodcalculator

10 Tech How-To

Cloned SSD Won’t Boot? Fix It Without Losing Data

Guide 10-31758 · Updated · Step by step

If your cloned SSD won’t boot, the fix usually involves repairing the boot configuration or changing the BIOS boot mode—not re-cloning the drive. You can resolve most boot failures without losing any data by using Windows recovery tools or a Linux live USB to repair the bootloader, and by ensuring the SSD is properly connected and recognized.

Why a Cloned SSD Fails to Boot

Cloning copies every byte from the old drive to the new one, including the operating system, files, and boot records. However, a perfect copy doesn’t guarantee a bootable drive because the hardware context changes. The most common reasons a cloned SSD won’t boot are:

  • BIOS boot mode mismatch: The original drive used Legacy (CSM) mode, but the new SSD is set to UEFI, or vice versa. Windows only boots in the mode it was installed for.
  • Boot order or drive priority: The system still tries to boot from the old drive or a USB stick, or the new SSD isn’t listed first.
  • Missing or corrupted boot files: The clone process may have missed the EFI system partition (ESP) or the Master Boot Record (MBR), especially if you cloned only the Windows partition.
  • Drive connection issues: The SSD may be on a port that is disabled, or the SATA/NVMe cable is loose.
  • Partition style mismatch: The original drive was MBR, but the clone tool created a GPT disk, or the motherboard doesn’t support the new style.

Before You Do Anything: Safety Checks

Your data is safe as long as you don’t format or repartition the SSD. The clone is intact; the problem is that the computer can’t find or execute the boot files. To avoid making things worse:

  • Keep the old drive unplugged during troubleshooting. This forces the system to attempt booting from the SSD and prevents accidental writes to the old drive.
  • Back up any critical files from the SSD if you can access it as a secondary drive (e.g., via a USB enclosure). This is a precaution, not a requirement.
  • Do not run any “repair” tool that offers to rebuild the partition table unless you have a full backup—these tools can overwrite the boot area.

Step-by-Step Fixes (From Simplest to Most Involved)

Try these in order. Each step is non-destructive and preserves your data.

1. Check BIOS/UEFI Settings

  1. Enter the BIOS/UEFI setup (usually by pressing Del, F2, F12, or Esc during startup).
  2. Set the correct boot mode: if your original system used UEFI, ensure the SSD is set to boot in UEFI mode; if it used Legacy, set CSM/Legacy mode. When in doubt, try toggling between UEFI and Legacy to see which one lets the SSD appear as a boot option.
  3. Set the boot order so the SSD is first. If the SSD doesn’t appear, check if the SATA port is enabled or if the M.2 slot is recognized.
  4. Disable Secure Boot temporarily if you are using a Windows 10/11 installation that was not originally set up with it.

2. Use Windows Automatic Repair

  1. Create a Windows installation USB (using Media Creation Tool on another PC).
  2. Boot from the USB, select your language, then click “Repair your computer”.
  3. Go to Troubleshoot > Advanced Options > Startup Repair. This scans for common boot issues and attempts to fix them without touching your files.

3. Rebuild the Boot Configuration Data (BCD)

If Startup Repair fails, open Command Prompt from the Advanced Options (Troubleshoot > Advanced Options > Command Prompt) and run these commands one by one:

  1. bootrec /fixmbr – rewrites the master boot record (safe for GPT too).
  2. bootrec /fixboot – writes a new boot sector.
  3. bootrec /scanos – scans for Windows installations.
  4. bootrec /rebuildbcd – rebuilds the boot configuration database. If it asks to add an installation, type Y.

If you get an “access denied” error on fixboot, your disk is GPT and you need to use diskpart to assign a letter to the EFI partition first. Steps:

  • Type diskpart, then list disk, select disk X (X is your SSD number), list partition, select partition 1 (the EFI partition, usually about 100MB), assign letter=S, then exit.
  • Then run bcdboot C:\Windows /s S: /f UEFI (assuming Windows is on C:). This rebuilds the EFI boot files.

4. Repair UEFI Boot with bcdboot

If the above doesn’t work, use the bcdboot command directly. In the Command Prompt, type:

bcdboot C:\Windows /s S: /f UEFI

Replace C: with the drive letter where Windows is installed (check with dir C:\Windows). This copies the boot manager files to the EFI partition and creates a new BCD store.

Common Mistakes That Make It Worse

  • Using the wrong partition style: If your old drive was MBR and your new SSD is GPT, Windows won’t boot unless the firmware is set to UEFI with CSM disabled. You can convert GPT to MBR without data loss using a tool like Minitool Partition Wizard, but it’s risky—back up first.
  • Cloning only the C: drive: Many clone tools let you select partitions. If you didn’t clone the EFI system partition (on GPT) or the System Reserved partition (on MBR), the SSD won’t boot. Re-clone using the “Clone Disk” option that copies all partitions.
  • Forgetting to remove the old drive: If the old drive is still connected, the BIOS may boot from it, and you might think the clone failed. Disconnect the old drive to test.
  • Using a USB 3.0 to SATA adapter that doesn’t support booting: Some adapters are not bootable. If you cloned via USB, connect the SSD directly to a SATA port on the motherboard.

When the SSD Is Not Recognized at All

If the SSD doesn’t appear in BIOS, the problem is hardware, not software. Check:

  • Is the SATA data cable securely connected? Try a different cable and port.
  • Is the M.2 SSD fully seated in its slot? Some slots share bandwidth with SATA ports; check your motherboard manual.
  • Does the SSD work in another computer? If not, it may be defective.
  • If the SSD is new, it may need to be initialized in Disk Management. Connect it as a secondary drive, open Disk Management, and if the disk shows as “Unknown” or “Not Initialized”, right-click and initialize it as GPT (or MBR). This does not delete data, but it writes a new partition table—only do this if you have a backup, as it could make the data inaccessible if the original table was corrupted.

Alternative: Use a Linux Live USB to Backup Data

If you are unable to repair the boot and fear data loss, you can access your files from a Linux live USB. Boot from a Ubuntu or Linux Mint USB, select “Try Ubuntu”, and then mount the Windows partition (usually appears in the file manager). Copy your important files to an external drive. This is a safe, non-destructive way to recover data before attempting more aggressive repairs.

Frequently Asked Questions

Will repairing the boot loader delete my files?

No. Commands like bootrec and bcdboot only rewrite the boot configuration and boot sector files. They do not touch your personal data, installed programs, or the Windows system files. Your files remain intact.

Why does my cloned SSD boot only when the old drive is plugged in?

This usually means the boot files are on the old drive, not the SSD. The clone may have copied only the Windows partition, leaving the boot manager on the old drive. You can fix this by using bcdboot to copy the boot files to the SSD’s EFI partition, as described above.

Should I use UEFI or Legacy mode for my new SSD?

Match the mode your old drive used. If you don’t know, try UEFI first (most modern systems), then Legacy if that fails. If you switch modes, you may need to run bcdboot with the correct /f parameter (UEFI or BIOS).

Can I fix the boot without a Windows installation USB?

Yes, if you have a recovery drive or a system repair disc. You can also create a bootable USB with a tool like Rufus and a Windows ISO. If you have another PC, you can create a Windows installation USB there.

What if the clone tool didn’t copy the EFI partition?

You can manually create the EFI partition using Diskpart, then use bcdboot to populate it. This is advanced but doable. Alternatively, re-clone the entire disk using a tool that copies all partitions, such as Macrium Reflect or Clonezilla.

Is it safe to use a third-party boot repair tool?

Tools like EasyBCD or Boot Repair Disk (Linux) can be effective, but they may modify the boot sector. Always back up important data before using them. Stick to Microsoft’s built-in tools first, as they are safer.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →