Fix Cloned SSD Won’t Boot: Step-by-Step Guide

If your cloned SSD won’t boot, the most common cause is a partition table or boot configuration mismatch between the source drive and the clone. This guide walks you through the standard fixes—checking BIOS boot mode, rebuilding the EFI boot entry, and verifying the clone with a disk tool—so you can get your system running from the new drive.

Why Cloned Drives Fail to Boot

Cloning copies every byte from the old drive to the new one, but the new SSD is not an exact physical replica. The boot process relies on a specific partition layout and boot configuration that can break when the drive geometry changes. Here are the most frequent reasons a cloned SSD won’t boot:

• Partition table type mismatch – The old drive uses MBR (Master Boot Record) while the clone is GPT (GUID Partition Table), or vice versa. Most modern systems use GPT, but older BIOS-based PCs expect MBR.
• Boot mode mismatch – Your firmware is set to UEFI mode, but the cloned drive was made from a legacy BIOS installation, or the reverse. The drive must match the firmware’s boot mode.
• Missing or corrupted EFI System Partition (ESP) – On UEFI systems, the ESP holds the boot loader. If the clone didn’t copy it correctly, the system has nothing to boot.
• Boot configuration data (BCD) errors – Windows stores boot options in the BCD store. A clone can have BCD entries pointing to the old drive’s letter or partition, which no longer exists.
• Drive order in BIOS – The system may still try to boot from the old drive or a USB stick. Check the boot priority in BIOS.
• Unallocated space or partition alignment – Some cloning tools leave unallocated space at the beginning of the drive, which can confuse the boot loader.

Before You Start: Check the Basics

Before diving into advanced fixes, rule out simple issues. These steps take two minutes and solve a surprising number of cases.

1. Disconnect the old drive – If both drives are connected, the system may try to boot from the old one. Unplug the old drive and try again.
2. Check the SATA or NVMe connection – Reseat the SSD, try a different cable or slot, and make sure the drive is detected in BIOS.
3. Set boot order – Enter BIOS (usually by pressing Del, F2, F12, or Esc during startup) and ensure the new SSD is first in the boot priority list.
4. Verify the clone – Boot from a Windows installation USB, open Command Prompt (Shift+F10), and run diskpart to list disks and partitions. Confirm the clone has the expected partitions.

If the drive is detected but still won’t boot, proceed to the firmware settings.

Fix 1: Match BIOS Boot Mode (UEFI vs Legacy)

The most common cause is a mismatch between the firmware’s boot mode and the drive’s partition style. Here’s how to check and fix it:

1. Enter BIOS and look for a setting called Boot Mode, UEFI/Legacy, or CSM (Compatibility Support Module).
2. If your old drive used MBR, set boot mode to Legacy or CSM. If it used GPT, set it to UEFI.
3. Save changes and exit. Try booting again.

If you don’t know which mode the old drive used, check the partition style: MBR drives have a small system partition (typically 100–500 MB) marked as Active, while GPT drives have an EFI System Partition (ESP) formatted as FAT32. If the clone’s partition style doesn’t match the firmware, you have two options: change the firmware setting (if it supports both) or convert the drive to the correct style—but conversion usually requires wiping the drive, so re-cloning with the correct settings is often easier.

Fix 2: Rebuild the EFI Boot Entry (UEFI)

If you’re using UEFI mode and the drive has an ESP but the boot entry is missing or corrupt, you can rebuild it from the Windows Recovery Environment. Here’s how:

1. Boot from a Windows installation USB (same version as your installed Windows).
2. Choose Repair your computer → Troubleshoot → Command Prompt.
3. Run diskpart, then list disk and select disk X (where X is your SSD). Run list partition to find the ESP (usually 100–500 MB, type EFI).
4. Assign a drive letter: select partition Y then assign letter=S.
5. Exit diskpart (exit). Now run: bcdboot C:\Windows /s S: /f UEFI (replace C: with the drive letter of your Windows installation if different).
6. Reboot and remove the USB. The system should now find the boot loader.

This command copies the boot files to the ESP and creates a new BCD store. If you get an error, double-check the drive letters and that the ESP is FAT32.

Fix 3: Repair the Master Boot Record (Legacy)

