Fix: Boot Configuration Data Store Could Not Be Opened (2024)

Several Windows users have reported getting the ‘Boot configuration data store could not be opened’ error when trying to run a bcdedit command inside Command Prompt. Most of the time, this error is accompanied by a sub-error like ‘Access is denied’ or ‘The requested system device cannot be found’. The issue is not exclusive to a certain Windows version since it’s confirmed to occur on Windows 7, Windows 8 / 8.1 and Windows 10.

What is BCDEdit?

BCDEdit is a command-line tool used for managing the Boot Configuration Data (BCD). It contains a store that is used to describe boot applications and boot application settings. When it comes to its functionality, BCDEdit can be used for a variety of purposes, including adding boot menu potions, modifying existing stores and creating new ones from scratch.

What is causing the ‘Boot configuration data store could not be opened’error?

We investigated this particular issue by looking at various user reports and the repair strategies that affected users have used in order to get to the bottom of this problem. As it turns out, there are a couple of common scenarios in which this particular issue will appear:

If you’re currently struggling to resolve the ‘Boot configuration data store could not be opened’ error, this article will allow you to fix the problem by providing you with a couple of troubleshooting guides that other users in a similar situation have successfully used.

For the best results, please follow the methods in the order that they are presented, since they are ordered by efficiency and severity.

Method 1: Opening Command Prompt as administrator

In most case, this particular issue occurs because of a privilege issue. Most likely, the BCDEdit is forced to perform an operation that requires elevated privileges (admin access). This is even more likely if the sub-message associated with ‘Boot configuration data store could not be opened’ error is ‘Access is denied’.

Several users encountering this exact error message have managed to resolve the issue and complete the BCDEdit operation by opening Command Prompt with administrative privileges. Here’s how to do this:

1. Press Windows key + R to open up a Run dialog box.
2. Next, type “cmd” and press Ctrl + Shift + Enter to open up an elevated Command Prompt.

   

3. When you’re prompted by the UAC (User Account Control), click Yes to grant administrative privileges.
4. Once you’re inside the elevated Command Prompt, perform the same operation that was previously triggering the ‘Boot configuration data store could not be opened’error and see it has been resolved.

If you’re still encountering the same error message, move down to the next method below.

Method 2: Changing the Boot Mode

As a few affected users have pointed out, when booting the machine, you need to make sure that you are booting from the same time of partition that the hard drive was created with in order for BCDEdit to work as intended. The quickest way to do this is to change the BIOS mode. This procedure is done from the BIOS settings but will differ from computer to computer according to the motherboard manufacturer and the BIOS version that it features.

Here’s a generic guide that should help you get there regardless of your motherboard manufacturer:

1. Start your computer and press Setup key (boot key) during the initial startup sequence. Typically, the setup key id displayed on the initial screen, but just in case you don’t see it, it’s either any of the F keys (F2, F4, F6, F8 etc.) the Del key (for Dell computers) or the Esc key.
   

   

   Note: You can also search online for the specific Setup key of your computer.
2. Once you arrive into the BIOS settings, look for a Boot tab and change the Boot Mode to the type in which the partition was originally created. In this case, it’s Legacy BIOS.

   

3. Once the boot mode has been changed, save the current configuration and restart your computer.
4. Attempt to use the BCDEdit command again and see if you’re still getting the‘Boot configuration data store could not be opened’error.