AOMEI
Cloned SSD Will Not Boot: Check the Drive, Boot Mode and System Partitions
A successful copy is only part of an SSD migration. Prove that the new drive can start Windows independently before erasing the original.
Keep the original drive intact and check where the startup process stops. Confirm the new SSD is detected, the correct Windows boot entry is selected, the firmware mode matches the disk layout and the required system partitions were copied. A completed clone job does not prove an independent boot.
The new SSD appears in the cloning software. The progress reaches 100%. After the swap, the computer opens its firmware menu or reports that no boot device was found. Repeating the clone immediately can hide the more useful question: is the failure in hardware detection, boot selection or the copied Windows layout?
Record the exact message and the source and destination drive models. Keep a verified backup and a recovery route available before further changes.
Identify the Stage That Fails
A drive that is absent from the firmware storage list presents a different problem from a drive that is detected but has no working Windows boot entry. A system that starts Windows and then crashes presents another problem again.
A Copy Result Is Not a Boot Test
Check detection first, then the startup path and copied layout.
01 Can the computer see the SSD?
Resolve hardware detection firstCheck the computer and drive documentation. Another clone does not repair an unsupported slot or interface.
02 Can the SSD start Windows?
Keep the original until verifiedTest without relying on the original drive, then check applications, files and the recovery copy.
| Observation | First area to check | Avoid assuming |
|---|---|---|
| New SSD is not detected | Physical installation, supported interface and slot | That another clone will fix a hardware mismatch. |
| SSD is detected but Windows does not start | Boot entry, firmware mode and system partitions | That copying C: alone copied every boot dependency. |
| Windows starts only with the old drive attached | Independent boot files and the selected startup drive | That the new drive is already a complete migration. |
| Windows starts and then fails | Exact error, drivers, encryption and hardware changes | That disabling security or changing controller mode is a universal repair. |
Check Detection and the Correct Boot Entry
Confirm that the computer supports the new drive's physical format and interface. M.2 describes a form factor; it does not by itself establish SATA or NVMe support in a particular slot. Follow the computer manufacturer's service instructions for installation and handling.
If the firmware detects the SSD, inspect the available startup entries. A UEFI Windows installation normally uses a Windows Boot Manager entry. With both old and new drives attached, similar entries can make it easy to start the original installation and believe the new one has passed.
Test the intended final installation arrangement. An SSD visible through a USB enclosure during copying is not proof that ordinary cloned Windows will boot from USB, or that the same drive is correctly installed in the internal slot. Do not remove or reconnect internal hardware while it is powered.
Match the Boot Mode and Include the System Partitions
Check whether the source uses UEFI with a GPT layout or a Legacy BIOS arrangement with MBR. Copying a drive does not automatically justify changing those settings. A mismatch between the installation layout and the selected startup mode can prevent booting.
Windows can use partitions outside C: for boot and recovery. Depending on the installation, these may include an EFI System Partition or a System Reserved partition. The exact layout varies, so a simple copy of the visible Windows files is not an operating-system migration.
AOMEI distinguishes Disk Clone and System Clone workflows. Choose the supported operation for the intended migration and review all selected partitions. Keep firmware, storage-controller and encryption settings documented. Do not randomly switch AHCI and RAID modes or disable Secure Boot to experiment.
Review the Clone Plan Before Repeating It
AOMEI Backupper Professional and Backupper Workstation provide cloning tools for their supported Windows PC use cases. Select the source by its identity and contents, then independently confirm the destination. Cloning can overwrite the destination's existing data.
Check the required capacity and cloning mode. Used-space copying and sector-by-sector copying have different space requirements. A smaller destination may be unsuitable even when a quick glance at C: suggests enough free space; the full selected layout and supported resizing behaviour matter.
The genuine vendor screenshot below shows SSD Alignment and the final clone controls. Alignment is a storage-layout setting, rather than proof that the firmware will boot the result. Review the entire plan before committing it.
Prove the New SSD Works Without the Original
After the clone, shut down and follow the computer manufacturer's procedure to test the new SSD as the intended startup drive. Where appropriate, have the original drive safely disconnected during the independent test so the computer cannot rely on its boot files.
Confirm that Windows starts, the expected new drive is in use, applications open and important files are available. Perform a normal restart as well. Check the storage capacity and encryption or recovery status, and retain the original until the migration and backup arrangement have been verified.
If the new disk starts only while the old disk remains attached, treat that as an incomplete test. Have the boot arrangement assessed before wiping either drive. Recreating boot files is a specific repair operation and should follow the actual partition layout and current recovery instructions.
Choose the Licence and Finish the Storage Plan
Backupper Professional is positioned for personal Windows PC use. Backupper Workstation is the business Windows PC edition. Windows Server and services performed for other customers require an appropriate licence scope; do not choose solely because two editions share a clone feature.
For supported personal Windows PC backup and migration use.
For supported business Windows PC backup and migration use.
A reliable migration ends with a working replacement and a recovery copy. Resolve detection first, then boot selection and layout, and finally prove normal use. Avoid erasing the source just because the copy operation completed.
If Windows starts but C: has not gained the expected extra capacity, the Extend Volume and partition-layout guide explains why spare capacity can remain beyond a recovery partition.
Frequently Asked Questions
Why will an SSD not boot after a successful clone?
The copy may be complete while hardware detection, boot selection, firmware mode or required system partitions still prevent startup. Identify the exact stage before repeating the clone.
Is copying C: enough to make a bootable SSD?
Not necessarily. Windows may rely on an EFI System Partition or System Reserved partition outside C:. Use an appropriate supported system or disk migration workflow.
Should I switch from UEFI to Legacy mode?
Do not change it blindly. Match the firmware startup mode to the actual Windows installation and disk layout, and preserve a record of the original settings.
Why does Windows boot only when the old drive is connected?
The startup path may still depend on the original drive or its boot files. Confirm the selected boot entry and have the layout assessed before erasing either drive.
Does SSD Alignment fix boot errors?
It concerns the SSD storage layout and is not a universal boot repair. Detection, boot entries, firmware mode and system partitions must still be checked.
When is it safe to erase the old drive?
After the new SSD has passed an independent startup and restart test, applications and files are checked, and a verified recovery copy is available. Keep the original longer if anything remains uncertain.
