Bcdboot Failed To Copy Boot Files | Fix In 10 Minutes

What This Error Means And Why It Shows Up

The BCDBoot tool copies boot files from an installed Windows folder into the system’s boot partition, then writes boot entries so firmware can find Windows. Microsoft documents the available command options, including firmware targets like /f UEFI, /f BIOS, and /f ALL. Microsoft Learn lists the current BCDBoot switches and examples.

When you see the copy failure message, it usually means Windows can’t write to the partition that should receive the boot files. On UEFI systems, that target is the EFI System Partition (ESP), which is a small FAT32 partition. On legacy BIOS systems, the target is a System Reserved partition or an active NTFS partition marked for boot.

This often appears after disk cloning, swapping drives, converting MBR to GPT, resizing partitions, or repairing Windows from recovery mode. It can also show up when you point bcdboot at the wrong Windows folder, or when you pick the wrong firmware mode with /f.

Common Root Causes You Can Spot Fast

Bcdboot Failed To Copy Boot Files On Windows 10/11

If you’re reading this, you’re likely in one of two places: a running Windows install that still loads, or Windows Recovery (WinRE) where you have a Command Prompt. The second path is the safer one because the system partitions are less “busy,” and you can work even if Windows won’t boot.

Before you type commands, take a breath and get two details straight: your firmware mode (UEFI or legacy BIOS) and the letters WinRE assigned to your Windows and system partitions. Drive letters in WinRE often differ from what you see inside normal Windows.

Quick Check: Confirm UEFI Or Legacy BIOS

If Windows still boots, open System Information and look for “BIOS Mode.” If Windows doesn’t boot, you can still infer it from partition style: GPT usually pairs with UEFI and an EFI System Partition; MBR usually pairs with legacy BIOS and an active system partition.

Step-By-Step Repair From WinRE

This is the clean, repeatable path that fixes most cases. You’ll mount the system partition, confirm the Windows folder you want, then run bcdboot in a way that matches your firmware. The goal is simple: give bcdboot a writable target and a correct source.

Get To Command Prompt

1. Boot from Windows media — Use a Windows 10/11 installer USB, choose Repair your computer, then open Command Prompt.
2. Open the disks view — Type diskpart and press Enter.

Find The Windows Partition Letter

1. List volumes — Run list vol and note the volume with your Windows folder, often the largest NTFS volume.
2. Test the Windows path — Exit diskpart with exit, then try dir C:\Windows, dir D:\Windows, and so on until you see the Windows directory.

Mount The EFI System Partition And Assign A Letter

On UEFI systems, the ESP is usually 100–300 MB and formatted FAT32. It may show as “System” in diskpart. Your job is to pick that volume and give it a temporary letter, like S.

1. Re-enter diskpart — Run diskpart.
2. List volumes again — Run list vol and identify the small FAT32 volume.
3. Select the ESP volume — Run select vol X using the correct number.
4. Assign a letter — Run assign letter=S.
5. Exit diskpart — Run exit.

Run BCDBoot With The Right Switches

1. Copy files for UEFI — Run bcdboot C:\Windows /s S: /f UEFI and replace C: with your Windows letter if needed.
2. Copy files for BIOS — If you are on legacy BIOS, run bcdboot C:\Windows /s S: /f BIOS where S: is your active system partition letter.
3. Write both sets when unsure — Run bcdboot C:\Windows /s S: /f ALL on systems that can boot both ways, or when you’re repairing a disk that may move between modes.

What A Successful Run Looks Like

You’ll usually see a short success message and no errors. If you still get the same message, keep going to the next section. You’re close, and the remaining fixes are mostly about removing a write block or correcting the target partition. If you changed letters, write them down before you reboot later.

Fixes When The Copy Error Still Won’t Quit

When the basic mount-and-run steps don’t work, the fix is rarely mysterious. It’s often one of these: the system partition is read-only, the ESP is the wrong file system, the target is too small or full, or you’re pointing at a Windows folder that isn’t the one you mean to boot.

Clear Read-Only Attributes On The Target Partition

1. Open diskpart — Run diskpart.
2. Select the disk — Run list disk, then select disk 0 (or the disk that holds Windows).
3. Clear read-only — Run attributes disk clear readonly.
4. Check the ESP volume — Run list vol, select vol X, then attributes volume clear readonly.
5. Exit and rerun bcdboot — Run exit, then rerun your bcdboot command.

Make Sure The EFI Partition Is FAT32

