Recovery Error 0xc0000225: When Windows Won’t Boot (2026 Updated Guide)

Quick answer

Error 0xc0000225 means Windows can’t find or read the Boot Configuration Data (BCD) — the database that tells the system how to start. The fix is usually to repair or rebuild the BCD from the Windows Recovery Environment, not to reinstall Windows. Don’t run anything that modifies the disk before you’ve checked whether your data can be recovered first, and don’t proceed at all if BitLocker is on and you don’t have the recovery key.

Before you start

This is a boot failure, which means three constraints apply that don’t apply to most other Windows errors:

One: you cannot run anything from inside Windows. Every command on this page runs from the Windows Recovery Environment (WinRE), which you reach either by interrupting boot three times in a row, or by booting from a Windows installation USB. If your existing Windows install boots far enough to show the recovery screen, that’s the easier path; if it doesn’t, you’ll need a USB.

Two: BitLocker is the dangerous variable. If the drive is encrypted with BitLocker (the default on most modern business laptops, and increasingly on consumer Windows 11 installs), every recovery action requires the BitLocker recovery key. If you don’t have it, you can permanently lock yourself out. Find your recovery key at aka.ms/myrecoverykey — it’s saved to your Microsoft account by default. Look this up before you do anything else.

Three: any boot repair has some risk to your data. Most steps below are non-destructive, but if the underlying cause is a failing drive, even safe-looking commands can accelerate the failure. If your data is irreplaceable and you don’t have a current backup, the right next step is data recovery before repair — copy files off via a Linux live USB or by attaching the drive to another working PC.

Don’t reset Windows out of frustration. Reset This PC will erase data unless you specifically choose “Keep my files,” and even that option fails on a system that can’t fully boot. Methodical repair almost always preserves more.

What this error means

The boot loader (Windows Boot Manager, bootmgfw.efi on UEFI systems) reads the Boot Configuration Data store at startup to know what operating systems are installed and where they live on disk. When the BCD store is missing, corrupted, or pointing at files that no longer exist, the boot loader returns error 0xc0000225 with a message that usually reads “Your PC needs to be repaired” or “A required device isn’t connected or can’t be accessed.”

The core causes are:

Corrupted BCD. A power loss during a Windows update, or an interrupted disk write, can leave the BCD partially written. This is the most common case.
Missing or damaged boot files. The BCD points at files (bootmgfw.efi, winload.efi) that have been deleted, moved, or corrupted.
EFI System Partition (ESP) damage. On UEFI systems — that’s most modern Windows 11 PCs — the boot files live on a small (100–500 MB) FAT32 partition separate from the main Windows partition. If that partition is damaged or its drive letter has been lost, boot fails.
Wrong active partition or boot order. Less common in 2026 because UEFI systems don’t use “active partitions” the way old BIOS systems did, but still possible if BIOS/UEFI settings have been changed (boot mode switched between Legacy and UEFI, for example).
A recently installed Windows update that didn’t complete cleanly. Patch Tuesday churn occasionally leaves boot files in an unusable state. Microsoft usually issues an out-of-band fix when this happens, but if your machine won’t boot you can’t pull that fix.
A failing drive. The hardware-fault case. Less common than the others, but the most dangerous, because every repair attempt is reading from and writing to a drive that’s already unreliable.

Where this error appears

0xc0000225 shows up at startup, before the Windows logo finishes loading. The usual variants are:

A blue screen with “Recovery — Your PC/Device needs to be repaired” and the error code at the bottom.
The same blue screen with the message “The Boot Configuration Data for your PC is missing or contains errors.”
A boot loop where the system tries to start, fails, tries automatic repair, fails, and lands on the same error screen.
A cleaner failure pointing specifically at \Windows\system32\winload.efi — that variant means the BCD is intact but the file it’s pointing at is gone or corrupt.

If your error code is similar but slightly different — 0xc000000e or 0xc000000f instead — the diagnostic path is the same, but the underlying file at fault may differ. The repair commands below cover all three.

