5
I am using a machine that dual boots windows 8.1 and OSX using the chimera boot manager. The disk layout is MBR so there is no EFI partition, the boot files can be found on C:\boot
. When I try to use bcdedit
in the command prompt I get the following error:
C:\Windows\system32>bcdedit /enum
The boot configuration data store could not be opened.
The system cannot find the file specified.
However if I manually specify the bcd location (which is at c:\boot\bcd
) everything works fine, I can edit the store, and the changes gets picked up the next restart just as expected:
C:\Windows\system32>bcdedit /store c:/boot/bcd /enum
Windows Boot Manager
--------------------
(...)
So it seems bcdedit
doesn't know where the system store is. Is there a way to fix this? It might also be helpful if I'd known where bcdedit tries to find the system store in the first place.
You can follow @ArtHare instructions, but it converts your dual boot machine to a windows only machine. If you want to keep it dual boot, it's normal to not find your BCD store in default location, because it's default location is the active partition, which is now hosting Chimera bootloader. – NetwOrchestration – 2016-12-26T18:20:16.477
Note: this is an almost 3 year old question. Since then I migrated over to an EFI based solution, which properly solves all of the issues. – SztupY – 2016-12-27T22:11:54.357