sodcalculator

10 Tech How-To

Fix Error 0xc0000225 in Windows 10: 7 Proven Ways

Guide 10-12252 · Updated · Step by step

Error code 0xc0000225 in Windows 10 means the boot configuration data (BCD) is missing, corrupt, or points to a device that doesn’t exist, so Windows can’t start. You can fix it by rebuilding the BCD, repairing startup files, or restoring the system from a recovery environment — the exact method depends on what triggered the error. Below are seven proven fixes, from the simplest to the most advanced, with step-by-step instructions.

What Causes Error 0xc0000225?

This error appears during the boot process, usually as a blue screen with the message “Your PC/Device needs to be repaired.” The most common triggers are:

  • Corrupt BCD: A failed Windows update, improper shutdown, or disk error can damage the boot configuration data.
  • Missing or damaged boot files: Files like bootmgr or the \EFI\Microsoft\Boot folder may be deleted or corrupted.
  • Disk or partition issues: A failing hard drive, a changed partition layout, or a disconnected drive can make the BCD point to an unavailable location.
  • Recent hardware or software changes: Installing a new SSD, resizing partitions, or dual-booting with another OS can break the boot chain.
  • BIOS/UEFI settings: Incorrect boot order, disabled Secure Boot, or a switch from UEFI to Legacy mode can cause this error.

Before You Start: Create a Windows 10 Recovery Drive

All fixes below require booting into the Windows Recovery Environment (WinRE). If Windows won’t start, you’ll need a recovery drive or installation media. Create one on another working PC:

  1. Insert a USB drive (at least 8 GB).
  2. Search for “Create a recovery drive” in Windows and open it.
  3. Check “Back up system files to the recovery drive” and follow the prompts.

Alternatively, download the Windows 10 Media Creation Tool from Microsoft’s website and create a bootable USB installer. You can use it to access “Repair your computer” on the setup screen.

Fix 1: Run Automatic Startup Repair

This is the easiest fix and often resolves the error if the BCD is slightly corrupted but still readable.

  1. Boot from your recovery drive or installation media.
  2. On the Windows Setup screen, click Next, then Repair your computer (bottom-left).
  3. Go to Troubleshoot > Advanced options > Startup Repair.
  4. Select your operating system and let the repair run. It may take several minutes.

If Startup Repair says it couldn’t fix the problem, try the next methods.

Fix 2: Rebuild the BCD with Bootrec

If the BCD is missing or corrupt, rebuilding it from Command Prompt is the most reliable fix. This method rewrites the boot configuration from scratch.

  1. Boot to WinRE as above, then go to Troubleshoot > Advanced options > Command Prompt.
  2. Type the following commands one by one, pressing Enter after each:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
  • fixmbr repairs the master boot record (MBR) on legacy BIOS systems.
  • fixboot writes a new boot sector.
  • scanos scans for Windows installations.
  • rebuildbcd rebuilds the BCD and asks you to add each installation found.

If fixboot gives an “Access denied” error, run bootrec /fixboot after typing diskpart, then list volume to find the EFI partition (usually FAT32, around 100 MB), select it, assign a drive letter, and run bcdboot C:\Windows /s S: (replace S: with the assigned letter). This is a more advanced step, but it’s necessary on UEFI systems.

Fix 3: Use bcdboot to Recreate Boot Files

This command copies the boot files directly from your Windows installation to the EFI or system partition. It’s more thorough than bootrec because it replaces missing files.

  1. Open Command Prompt from WinRE.
  2. Type diskpart, then list volume to identify your Windows partition (usually the largest NTFS volume) and the EFI partition (FAT32, ~100 MB). Note their drive letters (e.g., C: for Windows, S: for EFI).
  3. Exit diskpart with exit.
  4. Run: bcdboot C:\Windows /s S: (adjust letters as needed). This copies bootmgr and BCD files to the EFI partition.
  5. Close Command Prompt and restart.

Fix 4: Check Disk for Errors

If the error is caused by bad sectors or file system corruption, running chkdsk can help.

  1. Open Command Prompt from WinRE.
  2. Type chkdsk C: /f /r (replace C: with your Windows drive letter). The /f fixes errors, /r locates bad sectors and recovers readable data.
  3. Wait for the scan to complete. It may take a long time on large drives.

If chkdsk reports physical bad sectors, back up your data immediately — the drive may be failing.

Fix 5: Use System Restore or Reset This PC

If the error appeared after a recent change, restoring your system to an earlier point can undo the damage. If that’s not possible, a reset reinstalls Windows while keeping your files (or not).

  1. In WinRE, go to Troubleshoot > Advanced options > System Restore. Choose a restore point before the error started.
  2. If no restore points exist, go back and select Reset this PC. Choose Keep my files to preserve personal data (though installed apps will be removed).

Note: Reset requires the Windows installation files, which may be present on your recovery drive or you’ll be prompted to insert media.

Fix 6: Change BIOS/UEFI Settings

Sometimes the error is simply a boot mode mismatch. For example, if Windows was installed in UEFI mode but the BIOS is set to Legacy, or vice versa.

  1. Restart your PC and press the key to enter BIOS/UEFI (common keys: Del, F2, F10, F12 — check your manufacturer’s site).
  2. Find the boot mode setting (often under “Boot” or “Startup”). It may be called “UEFI/Legacy”, “CSM”, or “Secure Boot”.
  3. If you have a GPT disk, select UEFI (disable CSM). If you have an MBR disk, select Legacy (enable CSM).
  4. Also ensure Secure Boot is enabled if your Windows installation used it.
  5. Save and exit. Try booting again.

If you’re unsure which mode your Windows uses, check the disk partition style: in Command Prompt, type diskpart, then list disk. A GPT disk shows an asterisk (*) under the GPT column.

Fix 7: Replace the Hard Drive or SSD

If all software fixes fail, the drive itself may be dead or dying. Error 0xc0000225 can appear when the boot drive is physically disconnected, has bad sectors, or has failed entirely. Check if the drive appears in BIOS; if not, reseat the cables or try a different port. If the drive is detected but still fails to boot, you may need to replace it and reinstall Windows.

Frequently Asked Questions

Will I lose my files if I fix this error?

Most fixes (Startup Repair, bootrec, bcdboot, chkdsk, System Restore) do not delete personal files. Only “Reset this PC” with “Remove everything” deletes files, and even then you can choose to keep them. However, if the drive is failing, back up your data as soon as possible.

Can I fix 0xc0000225 without a recovery drive?

If your PC has a hidden recovery partition, you may be able to access WinRE by pressing a function key (like F11) during startup. If not, you’ll need a recovery drive or installation media from another computer.

Why does this error happen after a Windows update?

Updates can overwrite boot files or change the BCD, especially if the update is interrupted or the disk runs out of space. Running Startup Repair or rebuilding the BCD usually resolves it.

Is error 0xc0000225 the same as 0xc000000f?

No, but they’re related. 0xc000000f means the boot configuration is missing or contains errors, while 0xc0000225 specifically indicates the BCD is missing or the boot file path is invalid. The fixes are nearly identical.

Can I prevent this error from happening again?

Yes: always shut down Windows properly, avoid interrupting updates, keep your drive healthy (check SMART status), and create a system restore point before making major changes. Also, periodically back up your BCD with bcdedit /export C:\bcdbackup.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →