Cloning a hard drive to an SSD is usually intended to be a straightforward upgrade: copy the old drive, install the SSD, and continue using Windows with better performance. Sometimes the files appear to have copied correctly, but the computer will not start from the new drive.
This is not necessarily evidence that the SSD is defective. Booting depends on more than the visible Windows folder. The computer also needs the correct system partitions, a compatible partition layout, firmware settings, and valid boot information. A clone can contain nearly all of the original data and still be missing, inaccessible to, or ignored by the boot process.
First, protect the original hard drive
Do not erase, reformat, initialize, or repeatedly repair the original hard drive until the cloned SSD has been tested and your important files have been checked. If the old drive contains the only copy of important documents, photographs, accounting files, or business records, treat it as the source of truth until the migration is confirmed.
- Power the computer off before changing internal drives or cables.
- Label the original drive and the SSD so they cannot be confused.
- If possible, keep the original drive disconnected during the first boot test from the SSD.
- Do not use a disk-initialization prompt on the old drive simply because another computer cannot read it.
- Remember that a clone is not a backup. A later mistake, file deletion, or encryption problem can affect the clone too.
If BitLocker or another form of device encryption is enabled, have the recovery key available before changing drives or firmware settings. A boot change can trigger a recovery-key request, and there is no legitimate repair procedure that bypasses encryption or account security.
What the symptoms can tell you
The exact message matters. A computer that cannot see the SSD is experiencing a different problem from one that sees the SSD but displays “Operating System Not Found.” Windows automatic repair, a blinking cursor, a blue screen, and a request for a BitLocker recovery key each point toward different parts of the startup process.
| Symptom | Possible area to investigate |
|---|---|
| SSD is absent in firmware setup | Connection, adapter, drive compatibility, power, or a failed SSD |
| SSD is visible but not listed as a boot option | Missing boot files, wrong firmware mode, or no valid boot entry |
| “Operating system not found” | Incorrect boot disk, incomplete clone, or damaged boot structure |
| Windows begins loading, then fails | Boot configuration, storage drivers, encryption, or a hardware mismatch |
| BitLocker recovery screen appears | Expected security response to a significant boot or hardware change |
These are starting points rather than final diagnoses. The same message can have more than one cause.
Check whether the computer can see the SSD
Enter the computer’s UEFI or BIOS setup using the manufacturer’s displayed key, often a function key, Delete, or an on-screen option. Avoid changing settings at random. Record the current boot mode and storage settings before making a change.
Look for the SSD under storage devices and separately under boot options. If it is not detected anywhere, the problem is probably occurring before Windows starts. On a desktop, check the data and power connections with the computer unplugged. On a laptop, an SSD may not be fully seated, may require a particular form factor, or may not be supported by an adapter or enclosure used during cloning.
If the SSD is detected only through a USB adapter, that does not prove it will boot internally. USB boot support, internal storage drivers, firmware configuration, and the drive’s physical interface can all differ. Stop and investigate compatibility if the drive is not recognized internally.
Confirm that the clone included the boot partitions
A Windows installation normally includes more than the main partition shown in File Explorer. On a modern UEFI computer, the clone commonly needs an EFI System Partition, the Microsoft Reserved partition, the Windows partition, and possibly a recovery partition. Older systems may use an MBR partition layout and a different boot method.
A common cloning mistake is copying only the large Windows partition rather than the entire source disk. Another is cloning to a smaller SSD after excluding a small system partition that looked unimportant. The files may be present while the firmware has no usable boot files.
From another working Windows computer, or from suitable recovery media, inspect the SSD’s partition layout carefully. Do not delete partitions just to make the layout look cleaner. If the SSD contains valuable data, make sure you understand which disk is selected before using any disk-management command.
Check for a UEFI and Legacy mismatch
Windows may be installed using either UEFI with GPT partitioning or Legacy BIOS compatibility with MBR partitioning. The cloned drive and the computer’s current firmware mode must be compatible. For example, a GPT-based installation may not boot when the firmware is forced into Legacy mode, while an MBR installation may not boot when the system is configured for UEFI-only startup.
Changing between UEFI and Legacy settings can also affect encryption and boot entries. If the computer previously used UEFI, keep it in UEFI mode unless there is a specific reason and a documented plan to convert the installation. Do not convert the disk layout casually. A conversion can make the system unbootable and may require a recovery key.
Make sure the computer is selecting the new drive
When both the old hard drive and the cloned SSD are connected, the firmware can select the wrong device. Some systems show a generic disk name, while others show a Windows Boot Manager entry. The correct choice is often “Windows Boot Manager” associated with the SSD, not merely the SSD’s model name.
For a clean test, shut down and disconnect the original drive, then start the computer with only the SSD installed. This removes one source of confusion and prevents Windows from using boot files that remain on the old disk. If the system starts only when both drives are connected, the clone may not contain its own complete boot structure.
Repair boot files only after the layout is understood
Windows recovery tools can repair boot information, but they should not be the first response to an unknown disk layout. Automatic Repair may make changes, and commands such as bootrec or bcdboot can target the wrong volume if recovery mode assigns different drive letters.
If you proceed, first identify the SSD by its capacity and model, then identify the Windows partition and the EFI System Partition. Drive letters in recovery mode are not guaranteed to match the letters used in normal Windows. A command copied from a generic guide can therefore write boot files to the wrong disk.
Boot-file repair is a reasonable stopping point when the SSD is detected, the partition layout is appropriate, the original drive is safely preserved, and you have a current backup or a recovery key where applicable. Stop instead if the SSD reports errors, partitions appear corrupted, files are missing, or you are not certain which disk a command will modify.
Other causes that can look like a failed clone
- Source-drive errors: The cloning software may have skipped unreadable sectors or completed with warnings. Windows can then fail when it reaches a damaged system file.
- Different storage-controller settings: A change such as AHCI, RAID, or a vendor-specific storage mode can affect whether Windows loads its required driver.
- Encryption state: BitLocker can request recovery after a drive or firmware change. This is a security feature, not proof that the files disappeared.
- SSD capacity limitations: The source may have more used space, hidden partitions, or a layout that cannot be copied directly to the target.
- Hardware or adapter problems: An SSD may work through one connection but fail through a loose cable, incompatible adapter, or faulty storage slot.
When to stop and protect the data
Stop troubleshooting and preserve the drives if the original hard drive is clicking, disappearing, unusually slow, or reporting read errors. Repeated cloning attempts can place additional stress on a failing drive. Do not run repair utilities that write extensively to the source when data recovery is the priority.
Also stop if Windows asks for a recovery key you do not have, if the account needed to unlock the data is unavailable, or if the SSD has become the only copy of important files. A computer repair technician can help distinguish a boot-configuration problem from a storage or encryption problem, but no responsible technician should promise recovery before examining the drives and their condition.
Preventing the problem on the next clone
- Create a verified backup before beginning the upgrade.
- Record whether the current installation uses UEFI/GPT or Legacy/MBR.
- Clone the entire disk when the goal is a bootable replacement, not just the visible Windows volume.
- Use cloning software that reports skipped sectors or verification errors.
- Test the SSD with the original drive disconnected before wiping or repurposing anything.
- Confirm that important files open from the SSD and that encryption recovery information is available.
A cloned SSD that will not boot is often recoverable, but the right fix depends on where the startup chain breaks. Checking detection, partition structure, firmware mode, boot selection, and drive health in that order is safer than repeatedly changing settings or reinstalling Windows. If the problem involves important business data or a computer used in Bellevue, Omaha, Papillion, La Vista, Plattsmouth, Ralston, Council Bluffs, or at Offutt Air Force Base, preserve the original drive and obtain a careful diagnosis before making destructive changes.
When to call a professional
If the problem continues, the data is important, or the repair requires work beyond your comfort level, AME Computers can provide professional diagnosis and repair or call 402-505-6600.
Free repair guidance
Get New Computer Repair Guides by Email
Practical PC and Mac help from AME Computers. Confirm your email once and unsubscribe anytime.