Bcd Repair | Boot Errors Fixed In Minutes

For many Windows boot failures, bcd repair rebuilds the Boot Configuration Data so the firmware can find Windows and the PC can start normally.

The Boot Configuration Data (BCD) is a small set of startup records Windows uses to load the right system files. When those records get damaged or point to the wrong place, the machine can stall at a black screen, a repair screen, or a restart loop that never reaches the desktop.

Below you’ll get a clean, step-by-step path that works on Windows 10 and Windows 11. You’ll start with quick checks, then move into WinRE command-line fixes that rebuild boot files the right way.

What The BCD Does And Why It Breaks

During startup, your PC’s firmware (UEFI on most modern systems, BIOS on older ones) loads a boot manager. The boot manager reads the BCD to locate the Windows loader and the system partition it needs. If the BCD can’t be read, or it points to a Windows install that no longer matches the disk layout, startup stops.

BCD trouble usually comes from one of these situations.

Interrupted update — Power loss or a forced restart during an update can leave boot files half-written.
Drive migration — Cloning to a new SSD or moving partitions can change identifiers and paths.
File system damage — Bad sectors or repeated hard shutdowns can corrupt the partition that stores boot files.
Dual-boot changes — Another OS install can rewrite entries and point to the wrong loader.

On UEFI systems, boot files live on the EFI System Partition (ESP), a small FAT32 partition. On legacy BIOS systems, boot data is tied to the active system partition. The fixes below call out where that difference matters.

Common Boot Messages And Fast Checks

Boot errors often look scary, but the message can narrow the fix. Before you run tools, snap a photo of the full text and any code like 0xc000000f.

Quick Checks That Take Two Minutes

Unplug extras — Disconnect external drives and memory cards so the firmware doesn’t boot the wrong device.
Confirm the boot drive — In firmware settings, verify the Windows SSD is first in boot order.
Check recent changes — If this started after a clone or partition resize, suspect boot paths changed.

If those checks don’t change anything, use this table as a map.

On-Screen Message	Common Cause	Fast First Check
Boot Configuration Data file is missing	BCD store can’t be read or points nowhere	Run Startup Repair, then rebuild boot files
0xc000000f	Wrong device path or damaged EFI boot files	Confirm disk is detected, then run bcdboot
INACCESSIBLE_BOOT_DEVICE	Driver or storage mode mismatch, or disk errors	Run chkdsk, then offline SFC
Automatic Repair couldn’t repair your PC	Auto tool can’t fix boot chain or file damage is deeper	Check disk, then rebuild boot files manually

When the message mentions the BCD, the goal is straightforward: put fresh boot files on the correct partition, then make sure the firmware points to them.

Bcd Repair Commands You Can Run

You’ll run these from WinRE. If you can still boot sometimes, copy your files first. If you can’t boot at all, you can still back up from WinRE, then repair.

Get To Command Prompt In WinRE

Use a Windows USB installer — Boot it, pick Repair your computer, then open Command Prompt.
Use built-in WinRE — From Advanced options, choose Command Prompt.

Find The Right Drive Letters

Drive letters can change in WinRE, so confirm where Windows is installed before you run commands that copy files.

Locate the Windows folder — Try dir c:\windows, then dir d:\windows until you see it.
List volumes — Run diskpart, then list vol, then exit after you spot the EFI or System volume.

Try Startup Repair Once

Run Startup Repair — In WinRE, go to Troubleshoot, then Advanced options, then Startup Repair.

If it fails or loops back, move to the manual rebuild.

Rebuild Boot Files With Bcdboot

bcdboot recreates boot files from your Windows folder and writes new entries. On UEFI systems, you’ll usually copy to the EFI partition.

Mount the EFI partition — In diskpart, select the EFI volume, then run assign letter=S.
Copy fresh boot files — Run bcdboot X:\Windows /s S: /f UEFI and replace X with your Windows drive letter.
Restart and test — Reboot and see if Windows loads.

On legacy BIOS systems, use /f BIOS. If you can’t tell which mode you’re in, check firmware settings, then match the command to that mode.

Before you reboot, double-check that you mounted the correct EFI partition. On many PCs, it’s a small FAT32 volume with no label. If you mount the wrong volume, bcdboot can still run, but Windows may keep booting to the same error screen.

Confirm The EFI Partition Is The Right One

Check the file system — In diskpart, the EFI partition should show as FAT32 on most systems.
Check the size — Many EFI partitions are 100–300 MB. Bigger sizes are fine, but a multi-GB partition is often not the EFI.
Peek inside — After mounting as S:, run dir S:\ and look for an EFI folder.

If Windows uses BitLocker and you see a BitLocker code screen after repairs, that can be normal. Use your saved BitLocker code to proceed, then let Windows boot once. After you’re back in Windows, open BitLocker settings and confirm protection is on.

Once the PC boots again, you can review entries with bcdedit. Run bcdedit in an admin Command Prompt and look for unexpected device paths or extra loaders left over from a failed install. If you don’t need the extras, leave them alone until you’re sure the system starts cleanly for a few days.

Use Bootrec For Older Boot Chains

bootrec is still useful, mainly on BIOS installs. If you run it on a UEFI machine, bcdboot is usually the cleaner fix.

Scan for installs — Run bootrec /scanos to see if Windows is detected.
Rebuild entries — Run bootrec /rebuildbcd and add the install if prompted.

If you see “Access is denied” on bootrec /fixboot, skip the fight and return to bcdboot after mounting the EFI partition.

Check The Disk And Repair Windows Files Offline

bcd repair can fail again if the disk has errors. Run checks before you declare the job done.

Run a disk check — Use chkdsk X: /f and let it finish.
Repair system files — Use sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows.

Backup Steps Before You Change Boot Data

Most fixes here are safe, but they still change startup files. A quick backup gives you a fallback if you assign the wrong letter or need to undo a change later.

Copy Personal Files From WinRE

Plug in a USB drive, confirm its letter, then copy your user folder. Use your real username in the path.

Create a backup folder — Run mkdir E:\Backup and replace E with your USB drive letter.
Copy the user folder — Run xcopy X:\Users\YourName E:\Backup\YourName /E /H /C /I.

Export The Current BCD Store

Export BCD — Run bcdedit /export E:\Backup\bcd-backup to save a copy.
Copy EFI boot files — If the EFI partition is mounted as S:, run xcopy S:\EFI E:\Backup\EFI /E /H /C /I.

Repairing The BCD For Windows 10 And 11 Boot Errors

When you’ve got the basics down, the real win is choosing the right order. This sequence handles the most common real-world cases, including failed clones and update loops, without repeating work.

Step Order That Keeps Things Clean

Confirm boot mode — Check firmware settings for UEFI or legacy, then stick with that mode during repairs.
Confirm partitions — In diskpart, verify the EFI partition exists on UEFI systems.
Fix disk errors — Run chkdsk on the Windows partition first.
Rebuild boot files — Run bcdboot to write fresh boot files to the system partition.
Test a cold reboot — Shut down fully, then start again to confirm the fix survives a full restart.

When A Cloned SSD Won’t Boot

On a clone, the firmware may still point at the old drive, or the clone tool may have skipped the EFI partition. You can often fix this without reinstalling.

Disconnect the old drive — Boot with only the new drive connected so the firmware can’t pick the wrong entry.
Recreate EFI boot files — Mount the EFI partition, then run bcdboot X:\Windows /s S: /f UEFI.
Reconnect after it boots — Once Windows loads, reconnect the old drive and copy any leftovers you want. If you plan to sell the PC, wipe the old drive only after you’ve booted the new one twice without errors.

When A Update Leaves You In A Boot Loop

If the BCD rebuild doesn’t help, the issue may sit inside Windows. WinRE has tools for that.

Try System Restore — Pick a restore point from before the update if one exists.
Remove recent updates — Use Uninstall updates, starting with the newest quality update.
Run offline file repair — Use the offline SFC command again after chkdsk finishes.

When Nothing Works And How To Prevent A Repeat

At some point, rewriting boot files stops being productive. If a drive is failing, you can rebuild entries all day and still end up back at the same screen.

Signs It’s Time To Check Hardware

Changing error codes — The message changes each boot, or Windows boots once then fails again.
Repeated disk repairs — Chkdsk keeps finding the same errors every run.
Slow reads — Simple folder listings hang or take a long time in WinRE.

Reset Paths That Get You Running

Use an in-place repair install — If you can boot, run Windows setup inside Windows and choose to keep files and apps.
Reset Windows — From WinRE, use Reset this PC and pick Keep my files if you want a quicker rebuild.
Do a clean install — Wipe partitions only after your backup is checked, then install Windows fresh.

Habits That Reduce BCD Trouble

Keep a repair USB — Create it while the PC is healthy so you’re not scrambling later.
Let updates finish — Give updates time, and avoid cutting power during the final restart.
Clone the EFI partition — After a migration, confirm the new drive can boot while the old drive is disconnected.
Watch drive health — Use SMART tools from the drive maker and replace a drive that shows rising error counts.

If you’re still stuck again after all steps above, stop and gather facts before you try more commands. Write down the error code, your boot mode, and whether the EFI partition is present. That short checklist keeps the next troubleshooting attempt focused and safe.