By Ailsa / Last Updated September 14, 2020

Winload.efi Missing or Contains Error

There was a user encountered the Winload.efi missing or contains errors problem like that:

"I recently buy a new Windows 10 laptop comes with a 256GB SSD drive, and I want to upgrade it to a 1TB SSD. Therefore, I clone the original SSD to the new one, and put the new 1TB SSD in my laptop, the laptop refuse to boot and get a blue screen of death (BOSD) error:


Your PC/Device needs to be repaired

The application or operating system couldn't be loaded because a required file is missing or contains errors.

File: \windows\system32\winload.efi

Error Code: 0xc0000225

I tried several ways to fix it, but failed. So how can I repair this Windows boot error 225 easily?"

Winload.efi Error 0xc0000225

Sometimes, you might encounter other error codes associated with Winload.efi file, like error code 0xc000000e after clone Windows 10, error code: 0xc000000f, winload.efi 0xc0000428, etc. This article will help you to resolve these errors with detailed steps.

The Causes to Winload.efi Error

Before repairing, you have to find the root cause why your Winload.efi file is missing after clone. The reason lies in the following factors:

1. The incorrect registry key. The source disk and target disk owns different ID for volumes and drive letter, so you have to change the registry key after cloning.

2. Improper UEFI settings. The UEFI and Legacy mode requires different boot files and algorithms. So, make sure you set up correct settings for your destination disk.

3. The corrupted BCD files. Sometimes, cloning will damage the BCD store files, and then you will get this Winload.efi 0xc0000225 error message. Just repair BCD files first.

Therefore, how to repair Winload.efi missing after clone? Don’t worry about it, we will provides the solutions to fix quickly in Windows 7/8/10.

How to Fix Winload.efi Error in Windows 10, 8, 7?

According to the causes, we offer these following quick solutions for you, just check it. let's have a glance at the content:

Solution 1: Disable Secure Boot
Solution 2: Use DiskPart to Repair
Solution 3: Check and Repair Windows System Files
Solution 4: Fix Corrupted BCD files

Solution 1: Disable Secure Boot

The Secure Boot will stop your system from accessing the winload.efi file if you have a UEFI based computer. So boot into BIOS or UEFI via F2, F8, F12, ESC or DEL key (varies depends on your PC manufacturer), and find the Secure Boot option in BIOS or UEFI, and then Disabled it.

Disable Secure Boot

If above steps are not working for you, try the next way.

Solution 2: Use DiskPart to Repair

1. Boot into the Windows installation media, then go to Repair your computer -> Advanced Options -> Troubleshoot -> Command Prompt.

2. Input these commands to fix winload error in Windows 7/8/10:

  • diskpart

  • list volume

  • select volume=n (where the n is refer to volume number of system reserved partition with "System" labeled)

  • assign letter=m (m is the proper drive letter that not in use)

  • bcdboot c:\Windows /s m: /f uefi (Replace the letter "c" with the letter of your system partition with the "Boot" Label)

Now restart your computer to check if it is solved, if nothing helps try solution 3.

Solution 3: Check and Repair Windows System Files

1. Open Command Prompt with Windows installation media, then run the following command:

  • sfc /scannow

Or input the following commands to winload.exe missing after clone error:

  • bcdedit /enum | find "osdevice" (to find the Windows installed partition drive letter)

  • sfc /Scannow /OFFBOOTDIR=C:\ /OFFWINDIR=C:\Windows (replace the C: with the Windows installed partition drive letter)

SFC Scannow

Solution 4: Fix Corrupted BCD files

If the above ways are not working, try this way. First of all, you have to prepare a Windows 7/8/10 installation media, then boot into recovery Environment and rebuild BCD store. If you have a Windows installation disc, refer to this text.

1. Boot into Windows Recovery Environment from the installation media.

2. Choose Repair your computer -> Advanced Options -> Troubleshoot -> Command Prompt.

3. Then type the following commands to execute one by one to fix Master Boot Record (MBR), Boot Sector, and BCD store:

  • bootrec /fixmbr

  • bootrec /fixboot

  • bootrec /scanos

  • bootrec /rebuildbcd

Rebuild BCD

4. Restart your computer to check if you are success.

Of course, if you don’t have a Windows installation disc, you could create one by yourself. The powerful third party media creation tool - AOMEI Backupper Standard will do you a big favor. Before repairing winload.efi error, please download AOMEI Backupper Standard to create WinPE bootable media. Besides, you could prepare a USB flash drive at least 16GB and connect it to your computer.

1. Open this freeware after installing, choose Tools -> Create Bootable Media on the main window.

Create Bootable Media

2. Choose Bootable Disc Type for your media, Linux – Create bootable disc based on kernel or Windows PE – Create bootable disc based on Windows PE. And press Next to go on.

Windows PE Bootable Disc

3. Select PE boot mode: Create Legacy bootable disc or Create UEFI bootable disc. Hit Next.

Windows UEFI Bootable Disc

★Tip: You could check the option: Download WinPE creating environment from Internet.

4. Choose the USB Boot Device. Hit Next to create Windows 7/8/10 bootable media.

Select USB Device

★Tip: you could burn the WinPE to CD/DVD, or export to an ISO file as well.

Create USB Bootable Disc Process

After creating bootable media (just a few minutes), boot your computer from this media, then AOMEI Backupper will run automatically, then go to Tools -> Windows Shell Command.

Windows Shell Command

Then repair Winlaod.efi missing after clone error easily according to the above commands to fix BCD. Then check if your computer is bootable. Besides, you might encounter Seagate DiscWizard not cloning problem, Transcend SSD Scope not working for system clone, etc, this freeware will work out for you.

An Easier Way to Clone

If you encounter problems continuously after/while cloning, maybe you could turn to AOMEI Backupper for help to clone hard disk, like clone HDD to SSD or larger HDD, clone Windows 7 to new hard drive. It’s a powerful hard drive cloning software for Windows XP, Vista, 7, 8, 8.1, 10 and supports multiple languages like English, French, German, Italian, Japanese, Simplified Chinese, Traditional Chinese, Spanish, Dutch, Turkish, etc. The disk cloning steps listed below to bypass the winload.efi missing after clone error:

1. Choose Clone -> Disk Clone on the main console.

Disk Clone

2. Choose Windows system disk as source drive to clone, and hit Next.

3. Select a larger HDD or SSD as destination, hit Next.

4. Preview the operations, and press Start Clone to avoid the Winload.efi missing after clone problem in Windows 10/8/7.

Start Clone

✍Sector by sector clone: Make sure your destination is equal to or larger than this source disk if check this option.
✍SSD Alignment: If your destination is a SSD drive, please tick this option to optimize the reading and writing speed for SSD.
✍To clone HDD or SSD that contains operating system between MBR and GPT, please upgrade to its Professional edition.
✍You will generate an unallocated space in the destination disk after cloning smaller drive to larger drive, you could merge unallocated space to C drive or other existing partitions, or create a new partition to fully use the storage space.

After cloning, change the first boot device as the destination disk (the cloned drive) in BIOS if required, and then boot your computer to the cloned disk.

Of course, you are allowed to backup entire hard disk to an image file, and then restore the image file to your destination disk, the same result as cloned disk and will not meet the Winload.efi missing after clone issue in Windows 10/8/7.


It’s easy to solve Windows\system32\winload.efi missing or contain errors problem according to the above solutions. If you are technicians, just try AOMEI Backupper Technician Plus to enjoy more advanced features like system clone, universal restore, command line utility, dynamic disk volume clone, etc.