Fix BCD Error Windows 11: Step-by-Step Repair Guide

You hit the power button, expecting your usual Windows 11 login screen. Instead, you get a blue screen: File:\Boot\BCD missing, error code 0xc0000098. You restart. Same thing. Every reboot loops back to that same error, and the sinking feeling sets in—do I have to reinstall everything?

Take a breath. I've walked dozens of users through this exact scenario over the years, and in the majority of cases, a Windows 11 BCD error is fixable in 15–20 minutes using tools already built into Windows. Your personal files, applications, and settings can survive this. You just need to know the right order of operations.

This guide covers exactly that: the fastest fixes first (Startup Repair, bootrec, bcdboot), what to do when those fail, and how to stop this error from ever coming back.

---

What Is a Windows 11 BCD Error and Why Does It Appear?

The Role of BCD in the Windows 11 Boot Process

Think of the Boot Configuration Data (BCD) as your PC's boot-time navigation system. When you press the power button, firmware looks for the Windows Boot Manager (BOOTMGR), which then reads the BCD store to figure out where the OS loader files (winload.efi on UEFI systems) actually live. No BCD, no directions. And without directions, Windows simply can't start.

Microsoft's official documentation describes the BCD store as the repository for boot configuration parameters—everything from which operating system to load, to partition locations, to boot options like Safe Mode. It's not a user-friendly file; it's a structured binary database stored in the EFI system partition (ESP) on UEFI-based systems or the System Reserved partition on older MBR disks.

The BCD store exists precisely to manage complexity. If that file goes missing, becomes unreadable, or contains corrupted entries, the boot process collapses. That's when you see messages like File:\Boot\BCD missing or errors in the 0xc00000xx range.

Common Causes of BCD Corruption in Windows 11

In my experience, BCD corruption rarely comes from nowhere. There's almost always a trigger, even if it wasn't obvious at the time:

• Unexpected power loss or forced shutdown during a Windows update or mid-boot. This is, by far, the most common culprit I see in repair logs.
• Bad sectors or failing SSD. A weakening drive can corrupt the BCD file, and the "repair" won't stick until the underlying hardware issue is addressed.
• Dual-boot changes or third-party boot managers. Grub, rEFInd, or even a second Windows installation can overwrite or invalidate BCD entries.
• Manual BCD edits gone wrong. Using bcdedit without a clear understanding of what you're modifying can silently break the boot chain.
• Firmware or UEFI misconfiguration. Switching between Legacy (CSM) and UEFI boot modes after installation is a classic way to instantly invalidate the boot path.

Malware and rootkits can also target boot files, though that's less common than the scenarios above. If you suspect malware, deal with that after you can boot again.

---

Windows 11 BCD Error Codes: 0xc0000034 vs. 0xc0000098

The specific error code matters. It tells you whether the problem is the contents of the BCD or the file itself. Don't gloss over this—choosing the right repair from the start saves you time and frustration.

What Does BCD Error 0xc0000034 Mean?

0xc0000034 shows up with a message like: "The Boot Configuration Data for your PC is missing or contains errors." This typically means the BCD store exists, but the individual boot entries within it are missing, invalid, or referencing files that don't match the actual system layout.

I've seen this frequently after Windows feature updates that partially rewrote the BCD store, or when a user ran bcdedit to tweak boot settings and accidentally deleted a critical entry.

The direct repair path here is to inspect the store with bcdedit /enum and then rebuild it using bootrec /rebuildbcd or, more reliably, bcdboot. If those commands sound unfamiliar, don't worry—I'll walk through each one later in the guide.

What Does File:\Boot\BCD Error 0xc0000098 Mean?

0xc0000098 is different. This error says the Windows Boot Manager cannot find or read the BCD file at the expected location. In plain terms: the file itself is missing, unreadable, or sitting on a partition that firmware isn't checking.

This distinction matters. With 0xc0000034, you have a BCD store to try to salvage. With 0xc0000098, you're essentially starting from scratch—you need to recreate the BCD, not repair it.

One common trigger for 0xc0000098 on Windows 11, which I've seen in Microsoft Q&A threads repeatedly, is a BIOS boot order that points to the wrong disk. If you have multiple drives (an SSD for Windows and an HDD for media, for example), the system may try to boot from the HDD, find no BCD there, and throw the error. Before diving into command-line repairs, check your UEFI boot order and make sure the correct Windows drive is first.

---

How to Fix BCD Error Windows 11: Step-by-Step Repair Methods

Here's where we actually fix things. I've ordered these methods from least invasive to most thorough. Try them in sequence—each one builds on the previous, and jumping straight to bcdboot without trying the simpler fixes can unnecessarily complicate your situation.

Method 1: Run Startup Repair from Windows Recovery Environment

Startup Repair is Windows' automated boot diagnostic. It's not the most powerful tool, but it's the safest, and it occasionally works with zero technical effort required.

To get there:

1. Boot from a Windows 11 installation USB, or force the recovery environment by interrupting the boot process three times (power off during boot, then power on again; Windows should load WinRE automatically).
2. Select Troubleshoot → Advanced options → Startup Repair.
3. Let Windows diagnose. The process takes 5–10 minutes and may require a restart.

Here's my honest take: Startup Repair resolves some BCD issues—especially those caused by missing but recoverable entries—but it often fails on deeply corrupted stores or EFI partition problems. If it comes back saying "Startup Repair couldn't repair your PC," move on to Method 2. Don't run Startup Repair again and again expecting a different result; that's the definition of wasted time.

Method 2: Rebuild BCD with bootrec Commands

This is the classic command-line repair, and for good reason. bootrec rebuilds critical boot components from scratch.

From the Windows Recovery Environment:

1. Select Troubleshoot → Advanced options → Command Prompt.
2. Enter the following commands one at a time, waiting for each to complete:

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

• /fixmbr rewrites the master boot record (though on modern UEFI systems, this is less relevant).
• /fixboot writes a new boot sector to the system partition.
• /scanos scans all disks for Windows installations.
• /rebuildbcd scans for Windows installations and asks whether you want to add them to the boot list.

If /scanos finds your Windows installation and you're prompted with "Add installation to boot list? Yes/No/All", type Yes and press Enter.

Pay attention here: if /scanos returns "Total identified Windows installations: 0", something deeper is broken. Rather than repeating the commands endlessly, skip to Method 3 or Method 4. In my experience, a zero-installation result after /scanos usually means the BCD references a system it can't see—or the EFI partition itself is no longer recognized.

Method 3: Rebuild BCD with bcdboot for UEFI and Legacy Firmware

bcdboot is the most reliable BCD fix in Windows 11, period. While bootrec /rebuildbcd tries to reconstruct the store from scattered data, bcdboot recreates the entire BCD store using the actual Windows installation folder (C:\Windows) as the source of truth. It's a clean rebuild rather than a patch.

Here's how to target the right partition:

1. Open Command Prompt from WinRE.
2. Run diskpart to find your EFI partition:

diskpart
list disk
select disk 0
list volume

Look for the volume labeled EFI or System, typically FAT32 and 100–500 MB in size. Note its drive letter (it might be S:).

1. Exit diskpart and run:

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

Replace C: with your actual Windows partition letter and S: with the EFI partition letter you identified.

• Use /f UEFI on standard UEFI systems.
• Use /f BIOS for MBR-based, legacy firmware.
• Use /f ALL if you're dual-booting between UEFI and Legacy mode and want both boot paths covered.

I've used this command successfully in cases where bootrec failed entirely. If the BCD is missing, bcdboot doesn't care—it just rebuilds from C:\Windows and produces a valid store. The only requirement is that the Windows folder itself is intact.

Method 4: Repair BCD Manually with bcdedit

This is the advanced route, and I want to be clear: if Methods 1–3 didn't work, you probably shouldn't be hand-fixing BCD entries with bcdedit. But in case you need to inspect the damage, here's the manual workflow:

1. Back up the existing BCD store before touching anything:

bcdedit /export C:\bcdbackup

1. Unlock the BCD file so you can manipulate it:

attrib C:\boot\bcd -h -r -s
ren C:\boot\bcd bcd.old

1. Inspect the store to see what's actually wrong:

bcdedit /enum all

This shows every entry in the BCD store, including inactive ones. You'll see entries for Windows Boot Manager ({bootmgr}) and Windows Boot Loader ({default}). If {default} is missing or points to a nonexistent partition, that's your problem.

Creating a new boot entry manually with bcdedit /create is possible but finicky—you need to know the exact partition GUID and loader paths. For 99% of real-world BCD issues, bcdboot does this better and more reliably. Use bcdedit for diagnosis; use bcdboot for repair.

---

bootrec vs bcdboot vs bcdedit: Which Command Repairs Windows 11 BCD?

Quick Command Comparison for Windows 11 BCD Repair

If you're confused about which command does what, you're not alone. Here's a quick reference table I keep for clients:

Do You Need a Third-Party BCD Repair Tool on Windows 11?

In most cases? No. The built-in tools handle the standard BCD corruption scenarios well. I've seen third-party boot-repair utilities do more harm than good—especially free tools that weren't updated for Windows 11's UEFI requirements.

That said, there are two situations where a third-party tool might help:

1. You can't reach WinRE at all—not even from installation media. Some bootable Linux environments (like SystemRescue) include BCD repair utilities that can modify the EFI partition from outside Windows.
2. You're comfortable using bcdedit but want a GUI to visualize the boot entries.

If you go this route, stick to established tools with a verifiable track record. And regardless of the tool, back up your disk (or at least the EFI partition) before running anything from outside Windows. A wrong block-level write to the EFI partition can turn a fixable BCD error into a bricked boot.

---

How to Fix "Access Is Denied" in bootrec /fixboot and Other Windows 11 Repair Errors

