Bcdedit The Boot Configuration Data Store Could Not Be Opened | Fix It Without Guesswork

You usually meet this error while trying to check boot entries, enable Safe Mode, switch boot debugging, or clean up old loader entries. “Could not be opened” can mean a permissions block, a missing BCD file, a hidden EFI System Partition, or a command prompt that isn’t pointed at the right Windows install.

Below you’ll find fixes for a PC that still boots and fixes you can run from Windows Recovery (WinRE) when it doesn’t.

What The BCD Store Is And Why BCDEdit Fails

Boot Configuration Data (BCD) is the database Windows uses to decide what loads at startup. Microsoft documents BCDEdit as the command-line tool that edits this store.

BCDEdit fails for three common reasons:

• No Admin Rights — The command prompt session lacks elevation, so bcdedit can’t read or write system boot data.
• Wrong Store Location — The BCD store exists, yet it is on a partition that has no drive letter in your current session, so the tool can’t find it.
• Damaged Or Missing Boot Files — The BCD file or related boot files are missing or corrupted, so the store can’t be loaded.

Read the exact line after the first sentence. Two variants steer you toward different fixes:

• Access Is Denied — This points to permissions, disk protection, or a locked system partition.
• The System Cannot Find The File Specified — This points to a missing store, a hidden EFI partition, or commands being run against the wrong disk.

Bcdedit The Boot Configuration Data Store Could Not Be Opened On A Working Windows Desktop

If Windows boots normally and you only see the error when running BCDEdit, start with the least invasive changes, then move on only if the error stays.

Start With A Clean Elevated Command Prompt

1. Open An Admin Terminal — Right-click Start, choose Windows Terminal (Admin) or Command Prompt (Admin).
2. Confirm Elevation — Run whoami /groups and check that the output includes the Administrators group.
3. Run A Read-Only Check — Run bcdedit /enum to test access without making edits.

If the message was “access is denied,” this step alone can clear it because BCDEdit needs elevated rights to open the store.

Use A Table To Match The Message To The Fix

Check For Two Common Desktop Triggers

• Restricted Shell — Some remote tools and locked-down sessions launch without full rights even if your account is admin. Open a fresh admin terminal from the Start menu.
• Wrong Boot Disk — On multi-boot machines, you may be looking at a different store than you think. If you have multiple drives, confirm which disk holds the active boot files.

If you only need to view entries, try bcdedit /enum. If that works, the store is readable and the issue is tied to the edit you attempted next.

To confirm you’re editing the store you think you are, run bcdedit /enum, then note the path shown for the loader and the device for the boot manager. If the device points to a different partition than your Windows drive, stop and map partitions first. That check can save you from editing a store that your PC never uses during startup on the reboot.

Bcdedit The Boot Configuration Data Store Could Not Be Opened In WinRE Or On A Non-booting PC

When the PC won’t boot, you usually run BCDEdit from WinRE. In that mode the drive letters you know from Windows can change, so the store you want may not be where you expect.

Get To WinRE Command Prompt

1. Open Recovery Options — Use a Windows install USB, or hold Shift while choosing Restart from the sign-in screen.
2. Open Command Prompt — Choose Troubleshoot, then Advanced options, then Command Prompt.
3. Stay On The Internal Drive — Your target is the Windows install on the PC, not the USB stick.

Identify The Windows Partition And The EFI System Partition

In WinRE, map letters first. This removes guesswork.

1. Open DiskPart — Run diskpart.
2. List Volumes — Run list volume. Look for a large NTFS volume with a Windows folder, and a small FAT32 volume labeled System or EFI.
3. Assign EFI A Letter — Select the EFI volume and run assign letter=S.
4. Exit DiskPart — Run exit.

Now test whether the store exists on the EFI partition. Run dir S:\EFI\Microsoft\Boot\. If you see BCD listed, the store is present and reachable by path in this session.

Point BCDEdit At The Store Explicitly

• Read The Store By Path — Run bcdedit /store S:\EFI\Microsoft\Boot\BCD /enum.
• Try The BIOS Path If Needed — On legacy BIOS installs, test dir S:\Boot\ and look for BCD, then run bcdedit /store S:\Boot\BCD /enum.

If you get “the system cannot find the file specified” even with /store, the store is missing at that path. That points to rebuilding boot files instead of editing them.

If you get “access is denied” in WinRE, the partition may be locked by BitLocker, or the volume you selected is not the EFI/System partition for the boot disk you are repairing.

Unlock BitLocker Before You Repair Boot Files

If your OS drive is protected, WinRE may see the volume yet block reads and writes. That can make bcdedit and bcdboot fail even when you picked the right partitions.

1. Check Lock Status — Run manage-bde -status and look for a locked volume.
2. Unlock The Volume — Run manage-bde -unlock C: -RecoveryPassword YOUR-48-DIGIT-KEY with the correct letter and recovery key.
3. Confirm Access — Run dir C:\Windows again and confirm files list normally.
4. Retry The Store Command — Rerun bcdedit /store S:\EFI\Microsoft\Boot\BCD /enum, then run BCDBoot if the store is missing or corrupted.

If you are not sure which letter is the real Windows partition, search for it by checking a few letters for \Windows. In WinRE, that letter can shift between boots, so it is worth confirming each session.

Rebuild Boot Files The Clean Way With BCDBoot

When the BCD store is missing or corrupted, rebuilding is often faster than trying to patch entries. Microsoft documents BCDBoot as the tool that copies boot files and sets up the system to start Windows.

Recreate The Store On UEFI Systems

These steps assume your Windows folder is on C: in WinRE and your EFI partition is mounted as S:. Adjust letters to match what you saw in DiskPart.

1. Confirm The Windows Folder — Run dir C:\Windows. If you don’t see it, try another letter until you find it.
2. Run BCDBoot — Run bcdboot C:\Windows /s S: /f UEFI.
3. Verify Boot Files — Run dir S:\EFI\Microsoft\Boot\ and confirm a BCD file exists.
4. Restart And Test — Close the prompt and restart the PC.

Recreate The Store On Legacy BIOS Systems

On BIOS/MBR installs, boot files are stored on the active system partition.

1. Find The System Volume — In DiskPart, look for System Reserved or the active system partition.
2. Assign A Letter — Assign it as S:.
3. Run BCDBoot — Run bcdboot C:\Windows /s S: /f BIOS.

After this, rerun bcdedit /store S:\EFI\Microsoft\Boot\BCD /enum to confirm the store opens. If your original problem text was “bcdedit the boot configuration data store could not be opened,” this rebuild step targets the root cause when the store is missing or damaged.

Common Traps That Trigger The Error

Most failed repairs come from one of these traps. Fix the trap, then rerun the command you wanted.

Drive Letters Changed In WinRE

In WinRE, Windows might be on D: instead of C:. If you run commands against the wrong letter, tools report missing files, even when the system is intact. Use DiskPart volume mapping each time you boot into WinRE.

Multiple Disks And The Wrong EFI Partition

On desktops with more than one drive, the system may boot from an EFI partition on a different disk than the Windows partition. Select each disk in DiskPart and find the EFI partition that pairs with the Windows disk you intend to boot.

Firmware Mode Mismatch

If firmware settings were changed, Windows boot files created for UEFI may not load under Legacy/CSM mode, and the reverse is true. Match the BCDBoot /f switch to the firmware mode you plan to use.

Safer Ways To Make Boot Changes After You Regain Access

Once BCDEdit opens the store again, you can make the change that brought you here, with less risk.

Back Up The Store Before Editing

1. Create A Backup Folder — Make a folder like C:\BCD-Backup.
2. Export The Store — Run bcdedit /export C:\BCD-Backup\bcd-backup.
3. Keep Notes — Save the exact command you run next, so you can reverse it if boot behavior changes.

Use Targeted BCDEdit Commands

When you do need BCDEdit, keep edits narrow and verify after each change.

• List Current Entries — Run bcdedit /enum and copy the identifier you plan to edit.
• Change One Setting — Run one bcdedit /set command, then re-enum to confirm it applied.
• Undo Cleanly — Use bcdedit /deletevalue to remove a single value when you are done.

When You Should Protect Data First

If your system still won’t boot after rebuilding boot files, stop making repeated changes. Repeated attempts can make it harder to track what altered the boot path, and they can add write activity to a drive that may already be failing.

Signs it’s time to focus on data safety:

• Disk Errors Keep Appearing — You see repeated read errors, loud clicking, or SMART alerts.
• BitLocker Key Is Missing — You can’t unlock the OS volume, so repairs can’t complete.
• Windows Folder Looks Incomplete — The Windows directory is present, yet core folders are missing or unreadable.

At that point, boot from a trusted USB boot drive, copy your files to another drive, then decide whether to run deeper repairs or reinstall Windows.

If you still see the exact text “bcdedit the boot configuration data store could not be opened” after you verified drive letters and ran BCDBoot against the right partitions, re-check that you selected the correct disk and firmware mode.

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