For legacy BIOS systems with MBR, the boot sector can be repaired using the bootrec tool from the Command Prompt in the Recovery Environment:

1. Boot from the Windows installation USB and open Command Prompt as above.
2. Run these commands in order:
   • bootrec /fixmbr – rewrites the master boot record.
   • bootrec /fixboot – writes a new boot sector.
   • bootrec /rebuildbcd – scans for Windows installations and rebuilds the BCD store.
3. If /fixboot gives an “access deniedâ€� error, run bootsect /nt60 SYS /mbr instead.
4. Reboot and try again.

This fix works for legacy MBR systems. If your drive is GPT but you’re in legacy mode, this won’t help—you need to switch to UEFI mode or re-clone with GPT.

Fix 4: Use a Cloning Tool with Proper Settings

If the above fixes don’t work, the clone itself may be flawed. Many free cloning tools have options that affect bootability. When re-cloning, pay attention to:

• “Sector by sectorâ€� vs “proportionalâ€� – Use “sector by sectorâ€� if the source is smaller than the target, but note this copies the entire drive, including empty space, so it may take longer.
• Partition alignment – Ensure the tool aligns partitions to the SSD’s erase block size (usually 1 MB). Most modern tools do this automatically.
• Include hidden partitions – Some tools skip the recovery or system partitions by default. Make sure all partitions are selected, especially the ESP or System Reserved.
• Target drive size – If the target is larger, the tool may leave unallocated space. That’s fine, but the boot partition must be at the beginning of the drive.

After re-cloning, disconnect the old drive and try booting before installing the SSD in its final slot.

When to Reinstall Instead of Cloning

Cloning is great for a like-for-like upgrade, but it’s not always the best path. If you’ve spent hours troubleshooting and the drive still won’t boot, a clean install may be faster and more reliable. This is especially true if:

• The source drive is corrupted or has bad sectors.
• The clone is from a different Windows version (e.g., Win 10 to Win 11).
• You don’t need to preserve installed programs—just files.

A clean install takes about 30 minutes and avoids all boot configuration issues. You can back up your files first, then install Windows fresh on the SSD. Afterward, reinstall your programs and copy your data back.

Frequently Asked Questions

Why does my cloned SSD show as unallocated in Disk Management?

This usually means the clone failed or the partition table wasn’t copied. Check if the source drive is still intact, then re-clone using a tool that copies the partition table (MBR or GPT) correctly. If the drive shows as unallocated, it’s not bootable because there’s no boot code.

Can I clone a larger HDD to a smaller SSD?

Yes, if the used space on the HDD is less than the SSD’s capacity. Most cloning tools will shrink the partitions to fit. However, the boot partition must remain at the beginning of the drive, and the tool must handle the size difference correctly. If the clone fails to boot, try a tool that explicitly supports “clone to smaller disk.â€�

Do I need to change BIOS settings after cloning to NVMe SSD?

Often yes. If you’re moving from SATA to NVMe, the firmware may need to have NVMe support enabled and the boot mode set to UEFI (NVMe drives typically require UEFI). Also, check that the NVMe drive is recognized in BIOS before attempting to boot.

What does “Bootmgr is missing� mean?

This error appears on legacy BIOS systems when the boot manager (bootmgr) is not found on the active partition. It usually means the MBR or the boot files are missing or corrupt. Run the bootrec /fixmbr and bootrec /rebuildbcd commands from the Recovery Environment as described above.

Will a cloned SSD boot if the old drive is still connected?

It can, but it’s not recommended. The system may pick the old drive’s boot loader, or the BCD entries may point to the old drive’s partition. Always disconnect the old drive when testing the clone, and only reconnect it after the new drive boots successfully—ideally as a secondary data drive.

Is it safe to delete the old drive’s partitions after cloning?

Only after you’ve confirmed the clone boots and works correctly. Keep the old drive untouched for at least a week to ensure you don’t need to go back. Once you’re confident, you can format the old drive to use as extra storage.

Related

• Rockstar Error Code? Fixes for Launcher & Social Club
• Discord Stuck at RTC Connecting? Fixes That Work
• How to Access and Use My AI in Snapchat