UEFI firmware expects the ESP to be FAT32. If that partition was converted, damaged, or replaced with an NTFS partition, bcdboot may fail or the system may still refuse to boot even if files copy. If the ESP shows as NTFS, the clean fix is to recreate it as FAT32, then run bcdboot again.

1. Back up what you can — If the disk has data you can’t lose, clone it first.
2. Create a new ESP — In diskpart, shrink a little space if needed, create a 100–300 MB partition, then format it FAT32.
3. Assign a letter — Give the new ESP a letter like S:.
4. Rebuild boot files — Run bcdboot C:\Windows /s S: /f UEFI.

Point BCDBoot At The Correct Windows Folder

On systems with multiple Windows installs, old Windows folders, or a Windows-to-Go disk plugged in, it’s easy to aim at the wrong path. bcdboot copies from the Windows directory you provide, so confirm the source is the one you want.

1. List candidate drives — Run dir C:\, dir D:\, and look for a Windows folder with recent dates and the expected Users folder.
2. Use that letter in the command — Run bcdboot D:\Windows /s S: /f UEFI if D: is the correct Windows volume.
3. Reset the BCD store — Add /c when entries are messy: bcdboot D:\Windows /s S: /f UEFI /c.

Free Space And File System Checks

The ESP is small. If it’s crammed with leftover vendor tools, duplicate boot folders, or stray files, the copy step can fail. Also, file system errors can block writes even when a partition looks fine.

1. Check free space — Run dir S:\ and look for large folders you can remove, then delete only items you recognize.
2. Run a file system check — On NTFS Windows volumes, run chkdsk C: /f. On FAT32 ESPs, chkdsk can still help: chkdsk S: /f.
3. Retry the copy — Rerun the same bcdboot command after the check completes.

USB And Storage Driver Mixups

In WinRE, the Windows drive can change when a USB disk, SD card, or NVMe is present. If bcdboot points at the wrong install, it may fail or write boot files for a Windows copy you never use. Storage controller mode changes can hide the disk until the right driver loads.

1. Unplug extra drives — Leave only the Windows disk and installer USB.
2. Recheck the Windows path — Confirm X:\Windows exists before running bcdboot.
3. Match controller settings — Keep AHCI or RAID settings consistent with the install.

Checks After You Rebuild Boot Files

Once bcdboot runs cleanly, you still want to confirm the boot chain is set up the way your firmware expects. A little verification now saves you from another trip back into WinRE.

Verify The EFI Boot Folder Exists

1. List the Microsoft boot path — Run dir S:\EFI\Microsoft\Boot and confirm you see boot files and folders.
2. Check for a Boot folder too — If you used /f ALL, also check dir S:\Boot.

Reboot And Confirm Boot Order

1. Restart the PC — Exit Command Prompt and reboot.
2. Pick the right entry — If your firmware offers a boot menu, choose Windows Boot Manager on the correct disk.
3. Recheck BIOS mode — After booting, confirm BIOS Mode in System Information matches what you repaired.

When You Still Can’t Boot

If the system still won’t boot, the issue may be outside bcdboot: a failing drive, a missing storage controller driver, or firmware settings that block the disk. At that point, run built-in Startup Repair, test the drive health, and confirm the disk shows in firmware.

How To Avoid Seeing This Error Again

Boot partitions break most often during disk work. Cloning tools may copy partitions in the wrong order, resize the ESP too small, or change identifiers. Updates can also expose weak disks or file system damage. A few habits reduce repeat failures.

Safer Disk And Partition Habits

• Leave the ESP alone — Avoid storing files on it or assigning it a permanent letter.
• Keep free space on system partitions — Don’t shrink the ESP to the minimum; 200–300 MB gives breathing room.
• Shut down before moving drives — Hibernation and fast startup can leave volumes in a dirty state.
• Run periodic file checks — A quick chkdsk on the OS volume catches issues early.

Good Defaults For Most Repairs

If you only want one “safe bet” command to remember, it’s the one that matches your firmware mode and points at the right Windows folder. When the message bcdboot failed to copy boot files shows up, the fastest fix is usually mounting the ESP and rerunning the command from WinRE.

• UEFI and GPT disks — bcdboot X:\Windows /s S: /f UEFI
• Legacy BIOS and MBR disks — bcdboot X:\Windows /s S: /f BIOS
• Mixed repair situations — bcdboot X:\Windows /s S: /f ALL

If you reach this point and your PC boots, you’re done. If you still see bcdboot failed to copy boot files after mounting the correct partition and clearing write blocks, treat the disk as suspect and back up data before repeating aggressive partition work.

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