Bcd Repair Windows 10 | Boot Fix Steps That Work

If your Windows 10 PC shows “Boot configuration data file is missing,” “Bootmgr is missing,” or a blue recovery screen with a code like 0xc000000f, the BCD is a common suspect. If you’re searching for bcd repair windows 10, start here. You can fix it with built-in recovery tools, even when Windows won’t load.

This guide keeps it simple. Start with automatic repair. If that fails, rebuild boot entries with a few commands. You’ll also see what causes BCD breakage and the checks that help you avoid a repeat.

What The BCD Does During Startup

The Boot Configuration Data (BCD) is a small database that tells the boot loader where Windows lives and how to start it. Firmware (BIOS or UEFI) hands off to boot code on the system drive, then that boot code reads the BCD and follows its entries into Windows.

When those entries don’t match your current disk layout, the boot chain breaks. You might see a recovery loop, a black screen, or an error that points to missing or damaged boot data.

Common Reasons BCD Entries Break

• Interrupted updates — A power cut or forced shutdown during an update can leave boot files half-written.
• Disk changes — Cloning to a new SSD, moving drives, or switching boot mode can shift identifiers the BCD points to.
• File system damage — Bad sectors or corruption can damage the BCD store or the boot manager files next to it.
• Partition edits — Resizing, deleting, or “cleaning” hidden partitions can remove the EFI System Partition on UEFI systems.

Bcd Repair Windows 10 With Built In Recovery Tools

Start with the least invasive options. Automatic repairs can restore missing boot files and fix common configuration issues without you touching partitions or guessing where files live. If you need a fast return to a working desktop, begin here.

Get Into Windows Recovery Mode

If you can still reach the sign-in screen, enter recovery from inside Windows. If you can’t, boot from Windows 10 installation media, or trigger automatic repair by interrupting startup a few times.

1. Use Shift Restart — Hold Shift, select Restart, then pick Troubleshoot and Advanced options.
2. Trigger automatic repair — Power on, wait for spinning dots, then hold the power button to turn off; repeat until recovery loads.
3. Boot from Windows media — Start from a Windows 10 USB/DVD, then choose Repair your computer.

Run Startup Repair First

Startup Repair checks boot files, boot manager settings, and basic disk access. It can restore missing pieces and correct common boot settings that keep Windows from being found.

1. Open Startup Repair — In Advanced options, select Startup Repair.
2. Select the Windows install — If asked, pick Windows 10 and sign in with an admin account.
3. Restart and test — Reboot normally and check whether Windows loads cleanly.

Try System Restore If The Timing Fits

If the boot issue started after a driver install, update, or system change, System Restore can roll back the system state without touching personal files.

1. Open System Restore — In Advanced options, select System Restore.
2. Choose a restore point — Pick one from before the boot issue started.
3. Restart after completion — Test a normal boot once it finishes.

If these tools can’t repair the PC, you’re ready for manual steps. At this point, bcd repair windows 10 is mostly about mapping the right partitions, then rebuilding boot entries from scratch.

Rebuild The BCD From Command Prompt

Open Command Prompt from recovery, then use a short set of commands to repair boot records and rebuild the BCD scan. Type carefully, and stop if your Windows drive isn’t detected.

Open Command Prompt In Recovery

1. Open Advanced options — Select Troubleshoot, then Advanced options.
2. Launch Command Prompt — Choose Command Prompt, then sign in if prompted.
3. Confirm the disk is seen — If the drive is missing, check BIOS/UEFI storage settings or cables.

Run Bootrec In A Safe Order

On many legacy BIOS systems (MBR), bootrec repairs boot records and rebuilds the BCD scan. On some UEFI setups, /fixboot can return “Access is denied.” If you hit that, skip it and use bcdboot in the next section.

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

1. Run fixmbr — Repairs MBR boot code on legacy BIOS systems.
2. Run fixboot — Writes a new boot sector; skip if it errors.
3. Run scanos — Searches for Windows installs not listed in the current BCD.
4. Run rebuildbcd — Adds detected installs back into the BCD store.

If rebuildbcd finds your Windows install, add it, then restart. If it finds nothing, your recovery session may be using unexpected drive letters, or boot files may need to be recreated on the EFI/System partition.

Fix Drive Letters And Recreate Boot Files With Bcdboot

bcdboot is a reliable method because it copies clean boot files from your Windows folder and rebuilds boot entries in one pass. It’s a strong choice after cloning drives, changing partitions, or switching between BIOS and UEFI boot settings.

Find The Windows Partition Letter

In recovery, Windows might not be C:. Use DiskPart to list volumes, then verify the Windows volume by checking for a Windows folder.

diskpart
list volume
exit

dir D:\Windows

Replace D: with the letter that matches your system. If the folder lists, you’ve got the right target.

Mount The EFI System Partition On UEFI PCs

On UEFI systems, boot files live on a small FAT32 EFI partition. It may not have a letter, so assign one temporarily.

diskpart
list volume
select volume 1
assign letter=S
exit

Select the small FAT32 volume, often 100–300 MB. Don’t pick your large Windows partition.

Recreate Boot Files And Boot Entries

Run the command that matches your boot mode. Replace letters to match your Windows volume and EFI/System volume.

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

bcdboot D:\Windows /s C: /f BIOS

1. Restart and test — Type exit, reboot, and check for a normal Windows load.
2. Remove temporary letters — If Windows shows the EFI partition in File Explorer, remove its letter in Disk Management.

Quick Reference Table For Common Boot Errors

Check Firmware Settings After A Successful Repair

Some boot failures persist because firmware settings no longer match the disk format. If you rebuilt boot files but the PC still won’t load, check that boot mode and boot order align with how Windows was installed.

Match Boot Mode To Disk Type

• Use UEFI with GPT — Common on modern PCs and required for Secure Boot on many systems.
• Use Legacy with MBR — Common on older systems and older installs.
• Keep the same mode after cloning — Switch modes only after you confirm Windows loads.

Pick Windows Boot Manager In Boot Order

On UEFI systems, the boot target should be “Windows Boot Manager” for the correct drive. If your firmware is booting the raw drive name, set Windows Boot Manager as the first entry, then save and restart.

Run A Quick Disk Check After You Boot

Once you’re back in Windows, check the file system. It’s a fast way to catch corruption that can break boot files again.

chkdsk C: /scan

Keep Boot Problems From Returning

After the PC starts again, do a few quick safeguards so you don’t land back in recovery after the next restart. These are small moves that pay off when the disk is aging or the power isn’t stable.

Reduce Update And Power Interruptions

• Let updates finish — Avoid hard shutdowns during update screens.
• Use stable power — Plug in laptops for updates; consider a UPS for desktops.
• Restart when you can watch — If Windows asks for a restart, pick a time you can monitor it.

Keep A Repair USB Nearby

A Windows 10 installer USB also opens the repair tools you used above. Having one ready saves time the next time boot fails.

• Create the USB — Use Microsoft’s Media Creation Tool on a blank drive.
• Test the boot menu — Confirm you can reach Repair your computer.
• Label and store — Keep it with the PC so it’s easy to find.

Back Up With A Restore Test

Backups only help if you can restore them. After you set one up, do a small restore test, like copying a folder back from the backup drive, so you know the path works.

• Back up personal files — Use an external drive for Documents, Desktop, and photos.
• Create a system image — Store one on an external drive after major changes.
• Confirm access from recovery — Make sure your backup drive can be read from recovery.

If Windows Still Won’t Start After Repair

If you rebuilt boot entries and still can’t boot, the issue may be a bad driver, deeper system file corruption, or storage settings that changed. The steps below keep data safety in mind while you narrow the cause.

Try Safe Mode From Recovery

If Windows starts loading but crashes or loops, Safe Mode can get you into the desktop with minimal drivers.

1. Open Startup Settings — In Advanced options, select Startup Settings, then Restart.
2. Choose Safe Mode — Press 4 for Safe Mode or 5 for Safe Mode with Networking.
3. Undo the last change — Remove the newest driver or update if the timing matches the failure.

Run Offline System File Checks

If system files are corrupted, Windows may fail after the boot loader hands off control. You can scan the offline Windows folder from recovery.

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

Replace D: with your Windows partition letter.

Use Reset This PC Only After Backup

Reset this PC reinstalls Windows. “Keep my files” preserves personal files but removes apps and drivers. If BitLocker is on, have the recovery key ready before you start.

1. Open Reset this PC — In Troubleshoot, select Reset this PC.
2. Pick Keep my files — Start with the less destructive option.
3. Reinstall drivers after — Install drivers from your PC maker once Windows returns.

After any fix, do one more restart. That second cycle confirms the boot chain is still stable and the entries point to the right place.

Send us your feedbackTell us what you thought about this post

⚠Please use a real email you check. If it's fake or mistyped, your message won't reach us and we can't reply — wrong addresses are rejected automatically.

Name *Email *

Your comment *

Quick check — what is …? *

Send feedback