0xc0000225 and winload.efi: UEFI Boot Repair

When a Windows machine fails to start and displays 0xc0000225 with a message that winload.efi is missing or corrupt, the system is telling you that the UEFI firmware found the boot manager, but the boot manager could not locate the Windows boot loader. This happens during the POST-to-OS handoff, after the motherboard’s firmware has handed control to the EFI system partition (ESP). The error is not a hardware failure report; it is a missing-file report.

The ESP is a small FAT32 partition (typically 100–500 MB) that holds the boot manager (bootmgfw.efi), the boot configuration data (BCD), and the actual loader (winload.efi). When that partition is damaged, emptied, or its BCD entries are misconfigured, the boot chain breaks. The most common causes are:

1. Cloning or imaging a disk – A clone that copies only the Windows partition (C:) and not the ESP leaves the target without boot files. Even when the ESP is copied, its partition GUID may not match the BCD entry, causing 0xc0000225.
2. A failed Windows update – An update that interrupted while writing to the ESP can leave the BCD pointing to a non-existent loader.
3. Accidental deletion or formatting of the ESP – Often done when a user sees a small “System” partition and assumes it is junk.
4. Third-party partitioning tools – Tools that resize or move the ESP without updating the BCD can break the boot chain.
5. BitLocker or other encryption – If the drive is encrypted and the recovery key is not available, the Windows volume cannot be read, and BitLocker normally shows its recovery screen first.

Distinguishing the Causes

Before attempting repairs, determine which cause applies. The table below helps you narrow it down.

What People Get Wrong About This Error

The most common misdiagnosis is assuming the hard drive is dead or the Windows installation is corrupt. People immediately reinstall Windows or replace the disk, when the actual problem is a few missing files on a 100 MB partition. This is a natural mistake because the error appears suddenly and the machine seems completely broken. But 0xc0000225 is a boot configuration error, not a disk error. A disk that is failing will typically produce different symptoms: slow reads, bad sectors, or a blue screen with a storage driver error. If the disk were dead, the firmware would not even find the boot manager.

Another common mistake is using a Windows installation USB to “repair” by running sfc /scannow or dism. Those tools repair the Windows partition (C:), not the ESP. The ESP is not a drive letter, so sfc cannot touch it. The correct tools are diskpart, to give the ESP a letter, and bcdboot, which rewrites the boot files on it.

Repair Steps (Least Destructive First)

These steps follow Microsoft’s own procedure in BCDBoot Command-Line Options: Repair the system partition. The tool that does the work is bcdboot: it copies fresh boot files from the Windows folder to the EFI system partition and builds a new BCD store. Hand-building a store with bcdedit is not needed and is easy to get wrong.

Before you start: if the drive uses BitLocker, have the recovery key ready. Changing the boot files usually makes BitLocker ask for it at the next start.

Step 1: Boot from Windows Installation Media

You need a Windows installation USB or DVD for your Windows version (10 or 11). Boot from it. At the first screen, press Shift+F10 to open a command prompt, or select your language, click Next, then Repair your computer > Troubleshoot > Advanced options > Command Prompt.

Step 2: Find the Windows Volume and the EFI Partition

Start diskpart and list the volumes:

diskpart
list volume

Two volumes matter. The Windows volume is the large NTFS volume; in the recovery environment it is often not C:, so note the letter shown (for example D:). The EFI system partition is a small FAT32 volume, usually 100–500 MB, labelled System in the Info column; it normally has no letter.

Give the EFI partition a letter. Select it by its volume number from the list, then assign a letter that is not in use:

select volume 3
assign letter=S
exit

Replace 3 with the volume number of the FAT32 System volume. Now check what is on it:

dir S:\EFI\Microsoft\Boot

If you see bootmgfw.efi and BCD, the partition has boot files but they are damaged or point to the wrong place. If the folder does not exist, the partition is empty.

Step 3: Rebuild the Boot Files with bcdboot (Most Common Fix)

First rename the existing store, so a damaged BCD is not carried into the new one:

ren S:\EFI\Microsoft\Boot\BCD BCD.old

If there is no BCD, this fails with “file not found”, which is fine. Then rebuild the boot files and the store, using the Windows volume letter you noted in Step 2:

bcdboot D:\Windows /s S: /f UEFI

Replace D: with your Windows volume letter. bcdboot copies bootmgfw.efi and the other boot files to the EFI partition and creates a new BCD store with an entry for that Windows installation. It does not change anything on the Windows volume.

A warning about the BCD store. bcdboot builds the new store from Windows’ template but carries over (imports) settings from a store it finds on the partition. That is why the old BCD is renamed first: if it is the cause, nothing from it should be copied forward. For the same reason, do not create a store by hand and load it with bcdedit /import: /import replaces the entire system store, and a hand-built store is a common way to turn a fixable boot problem into a harder one.

Restart without the USB. Because the command used /s, bcdboot does not write a firmware boot entry; the firmware finds the boot files through its default path on the EFI partition. If the PC does not find Windows, choose Windows Boot Manager or the drive in the firmware boot menu. Once Windows starts, running bcdboot C:\Windows from an elevated prompt adds the firmware entry.

Step 4: Reformat the EFI Partition (If the Files Are Still Corrupt)

If Step 3 fails with a write error, or the error returns, the file system on the EFI partition may be damaged. Reformatting it erases only that partition, not the Windows volume. Make sure S: is the small FAT32 System partition before you format it; check with dir S:\ and list volume again.

format S: /FS:FAT32 /Q
bcdboot D:\Windows /s S: /f UEFI

Microsoft lists formatting the system partition as an optional step in the same repair procedure.

Step 5: If the EFI Partition Is Missing Entirely

If list volume shows no FAT32 System volume, create one. This needs a GPT disk (UEFI systems use GPT); create partition efi does not work on an MBR disk. Every command below runs inside diskpart, including shrink, which works on the volume you select. Back up your data first if you can: resizing the Windows volume is normally safe, but a mistake at this step can cost data.

diskpart
list volume
select volume 2
shrink desired=300 minimum=300
list disk
select disk 0
create partition efi size=300
format quick fs=fat32 label="System"
assign letter=S
exit

Replace 2 with the Windows volume number and 0 with the disk that holds it. shrink frees 300 MB at the end of the Windows volume (diskpart shrink), and create partition efi makes the EFI system partition in that space (create partition efi). Then run bcdboot as in Step 3.

Step 6: Check for BitLocker

If the drive is BitLocker-encrypted, bcdboot cannot read the locked Windows volume, so unlock it first with the recovery key: manage-bde -unlock D: -RecoveryPassword <key> (use the Windows volume letter from Step 2). Then run the repair. If you do not have the key, the data on the volume cannot be read, and a reinstall will not recover it.

After the Repair

Once the machine boots, run sfc /scannow and dism /online /cleanup-image /restorehealth from an elevated command prompt to ensure the Windows partition is healthy. These are not boot repairs, but they fix file corruption that may have caused the update failure.

If none of these steps work, the Windows installation itself is damaged beyond repair, and a reinstall is the only option. Back up your data first using a live Linux USB or by attaching the drive to another machine.