Why bootrec /fixboot Fails with Access Denied

This is one of the most common issues I get asked about. You're running bootrec /fixboot from the recovery environment, and instead of a success message, you see "Access is denied."

The cause is almost always UEFI's protection of the EFI system partition. The ESP is deliberately locked down; Windows won't let you write to it without explicit elevation, and even from WinRE, bootrec /fixboot can be blocked.

Here's the fix I recommend:

1. Open Command Prompt from WinRE.
2. Launch diskpart and assign a temporary letter to the EFI partition:

diskpart
list disk
select disk 0
list volume
select volume 1   (change to match your EFI partition number)
assign letter=S:
exit

1. Now retry the fixboot command, or use bcdboot directly—which doesn't require the same boot-sector write that /fixboot attempts:

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

This bypasses the access-denied wall because it writes the boot loader files to the partition you explicitly unlocked.

Also, make sure you're actually in WinRE. Running bootrec from an elevated command prompt in normal Windows desktop mode won't work properly—boot sectors are in active use and protected.

Other Windows 11 BCD Repair Errors You Might Hit

• "The system cannot find the path specified" — This usually means the ESP isn't where the command expects it. Boot from installation media and run diskpart to confirm your EFI partition layout before retrying.
• "The requested system device cannot be found" — Your firmware boot mode doesn't match the disk layout. If your disk is GPT, you need UEFI mode enabled. If it's MBR, you need Legacy/CSM mode. Mismatched firmware and disk formats will defeat every BCD repair.
• "Total identified Windows installations: 0" — The BCD store is so corrupted that bootrec can't extract installation paths. Go straight to bcdboot and rebuild from the Windows directory. If that command also fails, the OS loader files are likely damaged—which brings us to the repair-vs-reinstall question.

---

What If Windows 11 BCD Repair Fails? Repair vs. Reinstall Decision Tree

Signs You Should Stop Trying to Repair the BCD

I'll be honest with you: some BCD errors are not repairable through boot-file manipulation. If you've tried:

• Startup Repair
• bootrec /fixmbr, /fixboot, /scanos, /rebuildbcd
• bcdboot C:\Windows /s S: /f UEFI
• Manual BCD rebuild with bcdedit

…and you're still seeing 0xc0000098 or 0xc0000001, the issue is likely not the BCD file itself. It's a sign that the Windows loader (winload.efi) is damaged, the registry hives are corrupted, or the system partition is physically failing.

The key indicator: if bootrec /scanos returns 0 installations consistently, and automatic repair does nothing, your OS partition data is unreadable at a deeper level. Continuing to "fix the BCD" at that point is like changing a car's GPS while the engine is seized.

How to Back Up Your Data Before a Windows 11 Reinstall

Before you perform a clean install, get your personal data off the drive. Here's how:

1. Boot from a WinPE or Linux live USB (like SystemRescue or Ubuntu Live). This gives you access to the internal drive independent of Windows.
2. Copy your user profile folders—Users, Desktop, Documents, Pictures, AppData (for application settings)—to an external drive. Linux live environments make this easy with just a file browser.
3. Use a disk imaging tool like Macrium Reflect Free or Windows Backup (if you previously created a system image) to capture an entire disk image. This is the most reliable path if you want a recovery safety net.

One warning: don't attempt the backup from the same Windows installation that's failing to boot. Interacting with a corrupted system during boot can cause further overwrites. External boot media is the safest route.

---

How to Prevent Windows 11 BCD Errors: Use chkdsk, Backups, and Safe Shutdowns

Run chkdsk and Check Disk Health

Once your system is running again, prevention matters more than the repair itself. I've seen too many users fix a BCD error, only to have it return a month later because the underlying drive was failing.

Run this command from an elevated (administrator) command prompt in Windows:

chkdsk C: /f /r

This scans for bad sectors, attempts recovery, and repairs file system corruption that can silently damage boot files. You'll need to schedule it for next reboot—that's normal.

Also, check your SSD/NVMe drive health. Tools like CrystalDiskInfo (free) or smartctl (from the smartmontools package) read the drive's S.M.A.R.T. status, which tells you about reallocated sectors, wear level, and pending errors. If the drive is showing yellow or red health warnings, don't wait for the next boot failure. Replace it and clone your data while you still can.

Shut Down Safely, Update Firmware, and Disable Fast Startup

Three habits that prevent BCD corruption:

1. Avoid forced shutdowns during boot or Windows updates. I get it—Windows updates are slow, and sometimes the machine freezes. But pulling the power during an update is the single most reliable way to corrupt boot-critical data. If the system is unresponsive, wait at least 15 minutes before forcing a power-down.

2. Keep BIOS/UEFI and storage drivers updated. Firmware bugs can cause intermittent boot failures that eventually corrupt the BCD. Check your motherboard manufacturer's support page for updates, especially if you're seeing boot issues on a new build.

3. **Disable Fast Startup if BC