Fix "winload.exe Is Missing or Corrupt" on Windows 10/11

The fast answer. A screen reading File: \Windows\system32\winload.exe with a status such as 0xc000000f or 0xc0000225 means Windows Boot Manager started but couldn't load the Windows OS loader. winload.exe is the loader on legacy BIOS machines; UEFI machines use winload.efi instead. Most of the time the boot configuration (BCD) is damaged or points at the wrong partition, not the file itself. Boot into Windows Recovery (WinRE), run Startup Repair, and if that fails, rebuild the BCD from Command Prompt:

bootrec /scanos
bootrec /rebuildbcd

Type Y when it lists your Windows installation, then reboot.

Why this happens

Corrupted or misconfigured BCD — disk write errors, a power loss or forced shutdown (often mid-update), or a manual BCD edit left the boot entry broken. This is the most common cause.
BCD points at the wrong partition — after cloning to a new drive, resizing partitions, or deleting the System Reserved partition or a second OS, the entry no longer finds \Windows.
Damaged boot code — the master boot record or boot sector was overwritten by another OS installer, a disk tool, or a boot-sector virus.
winload.exe itself is damaged — bad sectors or an interrupted update corrupted the file in System32.
Failing drive or cable — read errors in the boot area surface as this message.

Step-by-step fix

Step 1 — Unplug external drives and confirm the error text

Remove USB drives, SD cards, and external disks, then power on. If Windows starts, the PC was booting from the wrong device. If not, read the screen: if it names winload.efi, the PC boots in UEFI mode and you want the winload.efi fix instead. Don't flip the BIOS between Legacy/CSM and UEFI on a guess — that just changes the error.

Step 2 — Get into Windows Recovery (WinRE)

Force three failed boots (power on, then hold the power button as the Windows logo appears, three times) to open Automatic Repair, or boot from a Windows 10/11 install USB and choose Next → Repair your computer. Because this error stops boot before Windows loads, the install USB is often the more reliable route. Then go to Troubleshoot → Advanced options.

Step 3 — Run Startup Repair

Choose Startup Repair and let it finish. It diagnoses and fixes many broken boot configurations automatically. Reboot and test. If it reports it couldn't repair the PC, continue.

Step 4 — Rebuild the BCD with bootrec

In Advanced options → Command Prompt, run:

bootrec /scanos
bootrec /rebuildbcd

Type Y when Windows is found, then reboot. If it finds nothing, or the error returns, back up the old store, rename it, and rebuild a fresh one:

bcdedit /export C:\bcdbackup
attrib C:\boot\bcd -r -s -h
ren C:\boot\bcd bcd.old
bootrec /rebuildbcd

Drive letters in WinRE often differ from normal Windows. On BIOS machines the \Boot folder usually lives on the small System Reserved partition, which WinRE may label C: while Windows shows up as D:. Run dir C:\boot and dir D:\Windows to find the right letters, and substitute them above.

Step 5 — Repair the boot code

Still failing? Rewrite the master boot code and the boot sector:

bootrec /fixmbr
bootrec /fixboot

/fixmbr overwrites only the master boot code. If the partition table itself is damaged, it won't fix that. Reboot and test.

Step 6 — Recreate the boot files with bcdboot

If the BCD keeps breaking or System Reserved was damaged, copy fresh boot files from your Windows folder. First find the partitions:

diskpart
list vol
sel vol <System-Reserved-vol#>
assign letter=S:
active
exit
bcdboot C:\Windows /s S: /f BIOS

System Reserved is the small NTFS volume (roughly 100–500 MB). If there's no separate System Reserved partition, select the Windows volume instead. active marks the partition the BIOS boots from; it applies only to MBR disks. Replace C:\Windows with the real Windows path in WinRE. Look for "Boot files successfully created," then reboot.

Step 7 — Check the disk and repair winload.exe itself

If the boot configuration is fine and the error persists, the file or the disk is damaged. Check the Windows volume, then run the offline System File Checker (use the Windows letter from Step 4):

chkdsk C: /f /r
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

If chkdsk reports bad sectors, or the error comes back within days of a repair, treat the drive or cable as the real fault: reseat the cable, run the drive maker's diagnostic, and plan a replacement.

Data safety: bootrec, bcdboot, and renaming the BCD change only boot data, not your files. The risky parts are chkdsk /r, which reads every sector and can push a failing drive over the edge, and diskpart, where one wrong volume number is easy to pick. If the files matter and you have no backup, image the drive to a known-good external disk first. Never run clean, format, or delete partition for this error, and never run repairs on the only copy of irreplaceable data.

GRAM tip: These repairs run in Windows Recovery, which lives on the broken PC or any Windows install USB. Once the machine boots again, plug in GRAM — a free portable repair toolkit that runs from a USB inside Windows — to check the drive's SMART health, read the event logs for the forced shutdown or failed update that broke the boot files, and let its AI agent confirm the root cause so the error doesn't come back.

Download GRAM free See AI pricing →

FAQ

Can I fix this without a second working computer?

Usually, yes. WinRE lives on the broken PC itself — three failed boots open Automatic Repair, where Startup Repair and Command Prompt are available. If WinRE won't load, boot any Windows install USB (made on any PC, even a borrowed one) and choose Repair your computer. The repair itself needs no second computer. (GRAM runs inside Windows rather than from boot media — use it once the machine boots to verify disk health and confirm the root cause.)

What's the difference between winload.exe and winload.efi errors?

They're the same loader for different firmware. Legacy BIOS machines start \Windows\system32\winload.exe; UEFI machines start winload.efi. The BCD steps are similar, but the final boot-file rebuild differs: BIOS systems use bcdboot ... /f BIOS against System Reserved, while UEFI systems use bcdboot ... /f UEFI against the FAT32 EFI System Partition.

Will these repairs delete my files?

No. bootrec and bcdboot rewrite boot data only, and sfc replaces only damaged system files. chkdsk /f /r can move damaged fragments into FOUND.000 folders but doesn't wipe the drive. The real risk is stressing a failing drive, so copy important data off first.

Startup Repair says it couldn't repair my PC. What now?

Move on to the Command Prompt steps above — Startup Repair often fails on a BCD that needs a full rename-and-rebuild. Its log is saved at \Windows\System32\LogFiles\Srt\SrtTrail.txt on the Windows volume and records what it found. See the SrtTrail.txt guide for how to read it.