BCD: File is not system store error when upgrading from Win 10 v1703

T

tadc

Contributor
Joined
Jan 24, 2020
Posts
43
Hi all - first off, thanks in advance for taking a look at my thread.

I've been struggling with this issue off and on for some time but now that 1703 is out of support I finally got motivated to solve it.

In short, the update from 1703 always fails. When I run manually I get the (coincidentally with another current thread: "We cant tell if your PC has enough space to continue installing win10" message.

In setuperr I see the following:

2020-01-24 15:36:27, Error IBSLIB BCD: File is not system store. File: \Device\HarddiskVolume2\EFI\Microsoft\Boot\BCD Status: 0

and potentially associated warnings in setupact:

2020-01-24 15:36:27, Warning [SetupHost.exe] winreGetWinReGuid open store failed: 0xc0000098
2020-01-24 15:36:28, Warning SP SPGetCurrentOSGuid: BCD Open failed. Error: 0x000003EE

Disk manager snapshot:
1579912031337.png

I've attached the setup logs. Any pointers in the right direction would be much appreciated.

Thanks!
 

Attachments

Hello and welcome!

You will need a bootable Windows disc or recovery flash drive to boot from to do this.
How to create a recovery flash drive: https://support.microsoft.com/en-us/...recovery-drive

After you create the recovery drive, boot from it by using the advanced startup options and choosing boot from device (or using the UEFI interface, whichever is simpler :) ).
Here's the instructions that other users have had success with:



Alright, apparently the issue is with the BCD (Boot Configuration Data). A few users reported that rebuilding it solved that issue.

https://answers.microsoft.com/en-us/...4-9ae12cfd89a2 - "Most Helpful Reply" from Cifad

If you cannot read the commands properly, here goes (to be entered in the command prompt from the Recovery Environment):

diskpart - Opens the Disk Partitionning tool
select disk 0 - Will select your first hard drive (the one with the Windows partition on it)
list volume - Note the number of the partition that have no drive letter assigned to it, is of 260MB of size and have "FAT32" listed under the "FS" column
select volume X - X will be the number of your partition with a size of 260MB, the EFI System Partition one that you identified in the last command
assign letter=Z: - It'll assign the Z: letter to the EFI System Partition
exit - To exit the diskpart utility

Now you'll be back in the command prompt, enter the following commands:

cd /d Z:\EFI\Microsoft\Boot - Goes to the "Boot" directory in the Z: partition
attrib Z:\EFI\Microsoft\Boot\BCD -h -r -s - Removes the hidden, read-only and system attributes from the BCD folder
ren Z:\EFI\Microsoft\Boot\BCD BCD.old - Renamed the BCD folder to BCD.old
bootrec /rebuildbcd - This command will rebuild the BCD.

When it asks you Add the installation to boot list?, press on y followed by Enter and if it succeed, you'll have a The operation completed successfully message. Once you're done, close the command prompt, restart your computer and try to upgrade again.



Make sure you have a complete backup of anything important on your computer BEFORE attempting any of these steps.
 
Thanks much for the reply.

I tried the bootrec /rebuildbcd and it succeeded, but I still get "we can't tell if you have enough space" error. However, the setuperr log message has changed:

Code: 
2020-01-26 18:46:24, Error                 IBSLIB BCD: Failed to enumerate boot entries. Status: c0000001
2020-01-26 18:46:24, Error                 IBSLIB BCD: BiBuildIdentifierList failed c0000001
2020-01-26 18:46:24, Error                 IBSLIB BCD: BiBindEfiNamespaceObjects failed c0000001
2020-01-26 18:46:24, Error                 IBSLIB BCD: Failed to bind with firmware. Flags: 0x0 Status: c0000001

Also of note, when I try to access the BCD store it errors, but when I specify the store directly (which IINM should be functionality identical) it works:

Code: 
C:\Windows\system32>bcdedit /enum all
The boot configuration data store could not be opened.
A device attached to the system is not functioning.

Code: 
N:\EFI\Microsoft\Boot>bcdedit /store n:\efi\Microsoft\Boot\bcd /enum all

Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {bootmgr}
                        {5cee3f75-4001-11ea-b274-975ec362cfbd}
                        {5cee3f78-4001-11ea-b274-975ec362cfbd}
                        {5cee3f76-4001-11ea-b274-975ec362cfbd}
                        {5cee3f79-4001-11ea-b274-975ec362cfbd}
                        {5cee3f77-4001-11ea-b274-975ec362cfbd}
timeout                 0

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=N:
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
displayorder            {5cee3f7a-4001-11ea-b274-975ec362cfbd}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {5cee3f75-4001-11ea-b274-975ec362cfbd}
description             USB Floppy/CD

Firmware Application (101fffff)
-------------------------------
identifier              {5cee3f76-4001-11ea-b274-975ec362cfbd}
description             USB Floppy/CD

Firmware Application (101fffff)
-------------------------------
identifier              {5cee3f77-4001-11ea-b274-975ec362cfbd}
description             IBA GE Slot 00C8 v1381

Firmware Application (101fffff)
-------------------------------
identifier              {5cee3f78-4001-11ea-b274-975ec362cfbd}
device                  partition=G:
description             Lexar USB Flash Drive 1100

Firmware Application (101fffff)
-------------------------------
identifier              {5cee3f79-4001-11ea-b274-975ec362cfbd}
description             Hard Drive

Windows Boot Loader
-------------------
identifier              {5cee3f7a-4001-11ea-b274-975ec362cfbd}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10 Pro
locale                  en-US
osdevice                partition=C:
systemroot              \Windows
resumeobject            {7fe39ab4-4001-11ea-9a43-806e6f6e6963}
bootmenupolicy          Standard

Resume from Hibernate
---------------------
identifier              {7fe39ab4-4001-11ea-9a43-806e6f6e6963}
device                  partition=C:
path                    \Windows\system32\winresume.efi
description             Windows 10 Pro
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=N:
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-US

I wonder if I might not need to edit the firmware BCD entries?

Thanks again for any help or advice.
 

Attachments

softwaremaniac said:
Let's try this:

How to Rebuild BCD File and Master Boot Record (MBR) in Windows 10? | Windows OS Hub
Click to expand...
Thanks, again for your help and replies.

I did try that link in the past and got a similar issue when I tried to open the BCDStore.

*However*, I have good news, I've solved my issue!

For posterity - the problem was, as suspected, with the NVRam/firmware/"BIOS".

I started to go down the path of resetting the firmware, but as I explored that option I saw that I had a VERY old (like 7 years) version, so I figured I'd update that before resetting. After flashing, BCDedit works again and the 1903 update successfully applied overnight!

So not sure if the flash also un-corrupted the Boot table in NVRAM, if there was some issue with the old firmware version, or what, but flashing solved it.

Incidentally this was for an HP/Compaq 6300 Pro.

Thanks again for your help!
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top