Clonezilla cloned drive not booting
By Daniel Brooks Published 11 min read
On this page (8 sections)
In short: A Clonezilla cloned drive not booting usually points to firmware mode, partition layout or the bootloader path. Clonezilla copies each partition, the partition table and boot code, so the clone is logically identical to the source. Start with the source drive disconnected before testing or repairing.
Part of our guide on options after drive trash emptied
| First safety step | Disconnect source drive |
|---|---|
| Firmware modes | UEFI or legacy BIOS |
| Windows partition type | EFI system partition |
| Legacy active marker | Boot flag on system partition |
| Primary test | Three quick checks |
| Repair tools | Windows install media, live USB |
The short version
- Disconnect the source drive before any repair so you cannot overwrite it
- Match UEFI or legacy BIOS mode to how the original drive was installed
- Read the partition table before changing a flag or partition type
- Check the clone's BCD with the /store switch
- Repair the bootloader onto the clone, not onto the original
Why a cloned drive stops booting
Say you clone a working Windows drive with Clonezilla, swap the disks, and the new one shows no boot device. The clone can contain every needed Windows file yet remain absent from the startup path.
Clonezilla copies each partition, the partition table and the boot code saved with the disk. It does not change the computer's firmware mode or create a new firmware boot entry for different hardware.
The usual fault is a mismatch between the installed boot method and the way the computer starts. A missing EFI system partition, an incorrect active flag, an absent NVRAM entry or a damaged BCD can produce similar symptoms.
Both Clonezilla and Windows installation media will happily operate on any disk you select. Disconnect the source before opening either tool, because neither can know which disk you meant. We cover troubleshooting testdisk usb drive partition problems in its own article.
- The computer starts legacy BIOS mode while the clone needs UEFI, or the reverse
- The partition table lacks the marker or partition type used by the selected boot mode
- The boot files or firmware entry point to another disk or another Windows installation
- Copies partitions and boot code in one operation
- Works without a network connection
- Supports repeatable imaging and restore jobs
- Does not rebuild Windows boot entries for new hardware
- Does not convert BIOS installations to UEFI installations
- A wrong disk selection can overwrite the source
What Clonezilla actually copies
A disk clone restores each saved partition, the partition table and the boot code recorded by the imaging job. The result is logically identical to the source at the time of capture.
The firmware still decides how to start that disk. A clone can therefore contain a sound Windows installation while its EFI entry, active marker or BCD points somewhere unusable.
The three checks to run first
Check the firmware mode, partition table and bootloader path before changing files. These checks are quick and non-destructive when you only inspect listings and command output. If that sounds like your situation, read up on can i get deleted files back next.
Use the original computer's settings as your reference. Windows reports the installed mode, while a firmware boot menu shows whether entries begin with “UEFI:”. The clone must use the same boot method unless you deliberately convert it.
- Check 1: Read the original firmware mode and match it to the clone
- Check 2: Read the partition table and confirm the marker or EFI type
- Check 3: Verify the clone's BCD, boot files and firmware entry
| Check | Reading | What it means | Next move |
|---|---|---|---|
| Firmware mode | Windows shows BIOS Mode, or the boot menu lists UEFI entries | The clone must use the matching boot method | Select the matching firmware entry |
| Partition flags | The active marker or EFI type is missing | Firmware has no usable system partition | Correct only the marker or type required by the mode |
| Bootloader | BCD or boot files are absent or point elsewhere | Windows cannot continue after firmware starts | Rebuild the boot files on the clone |
| NVRAM entry | The clone is detected but has no Windows Boot Manager entry | UEFI has no registered path for the loader | Register the clone's EFI loader, then adjust boot order |
| Disk target | The expected Windows volume is missing | The image may have restored to another disk or layout | Compare disk model, capacity and partition sizes |
How to verify the bootloader on the cloned drive
Check the original installation's mode before you inspect the clone. Press Windows-R, enter msinfo32, and read BIOS Mode. “UEFI” means the clone needs an EFI system partition; “Legacy” means it uses the older active-partition method.
A firmware boot menu offers a second check. Entries prefixed with UEFI: use UEFI startup, while an entry without that prefix may use legacy startup. Firmware labels vary, so record the wording shown on your own board. We cover how to recover files after robocopy mirror in its own article.
Boot the Windows install media and choose Repair your computer, Troubleshoot, then Command Prompt. Use diskpart, list disk and list vol to identify the clone by model, capacity and partition sizes before assigning letters.
Assign the EFI partition a letter, such as S:. Then run bcdedit /store S:\EFI\Microsoft\Boot\BCD /enum. This reads the clone's BCD instead of the recovery environment's temporary store.
The output should identify a Windows Boot Manager and a loader entry. Compare its device and path with the clone's Windows volume. A missing store, an inaccessible path or a different volume points to the boot files rather than the Windows installation. We go through keeping files intact during migration step by step elsewhere on the site.
msinfo32shows whether the original installation uses UEFI or Legacy mode- diskpart with list disk shows whether the selected disk is GPT or MBR
- diskpart with list vol shows letters, labels and likely EFI volumes
bcdedit /store S:\EFI\Microsoft\Boot\BCD /enumreads the clone's BCD- dir on the EFI folder shows whether Microsoft boot files exist
- Shows the exact BCD store being inspected
- Uses tools available in Windows recovery media
- Lets you inspect paths before changing files
- Requires Windows installation media
- Disk numbers and temporary drive letters can confuse beginners
- A correct BCD cannot fix the wrong firmware mode
UEFI boot order can hide a working clone
UEFI firmware stores boot choices in NVRAM. Some boards do not create a Windows Boot Manager entry after a disk clone, so the clone never appears as a selectable startup option.
Open the firmware setup and check storage detection, UEFI boot order and the saved Windows Boot Manager entries. Put the clone's entry above other Windows entries after confirming its disk model.
Secure Boot can also reject a clone moved to different hardware. Test with Secure Boot disabled only as a temporary diagnostic, then restore it after the correct signed loader and firmware settings work. Before you commit to anything, it is worth looking at checking child's online activity.
How to check partition flags and active partitions
A partition listing tells you which boot method the disk supports. Read it before changing anything, because the active marker and EFI type serve different firmware systems.
Legacy BIOS uses an active flag on the system partition. Set that flag only when the original installation uses Legacy mode and the disk uses the matching MBR layout.
UEFI ignores the active flag. It looks for a FAT32 partition typed as an EFI System Partition, then loads files from its standard directory. An active flag alone cannot make a UEFI clone boot.
A Linux live USB with GParted can show the flag, partition type and file system without changing them. Select the clone by capacity and model, then read the table. Do not click Apply unless you have confirmed the target and chosen a specific repair.
- Boot a Linux live USB and choose the trial desktop option
- Open GParted and select the clone by capacity and model
- Read whether the disk is GPT or MBR and inspect each partition type
- Set an active flag only on the correct Legacy system partition
- Confirm the UEFI partition has the EFI System Partition type and FAT32 file system
| Feature | Legacy BIOS | UEFI |
|---|---|---|
| Boot marker | Active flag on one system partition | EFI System Partition type |
| Disk layout | Usually MBR | Usually GPT |
| File system | Often NTFS for Windows and FAT32 for system files | FAT32 for the EFI partition |
| Where firmware looks | Active system partition | EFI partition containing boot files |
| Common failure | Active flag is missing or on the wrong partition | EFI type, files or NVRAM entry is missing |
Steps to repair or reinstall the bootloader after cloning
Repair the bootloader only after the firmware mode and partition layout match. Keep the source disconnected, then identify the clone's Windows and system volumes in recovery Command Prompt.
Run diskpart, list disk and list vol. Select the clone by model and size. Select the EFI partition, if present, and assign it a letter with assign letter=S. Find the Windows volume by its directory contents, since recovery letters often differ from normal Windows letters.
For a UEFI installation, run bcdboot W:\Windows /s S: /f UEFI, replacing W: with the clone's Windows letter. For a Legacy installation, use the matching system partition and run bcdboot W:\Windows /s S: /f BIOS.
The command copies boot files and creates the required BCD data. On UEFI systems, check firmware afterward for a new Windows Boot Manager entry and place the clone's entry first in boot order.
Reboot with the installer removed. If the clone still fails, return to the readings rather than repeating the same command. A hardware change, Secure Boot setting or damaged Windows volume can require a different repair.
- Boot the Windows install USB and open Command Prompt from Repair your computer
- Run diskpart, then list disk and list vol to identify the clone
- Assign a letter to the clone's EFI or system partition
- Find the clone's Windows volume by checking its folders
- Run bcdboot with
/f UEFIor/f BIOSto match the installation - Reboot with the installer removed and test the clone alone
- Rebuilds boot files without reinstalling Windows
- Creates a fresh BCD for the selected Windows volume
- Works when the Windows files remain intact
- Windows installation media is required
- Recovery drive letters differ between computers
- It cannot repair missing or damaged Windows files
A safe workflow for testing the clone
Treat the original drive as read-only evidence while the clone is being tested. Keep a current image of the original if the data matters, because boot repairs can still go wrong.
Test the clone with the installer USB removed. A successful standalone boot proves the firmware, boot entry and Windows loader can work without help from the original drive.
Shut the computer down before reconnecting the source. If both disks remain installed, check the boot order again and confirm Windows is using the intended disk.
Keep one known-good image on separate media. That gives you a recovery path if a later repair, drive failure or firmware reset affects the working installation.
- Disconnect the source drive physically before repair work
- Take a fresh image of the original before changing partitions
- Test the clone with the installer USB removed
- Reconnect the original only after shutting down from a successful test
- Keep one known-good image on separate media
| Step | Protects against | Cost | Reversible? |
|---|---|---|---|
| Disconnect the source drive | Repair tools writing to the wrong disk | None | Yes, reconnect later |
| Make a fresh image | A failed repair destroying the only copy | Storage space and time | Yes |
| Test the clone alone | Boot order confusion hiding a working clone | A short test session | Yes |
| Keep a spare image | Drive failure after repair | One spare drive | Yes |
Match the firmware mode, read the clone's partition table and inspect its stored BCD. Keep the source disconnected until the clone boots independently.
Questions people still ask
Does a failed Clonezilla boot usually mean the image is bad?
No. Clonezilla can restore the partitions and boot code correctly while firmware mode, the partition layout, BCD or NVRAM entry remains wrong. Read the clone's BCD with bcdedit /store and inspect the partition table before restoring again.
Can I fix the clone without reinstalling Windows?
Often, yes, when the Windows files remain intact. Match the firmware mode, correct the mode-specific partition layout and run bcdboot against the clone's Windows volume. Reinstallation is the fallback for damaged system files.
Should I convert the clone from MBR to GPT or BIOS to UEFI?
Only when you intend to change the startup method. Conversion requires a suitable partition layout, an EFI system partition, boot files and a UEFI firmware setting. Matching the original mode is the safer diagnostic test.
What if the firmware menu shows no boot entry for the clone at all?
Check whether firmware detects the disk, then inspect UEFI boot order and NVRAM entries. Confirm the clone has an EFI System Partition and boot files. Some boards need the Windows Boot Manager entry registered again before it appears.
Can Secure Boot stop a cloned drive from starting?
Yes. A clone moved to different hardware can fail when Secure Boot rejects its loader or the firmware settings differ. Disable Secure Boot only for a controlled test, then restore it after fixing the signed boot path.
Can I boot the clone while keeping the original connected?
You can, but both disks might contain similar boot files or Windows entries. Disconnect the original for repair and the first standalone test, then reconnect it after the clone starts correctly.