Software⏱️ 4 min read📅 2026-06-11

How to Fix: dd cloned Windows disk to new SSD – boot from clone with error "windows/system32/winload.efi" missing

How to fix the error "windows/system32/winload.efi missing" when booting a cloned Windows disk on a new SSD.

Quick Answer: Use the `bootrec` command in Windows to update the boot configuration and point to the correct EFI partition on the new SSD.

📋 Table of Contents

  1. ⚠️ Common Causes
  2. 🚀 How to Resolve This Issue
  3. 🎯 Final Words

The error 'windows/system32/winload.efi missing' occurs when attempting to boot from a cloned Windows disk on a new SSD. This issue affects users who have cloned their old external SSD to a new one using a cloning tool like dd, but now encounter this error when trying to boot the new SSD.

This error can be frustrating as it prevents the user from accessing their Windows installation. Fortunately, there are several methods to resolve this issue, and in this guide, we will walk you through the primary fix method and an alternative approach.

⚠️ Common Causes

  • The primary reason for this error is that the EFI/boot partition on the cloned disk points to content on the original disk. When the new SSD is booted, the system looks for the 'winload.efi' file in the Windows directory, but it's not present on the cloned disk.
  • An alternative reason could be that the cloning process did not properly transfer the EFI boot configuration, leading to the missing 'winload.efi' file.

🚀 How to Resolve This Issue

Update EFI Boot Configuration

  1. Step 1: Boot from a live Linux distribution (such as Ubuntu) and mount the new SSD to a directory. Then, navigate to the EFI boot partition on the new SSD and run the following command: `sudo efibootmgr -c -d /dev/disk5 -p 2 -f \EFI\Microsoft\Boot\bootmgfw.efi -l "Windows Boot Manager" -x` This will update the EFI boot configuration to point to the Windows Boot Manager.
  2. Step 2: Next, run the following command to reset the boot order: `sudo efibootmgr -c -d /dev/disk5 -p 2 -r \EFI\Microsoft\Boot\bootmgfw.efi` This will set the Windows Boot Manager as the default boot entry.
  3. Step 3: Finally, reboot the system and verify that it boots successfully from the new SSD.

Reclone EFI Partition

  1. Step 1: Use a cloning tool like dd to reclone the entire disk, including the EFI partition. This will ensure that all necessary files, including 'winload.efi', are transferred correctly.
  2. Step 2: Run the following command: `sudo dd if=/dev/disk2 of=/dev/disk5 bs=64K status=progress` This will clone the entire disk, including the EFI partition, to the new SSD.

🎯 Final Words

To resolve the 'windows/system32/winload.efi missing' error when booting from a cloned Windows disk on a new SSD, you can try either updating the EFI boot configuration or recloning the EFI partition. The primary fix method involves updating the EFI boot configuration using efibootmgr commands, while an alternative approach is to reclone the entire disk, including the EFI partition, using a cloning tool like dd. By following these steps, you should be able to resolve this issue and boot successfully from your new SSD.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions

🛠️ Related Fixes

How to Fix: Pc crashes shortly after launching game (rainbow

Fix Pc crashes shortly after launching game (rainbow six siege). Compl

How to Fix: Installing an APK on a locked down phone

Installing an APK on a locked down phone: Try using a rooted device, e

How to Fix: New PC build- no signal and no clue

Fix New PC build- no signal and no clue. Complete troubleshooting guid