How to Fix 0xc000014c Boot Configuration Error on Windows

Is your system throwing 0xc000014c? Follow this quick, zero-fluff guide to resolve the issue completely using terminal commands and system configurations.

What Is Error 0xc000014c?

The 0xc000014c status code indicates that the Boot Configuration Data (BCD) store is missing, corrupted, or contains invalid entries. Windows cannot locate a valid boot loader path, resulting in a blue/black screen with:

Your PC/Device needs to be repaired.
The Boot Configuration Data file is missing some required information.
Error code: 0xc000014c

Common Causes:

  • Disk cloning or partition resizing that broke BCD references
  • Power loss during a Windows Update
  • Dual-boot configuration gone wrong
  • UEFI/Legacy boot mode mismatch

---## Step 1: Boot Into Windows Recovery Environment

  1. Create a Windows Installation USB using the Media Creation Tool
  2. Boot from USB (press F12/F2/DEL at BIOS splash to access boot menu)
  3. Select Repair your computerTroubleshootCommand Prompt

---## Step 2: Identify Your Windows Partition

In the recovery Command Prompt, run:

diskpart
list volume

Identify your Windows volume (usually C: — look for the one labeled “Windows” with the largest size). Note the drive letter. Then exit diskpart:

exit

---## Step 3: Rebuild the BCD Store

Run these commands in sequence (replace C: with your Windows drive letter if different):

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

If bootrec /fixboot returns “Access is denied”, run this first:

bootsect /nt60 sys /mbr

Then retry the bootrec sequence.

---## Step 4: Manual BCD Rebuild (If Step 3 Fails)

If bootrec /rebuildbcd finds zero Windows installations, manually reconstruct:

bcdedit /export C:\BCD_Backup
attrib C:\Boot\BCD -h -s -r
ren C:\Boot\BCD BCD.old
bcdboot C:\Windows /s C: /f ALL

The /f ALL flag creates boot entries for both UEFI and Legacy BIOS modes, covering any firmware configuration.

---## Step 5: Verify and Reboot

Check the new BCD configuration:

bcdedit /enum

You should see a valid {bootmgr} entry pointing to \Windows\system32\winload.efi (UEFI) or \Windows\system32\winload.exe (Legacy). Remove the USB drive and reboot:

exit

Select Continue (Exit and continue to Windows).

---## Step 6: Post-Boot Verification

After Windows boots successfully:

  1. Open an elevated Command Prompt
  2. Run a system integrity check:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
  1. Verify no pending boot errors remain:
bcdedit /enum all

Pro Tip: If you’re dual-booting with Linux, the GRUB bootloader may overwrite BCD entries on kernel updates. Install os-prober on Linux and run update-grub after any Windows BCD repair to keep both entries valid.