Fix Error 0xc000014c: Boot Configuration Data Is Corrupt

The fast answer. Error 0xc000014c ("The Boot Configuration Data for your PC is missing or contains errors", usually naming \Boot\BCD or \EFI\Microsoft\Boot\BCD) means Windows Boot Manager can't read the BCD store — most often after a power loss or disk write error damaged it. Boot into Windows Recovery (WinRE), run Startup Repair once, and if that fails rebuild the BCD from Troubleshoot → Advanced options → Command Prompt:

bootrec /scanos
bootrec /rebuildbcd

Type Y when it offers to add the Windows installation, then reboot. On a UEFI/GPT machine, rebuild the boot files with bcdboot instead (Step 5).

Why this happens

Corrupt or missing BCD store — the PC lost power or was forced off while boot data was being written, or a disk write error damaged the file. This is the most common cause.
File-system damage on the boot or system partition — the same unclean shutdowns can corrupt the NTFS or FAT32 volume the BCD lives on.
Manual BCD edits or boot-manager tools — a mistake in bcdedit, a dual-boot setup, or a partition/clone operation left the store invalid.
Damaged system files — less often, the error names a registry file such as \Windows\system32\config\system instead of the BCD.
A failing drive — if the BCD keeps corrupting after you rebuild it, suspect bad sectors.

Step-by-step fix

Step 1 — 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 Repair your computer. If the BCD is too damaged for the on-disk recovery environment to load, the install USB is the reliable route. Then go to Troubleshoot → Advanced options.

Step 2 — Run Startup Repair

Choose Startup Repair and let it finish. It detects and rebuilds many damaged BCD stores automatically. Reboot and test before running commands.

Step 3 — Rebuild the BCD with bootrec

In Advanced options → Command Prompt, run:

bootrec /scanos
bootrec /rebuildbcd

When /rebuildbcd lists a Windows installation, type Y to add it. Reboot and test.

Step 4 — Legacy BIOS: rename the damaged BCD and rebuild (if bootrec finds 0 installations)

If bootrec /rebuildbcd reports "Total identified Windows installations: 0", the old store is blocking the rebuild. This is Microsoft's documented sequence — back up the store, strip its hidden/system/read-only attributes, rename it, then rebuild:

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

Use the letter of the volume that actually holds the \Boot folder — in WinRE the System Reserved partition may be C: and Windows may be D:. Check with dir C:\boot first. Type Y to add the installation and reboot.

Step 5 — UEFI/GPT: rebuild the boot files with bcdboot

On UEFI machines the BCD lives on the small FAT32 EFI System Partition. Give that partition a letter and let bcdboot recreate the store from the Windows folder:

diskpart
list disk
sel disk 0
list vol
sel vol <EFI-FAT32-vol#>
assign letter=S:
exit
bcdboot C:\Windows /s S: /f UEFI

The EFI partition is the ~100–500 MB FAT32 volume. Replace C:\Windows if your Windows volume has a different letter in WinRE. You should see "Boot files successfully created." Skip bootrec /fixboot here — on UEFI it often returns "Access is denied"; see the full bcdboot walkthrough.

Step 6 — Check the disk

Repair file-system damage on the Windows volume (use the correct letter):

chkdsk C: /f /r

If chkdsk reports bad sectors, or the BCD corrupts again after a rebuild, treat the drive as failing: back up and plan a replacement rather than repeating repairs.

Step 7 — Repair system files offline

If the error names a Windows system or registry file rather than the BCD, run System File Checker against the offline install:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

If that doesn't clear it, use Advanced options → System Restore to roll back to a restore point from before the error.

Data safety: bootrec, bcdboot, and renaming the BCD touch only boot data, not your documents. But 0xc000014c can be a sign of a drive with write errors. If the files matter and you have no backup, image the drive to a known-good external disk before running chkdsk /r, which stresses weak sectors. In diskpart, double-check volume numbers — never format or clean the wrong volume, and never run repairs on the only copy of irreplaceable data.

GRAM tip: These repairs run in Windows Recovery, which is already 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 unexpected shutdowns and disk errors, and let its AI agent confirm why the BCD corrupted 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 trigger Automatic Repair, where Startup Repair and Command Prompt are available. If a badly damaged BCD stops WinRE from loading, you need a 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.)

Will rebuilding the BCD delete my files?

No. The BCD is a small boot database; bootrec /rebuildbcd and bcdboot rewrite boot configuration only. Your documents and programs are untouched. Custom boot entries (for example a second OS) may need to be re-added afterward.

Why does bootrec /rebuildbcd say "Total identified Windows installations: 0"?

The existing damaged store is still in place, so bootrec doesn't offer to add the install. On legacy BIOS systems, export and rename the old \boot\bcd (Step 4) and run bootrec /rebuildbcd again. On UEFI systems, use bcdboot (Step 5).

The error keeps coming back after I fix it. What now?

Repeated BCD corruption points to hardware or power: a drive developing bad sectors, a loose or failing cable, or frequent forced shutdowns. Run chkdsk C: /f /r, back up your data, and check the drive's health with SMART or the manufacturer's diagnostic tool before trusting it again.