Fix BCDEdit Refusing to Add an Entry With Boot Configuration Store Could Not Be Opened

When you run BCDEdit to add a new boot entry, the tool may return the error “The boot configuration store could not be opened.” This error prevents you from modifying boot settings, adding a dual-boot option, or enabling debug mode. The cause is typically a missing or corrupted Boot Configuration Data store file, a permissions issue, or the command being run from the wrong environment. This article explains why the error occurs and provides step-by-step fixes to restore BCDEdit functionality.

Why BCDEdit Cannot Open the Boot Configuration Store

The Boot Configuration Data store is a registry-like file that holds boot settings for Windows. On a typical UEFI system, the store is located on the EFI System Partition at \EFI\Microsoft\Boot\BCD. On a legacy BIOS system, it resides in the System Reserved partition at \Boot\BCD. BCDEdit relies on this file to read, modify, or add entries.

The error “The boot configuration store could not be opened” appears when BCDEdit cannot locate or access the BCD file. Common reasons include:

• Running BCDEdit without administrator privileges. Standard user accounts cannot open the store.
• The BCD file is missing or corrupted. A failed Windows update, disk write error, or third-party tool may damage the store.
• The store path is not specified. BCDEdit assumes the store is in the default location, but if the system has multiple Windows installations or a nonstandard partition layout, the store may be elsewhere.
• The EFI System Partition is not mounted. On UEFI systems, the ESP must be assigned a drive letter before BCDEdit can access the BCD file.

Steps to Fix BCDEdit Store Access Errors

The following methods address the most common causes. Start with Method 1 and proceed if the error persists.

Method 1: Run BCDEdit as Administrator and Specify the Store

1. Open Command Prompt as administrator
   Press the Windows key, type cmd, right-click Command Prompt in the results, and select Run as administrator. Confirm the User Account Control prompt.
2. List the current boot entries
   Type bcdedit /enum and press Enter. If the command succeeds, the store is accessible and the issue is limited to a specific BCDEdit operation. If the error appears, proceed to the next step.
3. Identify the store file location
   If you have a dual-boot setup or an external Windows drive, determine where the BCD file resides. For a standard single-boot system, the store is at C:\EFI\Microsoft\Boot\BCD on UEFI or C:\Boot\BCD on BIOS. Use diskpart to assign a drive letter to the EFI System Partition if needed: run diskpart, then list disk, select disk 0, list partition, select partition 1, assign letter=S:, and exit.
4. Run BCDEdit with the /store parameter
   Type bcdedit /store S:\EFI\Microsoft\Boot\BCD /enum and press Enter. Replace the drive letter and path with the correct location. If the enumeration succeeds, use the same /store parameter for all subsequent BCDEdit commands, including adding entries. For example: bcdedit /store S:\EFI\Microsoft\Boot\BCD /create {ntldr} /d “Windows 10 Legacy”.

Method 2: Rebuild the BCD Store Using bootrec

1. Boot into the Windows Recovery Environment
   Restart the PC and press F11 or the manufacturer-specific key to enter the boot menu. Alternatively, from a working Windows installation, go to Settings > System > Recovery > Advanced startup > Restart now.
2. Open Command Prompt in WinRE
   Select Troubleshoot > Advanced options > Command Prompt.
3. Run bootrec commands
   Type bootrec /scanos and press Enter. This scans all disks for Windows installations. Then type bootrec /rebuildbcd and press Enter. When prompted, press Y to add each detected installation to the BCD store.
4. Exit and restart
   Type exit, remove any installation media, and restart the PC. Try BCDEdit again from an elevated Command Prompt.

Method 3: Manually Recreate the BCD Store

1. Open Command Prompt as administrator
   Press the Windows key, type cmd, right-click Command Prompt, and select Run as administrator.
2. Rename the existing BCD file
   Type ren C:\EFI\Microsoft\Boot\BCD BCD.bak and press Enter. If the file is in a different location, adjust the path accordingly. On BIOS systems, use ren C:\Boot\BCD BCD.bak.
3. Create a new BCD store
   Type bcdedit /createstore C:\EFI\Microsoft\Boot\BCD and press Enter. This generates a fresh, empty store file.
4. Add the Windows boot entry
   Type bcdedit /store C:\EFI\Microsoft\Boot\BCD /create {bootmgr} /d “Windows Boot Manager” and press Enter. Then run bcdedit /store C:\EFI\Microsoft\Boot\BCD /set {bootmgr} device partition=C: and bcdedit /store C:\EFI\Microsoft\Boot\BCD /set {bootmgr} path \EFI\Microsoft\Boot\bootmgfw.efi.
5. Restart the PC
   Close Command Prompt and reboot. The system should boot normally. Verify BCDEdit works by running bcdedit /enum.

When BCDEdit Still Fails After Rebuilding the Store

BCDEdit returns “The system cannot find the file specified”

This error indicates the BCD file path is incorrect or the EFI System Partition lacks a drive letter. Use diskpart to assign a letter to the ESP as described in Method 1, step 3. Then retry the BCDEdit command with the correct /store path.

Boot menu shows duplicate or missing entries after rebuild

If the rebuilt store contains incorrect entries, remove them with bcdedit /delete {identifier}. List all entries with bcdedit /enum, copy the GUID of the unwanted entry, and run bcdedit /delete {GUID}. Restart to confirm the boot menu is clean.

BCDEdit works in WinRE but not from the installed Windows

The BCD store on the system partition may be different from the one on the EFI System Partition. Compare the output of bcdedit /enum in WinRE and in Windows. If the stores differ, use the /store parameter in Windows to target the ESP store directly.

BCDEdit Error Fixes: WinRE vs Elevated Command Prompt

Item	Windows Recovery Environment	Elevated Command Prompt in Windows
Access method	Boot from installation media or use Settings > Recovery > Advanced startup	Right-click Start > Windows Terminal (Admin) or search cmd and run as administrator
BCD store location	Automatically detects the correct store on the system drive	May require /store parameter if the ESP is not mounted
bootrec tool availability	Available by default	Not available; use bcdedit directly
Best for	Rebuilding a corrupted store or fixing boot failures	Adding or modifying boot entries on a working system

The primary difference is that WinRE can access the system partition and ESP without extra steps, while the Windows environment may require manual drive letter assignment. Use WinRE when the store is severely corrupted or the system does not boot. Use the elevated Command Prompt in Windows for routine BCDEdit operations on a functioning PC.

After resolving the store access error, test BCDEdit by adding a simple entry such as a Safe Mode boot option. Run bcdedit /copy {current} /d “Windows 11 Safe Mode” and then enable Safe Mode boot with bcdedit /set {GUID} safeboot minimal. If this succeeds, the store is fully operational.