If your cloned SSD won’t boot, first check that the computer detects the new drive and is selecting the correct boot entry. Then match the disk’s partition style to the firmware mode. If those checks pass, repair Windows startup files or investigate storage drivers. Re-clone when the first copy is incomplete or missing required system partitions.
This guide covers a typical x64 Windows 11 or Windows 10 installation moved to an internal replacement drive in the same PC. The startup checks also apply to a cloned HDD. Keep the original drive available as your rollback copy while you work on the SSD.
Find Where Startup Fails After Cloning
Start with what the computer actually shows. A drive missing from the firmware’s storage list needs a different investigation from a Windows installation that reaches a blue screen.
| What you see | Check first | Next section |
|---|---|---|
| The SSD is absent from the storage-device list. | Installation, connection, power, and interface compatibility. | Connection and boot selection |
| The SSD is detected, but the PC returns to BIOS or shows “No bootable device.” | Firmware mode, the EFI partition, and the firmware boot entry. | Disk layout and firmware mode |
| The computer still starts Windows from the old drive. | The selected boot entry and dependence on the old disk. | Test without the original drive |
| A recovery screen mentions BCD or a missing boot file. | Windows startup files on the cloned disk. | Repair Windows startup files |
| Windows reports INACCESSIBLE_BOOT_DEVICE. | Storage-controller settings, drivers, and hardware access. | Check storage drivers |
| The clone reported errors or left out system partitions. | The source’s condition and the scope of the copy. | Re-clone an incomplete copy |
A black screen can occur at several stages, so confirm hardware detection and boot selection before changing startup files.

Check the SSD Connection and Boot Selection
Confirm the SSD Is Detected as a Storage Device
Open the computer’s firmware setup using the key listed in its manual. Look under storage, SATA, or NVMe information. The drive’s appearance here confirms detection, while the boot menu answers a separate question: whether the computer has a usable way to start Windows from it.
If the drive is missing, shut down and disconnect power before checking its installation:
- 2.5-inch SATA SSD: check both the data and power connections. On a desktop, a known-working cable or supported SATA port can help isolate a connection fault.
- M.2 SSD: check that it is fully seated and that the slot supports its interface. An M.2 SATA drive and an M.2 NVMe drive are not interchangeable in every slot.
- SSD still in a USB enclosure: install it in the intended internal connection before judging an ordinary internal-system clone. A portable Windows installation over USB is a separate workflow.
If detection remains unreliable, resolve the hardware or connection problem before repairing BCD or copying the disk again.
Select the Correct Windows Boot Manager
On a UEFI Windows installation, select Windows Boot Manager associated with the replacement SSD. Depending on the firmware, the SSD model may appear beside that entry. Use the one-time boot menu to test it, then save the working entry as the first boot option.
On a Legacy BIOS installation, select the replacement disk itself. If there are multiple similar entries, use the disk model and the independent test below to establish which one starts the clone.
Test the Clone with the Original Drive Disconnected
Shut down, then temporarily disconnect the original system drive according to the computer’s service instructions. Leave the replacement SSD installed and try to start it. Keep the old drive’s partitions intact.
- The SSD boots: continue to the final verification checks.
- It only boots when the old disk is connected: startup files may still be on the original disk, or the firmware may still be selecting its boot entry.
- It fails with or without the old disk: follow the firmware-mode and startup-repair checks.
For a laptop without straightforward drive access, use the manufacturer’s supported procedure rather than disconnecting components while powered on.
Match the Disk Layout to the Firmware Boot Mode
Check Whether the Cloned System Uses GPT or MBR
If the original installation still starts, open Disk Management, right-click the cloned disk’s label, and choose Properties > Volumes. Read its partition style. Check the replacement disk itself, since its layout may differ from the source.
If Windows cannot start, use the recovery Command Prompt described in the next section. Run diskpart, followed by list disk. An asterisk in the GPT column identifies a GPT disk. Compare capacity and disk details before selecting it; disk numbers can change between environments. Enter exit to return to Command Prompt.
Use the Matching UEFI or Legacy Configuration
| Windows system-disk layout | Matching startup configuration |
|---|---|
| GPT with an EFI System Partition | UEFI, using the appropriate Windows Boot Manager entry. |
| MBR with a BIOS system partition | Legacy BIOS or an available, compatible CSM configuration. |
Use the configuration intended for that Windows installation. For a standard Windows 11 setup, follow the UEFI/GPT path. Enabling Legacy mode is not a way to make a GPT clone start.
If you deliberately need to move an MBR installation to UEFI, plan a conversion separately. Microsoft’s MBR2GPT documentation explains validation requirements and the firmware change needed afterward. Do not convert a disk simply because the clone has not booted yet.
If the screen explicitly reports a Secure Boot violation, follow the PC manufacturer’s guidance for that error and bootloader. Record the original settings before making changes. Disabling Secure Boot is not a general repair for a missing EFI partition or damaged Windows files.
Repair Windows Startup Files on the Cloned SSD
Use this path when the SSD is detected and the startup configuration matches, but Windows still reports a boot-file error or returns to recovery. Keep the original disk disconnected during the repair so that changes are directed at the replacement.
Run Startup Repair from Windows Recovery
Start with Windows’ automatic repair. Have the BitLocker recovery key available if the installation is encrypted.
- Boot from compatible Windows installation media. For the UEFI/GPT path, select its UEFI entry in the boot menu.
- Choose Repair your computer rather than starting an installation.
- Open Troubleshoot > Advanced options > Startup Repair, then select the Windows installation if prompted.
- Let the repair finish. Shut down, remove the USB, and test the SSD again.
If it cannot repair the installation, note the reported result before continuing. Microsoft’s Startup Repair instructions describe its recovery options.
Identify the Windows and System Partitions
Return to Advanced options > Command Prompt. Before writing boot files, identify the cloned disk and the partitions on it. Enter commands one at a time:
diskpart
list disk
select disk N
detail disk
list partition
list volume
exit
Replace N with the replacement SSD’s actual disk number. Compare its model, capacity, and partition layout. The volume list can include the installation USB, so use the disk and partition details to establish which volumes belong to the SSD.
In the examples below, W: means the cloned Windows volume’s actual letter in recovery. It is a placeholder, not a letter you must assign. Substitute the letter shown on your computer and confirm that the expected installation exists:
dir W:\Windows\System32
Windows may normally call its system drive C: while recovery gives it another letter. If the volume is locked, unlock it with its recovery key before continuing. Do not initialize or format a volume because its files are temporarily inaccessible.
Repair Boot Files on a UEFI/GPT System
Locate the existing EFI System Partition on the cloned SSD. Confirm its partition type and FAT32 filesystem; size alone does not identify it. If the partition is missing, move to the re-cloning section.
Use an unused temporary letter, shown here as S:, for that partition. Replace N and P with the confirmed disk and EFI partition numbers:
diskpart
select disk N
select partition P
detail partition
assign letter=S
exit
Run the following only after W: and S: refer to the correct Windows and EFI partitions:
bcdboot W:\Windows /s S: /f UEFI
This copies UEFI boot files to S: and creates the BCD store there. The /s option does not create a Windows Boot Manager entry in firmware NVRAM. If the firmware still lacks a working entry, use its supported Add Boot Option procedure, where available, to select \EFI\Microsoft\Boot\bootmgfw.efi on the cloned SSD. Otherwise, follow the manufacturer’s boot-entry recovery procedure. See Microsoft’s BCDBoot reference for the parameter behavior.
Remove the installation USB and test the SSD after the repair. A successful file-copy message is a step toward recovery; the independent boot test establishes whether startup now works.
Repair Startup on a Legacy/MBR System
For a confirmed MBR installation, identify the primary partition intended to hold BIOS startup files. It is often System Reserved, although some installations place those files on the Windows partition. Do not assume it is partition 1.
Inspect it with DiskPart. If that confirmed system partition is inactive, select it and run active. This flag does not check or create boot files, so marking an arbitrary partition active can prevent startup. Microsoft’s active command documentation explains that distinction.
If the selected system partition has no drive letter, assign an unused one with assign letter=S; otherwise, use its existing letter. Enter exit before running BCDBoot. Where Windows and startup files share a partition, both placeholders below refer to that same volume.
With S: representing the identified BIOS system partition and W: the Windows volume, rebuild the BIOS startup files:
bcdboot W:\Windows /s S: /f BIOS
If the diagnosis specifically identifies damaged MBR boot code, bootrec /fixmbr addresses that code. It does not convert GPT to MBR or replace a missing Windows installation. Follow the matching repair in Microsoft’s Windows startup troubleshooting guide, then restart without the USB.
Check Storage Drivers After a SATA-to-NVMe Clone
If Windows reaches INACCESSIBLE_BOOT_DEVICE, investigate access to the system disk. A controller setting or driver can matter even when the firmware detects the SSD. Microsoft’s 0x7B guidance identifies storage hardware, drivers, and configuration changes among the possible causes.
- Review recent firmware changes. If you changed AHCI, RAID, or VMD settings during troubleshooting, compare them with the original working configuration and the PC manufacturer’s instructions. Avoid cycling through modes at random.
- Obtain the matching storage driver. Use the PC or motherboard maker’s driver for the exact controller and Windows version.
- Distinguish recovery access from Windows access. A driver loaded into rescue media can make the SSD visible there, but it does not automatically install that driver into the cloned Windows system.
- Prepare the installation using the manufacturer’s supported method. Where supported, install the required driver in the working source Windows installation before cloning again. Otherwise, follow its instructions for servicing the offline Windows installation.
Moving a clone into a different PC introduces additional hardware differences. Rebuilding BCD alone does not address those differences.
Re-Clone Windows When the First Copy Is Incomplete
Re-cloning makes sense when the earlier copy omitted system partitions, stopped with errors, or left the target without a usable Windows installation. If the original Windows installation has the same underlying fault, copying it again may reproduce that fault.
Check Which System Partitions Were Copied
Copying the Windows volume alone can leave startup files behind. On a UEFI installation, the EFI System Partition contains the boot environment; the Windows partition contains the operating system. The MSR supports partition management, while the recovery partition holds Windows recovery resources. Their roles are different, as shown in Microsoft’s UEFI/GPT partition documentation.
Also inspect the original disk arrangement. Some computers have Windows on one physical disk and the system partition on another. Cloning every partition from only the Windows disk can still leave the new SSD dependent on the other drive.