Common causes (ranked by frequency)

A failed or interrupted Windows update. The single most common cause. Power loss, force shutdown, or storage timeout during an update.
A drive on its way out. SSDs near end-of-life sometimes lose individual sectors that happen to contain boot files.
Disk imaging or partition tools that didn’t quite finish. Cloning to a new drive, resizing partitions, or restoring from a backup image — all can leave the BCD in a state inconsistent with the new layout.
Malware or unauthorised software touching the boot sector. Rare, but it happens. More common with older Windows 7 / 8.x systems than current Windows 11.
A BIOS/UEFI setting that changed. Boot mode switched between Legacy and UEFI, Secure Boot toggled, or boot order set to point at a drive other than the Windows install.

Fixes to try first

You’ll need either the recovery screen on your existing Windows install, or a Windows installation USB created on another working PC using the Microsoft Media Creation Tool. The USB needs to match the version of Windows installed on the broken machine — Windows 11 USB for a Windows 11 install, etc.

1. Get into the Windows Recovery Environment.

If your machine boots far enough to show the recovery screen, click Advanced options → Troubleshoot → Advanced options. If it doesn’t, force-power-off the machine three times in a row during boot (hold the power button for 5 seconds while the Windows logo is on screen), and Windows should drop to recovery on the fourth attempt.

If neither works, boot from the installation USB: at the language selection screen, click Next, then choose Repair your computer in the bottom-left — not Install. That puts you in WinRE.

2. Try Startup Repair first.

From WinRE: Troubleshoot → Advanced options → Startup Repair. This is Microsoft’s automated repair tool. It can fix the BCD, missing boot files, and minor file system damage. It runs for 5–30 minutes and doesn’t ask you anything.

If Startup Repair succeeds, reboot. If it loops back to the recovery screen with the same error, move to manual repair.

Startup Repair fails on roughly half of 0xc0000225 cases — that’s not a flaw in the tool, it’s that the tool is conservative and won’t run more aggressive repairs without confirmation.

3. Rebuild the BCD using bcdboot (preferred on UEFI).

From WinRE: Troubleshoot → Advanced options → Command Prompt.

First, identify your drives. The drive letters in WinRE are usually different from what you see in normal Windows. Run:

diskpart
list volume

You’re looking for two volumes: the Windows volume (typically the largest NTFS partition, where the Windows folder lives) and the EFI System Partition (a small FAT32 volume, usually 100–500 MB, marked “System”). Note their letters or partition numbers.

If the EFI partition doesn’t have a drive letter assigned, give it one — that’s a common problem and often the underlying cause of 0xc0000225:

select volume X     (where X is the EFI partition number)
assign letter=Z
exit

Now rebuild the boot files:

bcdboot C:\Windows /s Z: /f UEFI

Replace C: with the actual letter of the Windows volume in WinRE, and Z: with the letter you assigned to the EFI partition. The /f UEFI flag is critical on modern systems — using /f BIOS on a UEFI system will write the wrong files.

bcdboot is the modern, supported way to rebuild boot files on UEFI systems. The older bootrec /rebuildbcd works too, but it’s noisier, sometimes asks ambiguous questions about including Windows installations it finds, and on UEFI systems can produce a working but suboptimal result. Use bcdboot first.

4. If bcdboot fails, try bootrec.

Still in Command Prompt:

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

On Windows 11, bootrec /fixboot sometimes returns “Access is denied.” If that happens, the EFI partition needs reformatting and rebuilding from scratch — that’s a more involved procedure. Search Microsoft’s documentation for “bootrec fixboot access denied” rather than running the formatted commands you’ll find on third-party guides; one wrong drive letter and you’ve wiped the wrong partition.

5. Run chkdsk to rule out file system damage.

chkdsk C: /f /r

Replace C: with the actual Windows drive letter in WinRE. The /f flag fixes file system errors; /r locates bad sectors and recovers readable information. This takes a long time on large drives — leave it overnight if necessary. If chkdsk reports unrecoverable bad sectors, your drive is failing and any further repair work is buying time, not fixing the problem.

Advanced fixes

Check whether a recent Windows update is the cause.

If 0xc0000225 started appearing after a Windows update, you can uninstall the most recent update from WinRE: Troubleshoot → Advanced options → Uninstall Updates. Choose either “Uninstall latest quality update” (cumulative monthly patches) or “Uninstall latest feature update” (24H2 → 25H2 type upgrades).

This is occasionally the right answer — particularly in months where Microsoft has issued a known-bad update without yet pushing a Known Issue Rollback.

Check disk health from WinRE.

If you have a Windows installation USB, you can run PowerShell from WinRE (Troubleshoot → Advanced options → Command Prompt, then type powershell). From there:

Get-PhysicalDisk | Select FriendlyName, MediaType, HealthStatus, OperationalStatus

Anything other than “Healthy” / “OK” means the drive is failing and your priority should be data extraction, not boot repair.

Use a System Restore point if available.

From WinRE: Troubleshoot → Advanced options → System Restore. If restore points exist (and they often don’t on freshly-installed systems), this rolls the system back to a known-good state without touching personal files. It’s worth trying before anything more invasive.

If you are on a work or school device

Stop immediately. Don’t run any of the commands above. Corporate-managed devices are often configured with Secure Boot policies, custom BIOS settings, and BitLocker — touching boot files can trigger irreversible lockout that requires the IT team to intervene anyway, and may now require them to recover from backup.

Open a ticket with IT. Tell them: when the error started, what you saw on screen, whether you’ve made any recent hardware or BIOS changes, and whether you have your BitLocker recovery key (don’t recite it — they have it on file). They have managed-device recovery procedures that don’t require guesswork.

When to stop

Stop and either restore from backup or call a professional when:

BitLocker is enabled and you don’t have the recovery key. Don’t run any boot repair without that key in hand.
Your data is irreplaceable and not backed up. Recovery before repair, not after.
You’ve run Startup Repair, bcdboot, bootrec /rebuildbcd, and chkdsk, and the error persists. At that point, the cause is hardware or filesystem damage that needs hands-on diagnosis.
The drive is showing physical signs of failure — clicking sounds (mechanical), repeated read errors, SMART warnings, or system freezes during chkdsk. Continued use risks losing what’s still recoverable.
A recovery tool you don’t recognise is asking you to pay before it shows results, or claims it will “fix BSOD and boot errors automatically.” Those are scareware patterns; the genuine tools are built into Windows.

How to Run DISM and SFC Safely — for system file integrity issues that sometimes underlie boot failures
CRITICAL_PROCESS_DIED: Safe Diagnostic Steps — when Windows boots but crashes immediately afterward

Official references

FAQ

Will I lose my files fixing 0xc0000225?

Probably not. The repair commands above only touch boot files — the BCD store and the small EFI partition. Your personal files in the main Windows volume aren’t touched. The risk is non-zero (any disk operation has some risk), so back up first if your data is irreplaceable.

Can I fix this without a Windows installation USB?

If your existing Windows install boots far enough to reach the recovery screen, yes — everything you need is in there. If it doesn’t, you need a USB or another working PC to create one.

Why does Startup Repair say “couldn’t repair your PC”?

Startup Repair is intentionally conservative. It won’t run aggressive repairs that risk data, even when those are what’s actually needed. The next step is the manual bcdboot or bootrec work above.

Should I disable Secure Boot to fix this?

No. Secure Boot has nothing to do with 0xc0000225. Disabling it can introduce new problems (BitLocker may demand recovery, Windows may refuse to boot with the new policy) without fixing the original error.

Is 0xc0000225 caused by a virus?

Almost never. The error reflects boot file damage, which is far more often caused by interrupted updates, drive failures, or disk-imaging accidents than by malware. Don’t pay for a “boot virus removal tool” — they don’t exist as legitimate products.

↑ Back to top