Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

The boot configuration data store could not be opened. The volume for

- - - - -

  • Please log in to reply

#1
ziomario

ziomario

    New Member

  • Member
  • Pip
  • 6 posts

Hello to everyone.


At the beginning I'd installed windows 10 with the legacy BIOS-MBR boot mode,but since I needed a Windows 10 installation that was able to boot using the EFI partition style,I have converted the partition scheme from MBR to UEFI with a tool and after this operation I have reinstalled Windows 10 from an old backup. This backup comes from the old BIOS/MBR installation of Windows 10. When I tried to boot Windows,I realized that it was not able to do that (no error message.but blinking cursor). I have so realized that the EFI partition didn't exist. So,I have created a new FAT32 partition and I have repaired the EFI partition following this guide :


How to Restore Deleted EFI System Partition in Windows 10? | Windows OS Hub


it worked,but only partially. Infact,since I need to put the "TESTSIGNING ON",when I gave this command :
 

Bcdedit.exe -set TESTSIGNING ON

 

I've got this error :


The boot configuration data store could not be opened. The volume for a file has been externally altered so that the opened file is no longer valid.


I tried a lot of methods to fix it,but right now unsuccesfully. Can someone help me ? thanks.


  • 0

Advertisements


#2
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,375 posts

You can try the command from Windows Recovery Environment you can also rebuild new BCD store by executing Bootrec  /RebuildBcd command.


  • 0

#3
ziomario

ziomario

    New Member

  • Topic Starter
  • Member
  • Pip
  • 6 posts

As u can see on the pictures attached below,the reinstallation of the EFI boot files worked great and now I'm using windows,but I still get the same error :

 

https://drive.google...vvD?usp=sharing

 

(keep in consideration that windows is on drive E: and the EFI partition on drive Z). I suspect that I should make some modification on the BCD store after having rebuilded the BCD with Windows 10 running.


Edited by ziomario, 19 September 2020 - 12:30 PM.

  • 0

#4
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,375 posts
If you rebuild BCD store it should disable driver signature enforcement option.

https://windowsrepor...ent-windows-10/
  • 0

#5
ziomario

ziomario

    New Member

  • Topic Starter
  • Member
  • Pip
  • 6 posts

so ? what should I do ? I need to put the TESTSIGNING ON.


Edited by ziomario, 19 September 2020 - 04:05 PM.

  • 0

#6
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,375 posts

No you don't need to enable driver signature enforcement option.


Edited by FreeBooter, 19 September 2020 - 04:22 PM.

  • 0

#7
ziomario

ziomario

    New Member

  • Topic Starter
  • Member
  • Pip
  • 6 posts

yes,I need it,because I need to use an unsigned (signed by me) driver. My unsigned driver gives to me this error :

 

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)

 

so I need to enable it.


Edited by ziomario, 20 September 2020 - 04:47 AM.

  • 0

#8
ziomario

ziomario

    New Member

  • Topic Starter
  • Member
  • Pip
  • 6 posts

I have also tried to do that going on the group policy changing this policy setting :
 
User Configuration ->Administrative Templates -> System -> Driver Installation -> Code signing for drivers

 

and setting it to "Enable / Ignore" :

 

but it didn't work. Infact it says that Windows 10 is not supported...


Edited by ziomario, 20 September 2020 - 05:03 AM.

  • 0

#9
FreeBooter

FreeBooter

    Member 1K

  • Member
  • PipPipPipPip
  • 1,375 posts
Once you are on the command prompt screen, you need to type or copy/paste the following command. After that, hit Enter after each one:
 
 
bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS

bcdedit -set TESTSIGNING ON
 


If the above command doesn’t work or fails to remove the error code 52, then you can try the below code and instructions.
 
 
bcdedit /deletevalue loadoptions

bcdedit -set TESTSIGNING OFF

Since the BCD store exists and lists a Windows installation, you'll first have to "remove" it manually and then try to rebuild it again.

At the Command Prompt, type below command as shown and then press Enter:

C:
At the Command Prompt, type below command as shown and then press Enter:

bcdedit /export C:\bcdbackup
The bcdedit command is used here to export the BCD store as a file: bcdbackup. There's no need to specify a file extension.

The command should return the following on screen:
The operation completed successfully.

Meaning the BCD export worked as expected.


At this point, you need to adjust several file attributes for the BCD store so you can manipulate it. At the prompt, execute the attrib commands exactly like this:

attrib c:\boot\bcd -h -r -s
What you just did with the attrib command was remove the hidden, read-only, and system attributes from the file bcd. Those attributes restricted the actions you could take on the file. Now that they're gone, you can manipulate the file more freely - specifically, rename it.

To rename the BCD store, execute the ren command as shown:

ren C:\boot\bcd   bcd.old
Now that the BCD store is renamed, you should now be able to successfully rebuild it.

Try rebuilding the BCD again by executing the following, followed by Enter:

bootrec /scanos
bootrec /rebuildbcd
Restart your computer after rebuilding the BCD store.
  • 0

#10
ziomario

ziomario

    New Member

  • Topic Starter
  • Member
  • Pip
  • 6 posts

I've fixed the error making the ISO image of my windows installation and then I have reinstalled it using a tool called "WintoHDD". Without this tool it won't work. Infact,I tried several times to reinstall Windows 10 from the USB stick in a EFI mode with an EFI partition style scheme,but it seems not able to create the EFI partition. In addition,it writes some boot values inside the EFI partition of the NVME disk (that I can't disable from the BIOS). I put it as secondary boot disk but it didn't work anyway. Infact windows 10 can't boot if it is installed as a sata disk and if it is not the only disk on the PC or if it is not on the first place. I'm not sure what's the true.


Edited by ziomario, 21 September 2020 - 01:20 PM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP