Bcdboot Repair | Boot Files Fix Steps That Work

When a Windows PC refuses to boot, the cause is often simple: the boot files that point to Windows are missing, damaged, or sitting on the wrong partition. That can happen after a clone to a new drive, a firmware reset, a failed update, a dual-boot change, or a disk check that “fixed” things a bit too aggressively. The good news is that Windows includes a built-in tool for rebuilding those boot files without reinstalling the whole OS.

BCDBoot copies fresh boot files from a working Windows folder and writes a new boot configuration on the system partition. It’s fast when you aim it at the right Windows install and the right target partition. The tricky part is not the command itself. The tricky part is figuring out which partition should hold the boot files on your machine, then giving it a drive letter inside the WinRE session.

What Bcdboot Repair Does And When It Helps

BCDBoot is made for one job: set up, restore, or refresh the boot setup. It copies files like bootmgfw.efi for UEFI systems or bootmgr for BIOS systems, then builds or updates the BCD store on the target partition. Microsoft documents the general syntax as pointing BCDBoot at a Windows directory, with optional switches to target a system volume and firmware type.

BCDBoot has switches that change what it writes. /l sets boot menu language. /v prints more detail. /c builds a new BCD store instead of merging. Most repairs only need /s and /f, yet these options help when you’re cleaning up old boot entries.

This approach tends to help when Windows shows messages like “Boot configuration data is missing,” “The boot selection failed,” “0xc000000f,” “0xc0000225,” or when the machine drops into firmware setup after a drive swap. It also helps when a cloned Windows disk boots only when a second disk is attached, meaning the boot files are still living on the other drive.

It’s less useful when the Windows partition itself is encrypted and you can’t access it, when the drive is physically failing, or when the Windows folder is badly corrupted. In those cases you may still run it as a test, yet you’ll often need extra repair steps or a backup restore.

Prep Steps Before You Run The Command

You’ll get the cleanest result when you do a few checks first. These steps keep you from writing boot files to the wrong disk or choosing the wrong firmware mode.

1. Confirm firmware mode — In your PC’s firmware setup, note whether it’s set to UEFI, Legacy, or a mixed mode. Match your repair steps to that mode.
2. Boot into WinRE — Start from a Windows install USB, then open the WinRE tools and launch Command Prompt.
3. Find the Windows partition — Use diskpart to list volumes, then locate the volume that contains the Windows folder you want to boot.
4. Identify the system partition — On UEFI systems it’s the EFI System Partition (often 100–300 MB, FAT32). On BIOS systems it’s the active “System Reserved” partition or the active primary partition.
5. Assign drive letters — Give the Windows partition a letter like C: and the system partition a letter like S: inside WinRE so commands can target them.

Drive letters in WinRE often differ from what you see inside Windows. Don’t assume Windows is always C:. Treat it like a new setup and verify with directory checks. A quick photo of Diskpart output can save you from a wrong-disk mistake later. Write them down before rebooting.

Diskpart Quick Walkthrough

Diskpart is the simplest way to map volumes to drive letters while you are in WinRE. The general flow is list disks, select the right disk, list volumes, then assign letters. If you are unsure which volume is Windows, you can temporarily assign a letter and run a quick directory listing to see if it contains a Windows folder.

• Start diskpart — Type diskpart and press Enter.
• List volumes — Run list vol and note the size, file system, and labels.
• Select a volume — Use select vol N for the volume number you want.
• Assign a letter — Run assign letter=C for Windows or assign letter=S for EFI.
• Exit diskpart — Type exit to return to the normal prompt.

UEFI Windows Boot Repair With Bcdboot

Most modern PCs use UEFI with a GPT disk. In that setup, the EFI System Partition (ESP) is a small FAT32 partition that holds the bootloader files used by firmware. Your goal is to copy fresh EFI boot files from your Windows install to that ESP, then let firmware find Windows Boot Manager again.

After you assign letters, verify both sides. Check that C:\Windows exists on the Windows volume you picked. Check that S: shows as FAT32 and is the small EFI volume. Once those match, you can run BCDBoot with the /s switch to point to the system volume and /f UEFI to build UEFI boot files.

1. Verify the Windows folder — Run dir C:\Windows and confirm the folder list appears.
2. Verify the EFI volume — Run dir S: and confirm it’s accessible and shows a FAT32 volume.
3. Run BCDBoot for UEFI — Type bcdboot C:\Windows /s S: /f UEFI and press Enter.
4. Reboot and test — Close the window, remove the USB, and restart to see if Windows loads.

If the command succeeds, you’ll usually see a short success message. If you get an error, keep the letters and mode in mind. Most failures come from pointing at the wrong Windows folder, targeting the wrong partition, or mixing UEFI and BIOS switches.

If you’re fixing boot files after cloning to a new SSD, unplug extra drives for the first test boot. That removes guesswork and stops the firmware from picking an older Windows Boot Manager entry.

When You Have Multiple Windows Installs

On systems with more than one Windows installation, BCDBoot needs the Windows folder that you actually want to boot. You can check each candidate volume with dir and look for a valid Windows folder plus the usual directories. Then run BCDBoot from that source path.

Legacy BIOS Boot Repair With Bcdboot

Some machines still boot in Legacy BIOS mode, often paired with an MBR disk. In this setup, the system partition is a primary partition marked Active, and boot files like bootmgr live there. You can still use BCDBoot to refresh the boot files and recreate the BCD store, as long as you point the tool at the right active partition and use the BIOS firmware switch.

First, confirm which partition is marked Active. Diskpart can show it in the volume list, or you can switch to partition view for the selected disk. If your disk has a “System Reserved” partition, that is often the active boot partition. If it does not, the Windows partition itself may be active.

1. Assign letters — Give the Windows partition a letter like C: and the active system partition a letter like S:.
2. Run BCDBoot for BIOS — Type bcdboot C:\Windows /s S: /f BIOS and press Enter.
3. Set the active flag if needed — In diskpart, mark the correct partition active only if your layout requires it.
4. Reboot and test — Remove install media and restart.

On BIOS systems, a mismatched “active” partition can cause the same boot loop even after BCDBoot runs. If you are repairing a cloned disk, double check that the clone’s intended boot partition is active and the old disk is not stealing the boot role.

Common Bcdboot Errors And Fixes

BCDBoot is simple, yet it can fail with messages that feel cryptic. The fastest path is to map the error to a small set of likely causes: wrong path, wrong target, locked volume, or wrong firmware mode.

BitLocker And Encrypted Drives

If the Windows volume is protected by BitLocker, WinRE may see the partition but block access to the Windows folder. Use your BitLocker 48-digit password to access the volume. Then verify C:\Windows again and rerun BCDBoot.

UEFI Systems With Missing Or Damaged EFI Partition

If the EFI System Partition is missing, unformatted, or too small, BCDBoot has nowhere safe to write the boot files. You may need to recreate the ESP with disk management tools, format it as FAT32, then assign it a letter and run the same UEFI command. This is a higher-risk operation, so it’s smart to image the disk first if your data matters.

Boot Still Fails After Success

If BCDBoot reports success yet the PC still won’t boot, the next suspects are firmware boot order and duplicated boot entries. In firmware setup, check that Windows Boot Manager on the correct disk is selected. If you have multiple drives, unplug non-OS drives for one test boot so you can see whether the system starts from the intended disk.

Verify The Repair And Keep It From Coming Back

After Windows starts again, take a minute to confirm your boot layout is stable. This is where many “it worked once” repairs turn into lasting fixes.

1. Check disk layout in Disk Management — Confirm the EFI or System Reserved partition is on the same disk you expect to boot from.
2. Keep firmware boot order clean — Put the OS drive first, then remove stale entries that point to old disks.
3. Run a file system check — Use chkdsk on the OS volume if you suspect prior disk errors.
4. Back up once you are stable — Create a full image so the next boot failure becomes a quick restore.

If you are moving to a new SSD, do one extra test. Shut down, disconnect the old drive, and boot only from the new one. If it boots cleanly, you’ve confirmed the boot files live where they should.

Use bcdboot repair like a surgical tool. It can rebuild boot files fast, yet it won’t solve each startup failure on its own.

If boot issues return, check drive health warnings, power losses, and loose cables. Keep a fresh image backup and a WinRE USB so the next startup failure is a quick restore.

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