bcdedit: The boot configuration data store could not be opened

Boot the computer using the Windows 10 installation media.

My machine is already booted, luckily I didn't reboot it since breaking the BCD store. Do I still have to boot off the Win10 install media disk?

- - - Updated - - -

​

The first thing that I would do is physically disconnect all the drives other than the drive containing the Windows partition you want to actually boot into. That will make things MUCH easier. You'll also need a standard Windows 10 installation media USB flash drive, such as is created with the Media Creation Tool.

After you do that, boot the computer from the Windows 10 USB flash drive. Press Shift + F10 to open a command prompt (you might have to press Shift + Fn + F10). Then run:
diskpart
select disk 0
list part
list vol


Post the output here.

since I won't be able to use the Win10 screenshot tool in the Windows 10 recovery mode, I will have to take a pic using another device and then uploading a pic.

dictum said:

since I won't be able to use the Win10 screenshot tool in the Windows 10 recovery mode, I will have to take a pic using another device and then uploading a pic.

Yep.

One second.

- - - Updated - - -

I figured out the root cause of this, it was the SATA III disk that had the primary boot OS cloned onto it.

it screwed things up and bcdedit output disappeared, not sure why. Some conflict between disks?

Once I removed the SATA III HDD, the problem went away.

The MSI laptop has 4 drives, 2 are PCIE SSD, and the rest are SATAIII SSDs. It seems that the SATAIII ones cannot be bootable, or else cannot be bootable in conjunction with the other disks being bootable.

- - - Updated - - -

I did boot off the Windows install media, via flash and did diskpart:

100%x​

- - - Updated - - -

100%x​

- - - Updated - - -

100%x​

- - - Updated - - -

So the issue is resolved though I would still like to know what was the root cause of it.

dictum said:

One second.

- - - Updated - - -

I figured out the root cause of this, it was the SATA III disk that had the primary boot OS cloned onto it.

it screwed things up and bcdedit output disappeared, not sure why. Some conflict between disks?

Once I removed the SATA III HDD, the problem went away.

The MSI laptop has 4 drives, 2 are PCIE SSD, and the rest are SATAIII SSDs. It seems that the SATAIII ones cannot be bootable, or else cannot be bootable in conjunction with the other disks being bootable.

- - - Updated - - -

I did boot off the Windows install media, via flash and did diskpart:

100%x​

- - - Updated - - -

100%x​

- - - Updated - - -

100%x​

- - - Updated - - -

So the issue is resolved though I would still like to know what was the root cause of it.

Having active partitions on secondary drives can confuse the boot process. You can change those partitions to inactive (e.g. using MiniTool Partition Wizard) to avoid such problems. Obviously don't fiddle with the partitions on the system drive.

Steve C said:

Having active partitions on secondary drives can confuse the boot process. You can change those partitions to inactive (e.g. using MiniTool Partition Wizard) to avoid such problems. Obviously don't fiddle with the partitions on the system drive.

Impossible with a UEFI computer with GPT partitioned drives.

x509 said:

What if you have a GPT-based boot drive?

What if you have protective Master Boot Record.

Both of these partitions have boot information, can I delete the D: ?

Having difficulty booting the system with having to go to BIOS and choose the drive.