Choose Disk Clone or Migrate OS for the Replacement
Use Disk Clone to replace a whole disk, including its data partitions. Use Migrate OS when your task is to move the Windows system. Our comparison of disk cloning and OS migration explains that choice.
For either workflow, review the proposed target layout and confirm that the system-related partitions you identified are included. A single-partition copy is not a substitute for checking the complete startup path.
Re-Clone with Wittytool Disk Clone
Wittytool Disk Clone brings disk cloning, system migration, backup, and restoration into one graphical workflow. For a failed clone, the useful part is being able to review what will be copied, identify the destination, and adjust its partition layout before starting again. SSD 4K alignment is enabled by default.

Our WinPE media creation feature also lets you run cloning outside the installed Windows session. If you need that route, follow the WinPE rescue disk tutorial. Back up the selected USB first: creating the rescue media deletes all of its partitions before writing the new data.
Download Wittytool Disk Clone on a working Windows PC to prepare the replacement copy and review its system layout.
Review the Destination and Complete the Clone
Use a readable, unencrypted source for this workflow. If a disk repeatedly disconnects or shows signs of physical failure, preserve its data before attempting more copies. Skipping unreadable sectors cannot recover their contents.
- Choose the workflow. Open Disk Clone for a full replacement, or Migrate OS for system migration.
- Identify the source. In Disk Clone, select the original disk by its model, capacity, and partition layout. In the system-migration workflow, verify that the detected Windows installation is the one you intend to move.
- Select the replacement SSD. Confirm that it is the destination and has sufficient capacity for the chosen operation.
- Review the target layout. Check the included system partitions and any partition-size adjustments. The Wittytool Disk Clone user guide shows the layout-review stage. Keep the intended firmware configuration in mind; do not enable conversion options without planning that change.
- Back up destination data and confirm the overwrite. Cloning replaces data on the selected destination. Recheck the source and destination before selecting Start Clone.
- Let the operation finish. Maintain stable connections and power. If it reports an error, inspect that result before repeating the same operation.
For the full replacement walkthrough, including preparation and destination selection, see how to clone an HDD to an SSD.
Verify That Windows Boots Independently from the SSD
A completed clone or repair is ready for an independent startup test. Shut down, remove the rescue USB, and leave the original system drive disconnected.
- Select the replacement SSD’s working boot entry and sign in to Windows.
- Open Disk Management and confirm that the running Windows volume belongs to the replacement SSD.
- Open important files and launch the applications you rely on.
- Restart once more and confirm that Windows starts from the SSD again.
- Check that your separate backup is accessible before deciding how to reuse the original drive.
When reconnecting the old disk, keep the new SSD’s boot entry first. If the problem returns only after reconnection, investigate the selected boot entry and any reported disk-identity conflict before deleting partitions.
Frequently Asked Questions
Why does the cloned SSD appear in BIOS but not in the boot menu?
Hardware detection and boot eligibility are separate. The SSD may lack a usable EFI boot environment or firmware entry, or its partition style may not match the selected boot mode. Check the layout and firmware mode before assuming the SSD itself has failed.
Why does Windows boot only when the old drive is connected?
The computer may still be using startup files or a boot entry associated with the old disk. The clone needs its own complete startup path. Repair the system partition on the SSD or repeat the migration with the required system partitions included.
Do I need to format or initialize the SSD again after cloning?
No. A completed system clone should already have a partition layout. Initializing or formatting it again does not repair its startup configuration and can remove data you need. Diagnose the existing clone before changing its partitions.
Should I repair the clone or clone the drive again?
Repair is appropriate when the Windows installation and required system partitions are present but startup files or settings need correction. Re-clone when the copy was incomplete, omitted required partitions, or ended with errors. Resolve hardware or driver problems first if they caused the failure.

