REAGENTC.EXE: Unable to update Boot Configuration Data.

Anonymous
2023-04-19T12:50:25+00:00

I am unable to enable WindowsRE?

Windows for home | Windows 11 | Recovery and backup

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2023-04-21T04:29:52+00:00

(1) You've got two System partitions each with its own BCD. C partition is doubling as a System partition, & EFI is a System partition...

Image

That is likely what is confusing ReagentC. It needs to find the BCD in order to enable the Recovery partition. We need to tell Windows that EFI is to be used -- not C. Let's try this...

DiskPart<<<Enter DiskPart

List  Vol<<<List the volumes & letters

Select  Vol  7           <<<Select EFI -- I guess it's still Volume 7

Assign  Letter=S     <<<Give it letter S -- unless List Vol shows it's already there

Exit<<<Exit Diskpart

BCDBoot  C:\Windows  /s  S:  /f  UEFI <<< **** Rebuild the BCD in EFI & all other boot files.

A reboot will be necessary to inform the rest of Windows of the change.

(a) I'm unsure that actually tells Windows to use EFI.

(b) I'm unsure whether that will also remove the System attribute from C.

(c) I'm unsure exactly what would remove it.

(d) So, maybe try this before the reboot...

REN C:\EFI EFI_unwanted <<<Rename the folder

..........................................................................

Then -- if it turns out it can't reboot -- you'll have to rename it back in the recovery environment, thus...

(a) At the Choose an Option screen, click "Troubleshoot > Advanced Options > Command Prompt".

(b) Enter the following commands...

DiskPart

List Vol

Exit

The Windows partition may have a different letter here. Use it instead of C in the following command...

REN C:\EFI_unwanted EFI <<<Rename it back

......................................................................

(2) After the reboot (presuming it did)...

Does BCDEdit /Enum {fwbootmgr} now show {bootmgr} on top?

Does BCDEdit /Enum {Bootmgr} name either HarddiskVolume9 or S: as the Device?

If so, try again...

ReagentC /Disable <<<Moves WinRE.wim to staging area

ReagentC /Enable <<<Moves it to the Recovery partition

ReagentC /Info <<<Show whether it is enabled

If it isn't enabled, let's see C:\Windows\Logs\ReAgent\Reagent.log. Just copy/paste the output of those three commands from the bottom of the log.

(3) A volume is a partition that has a file system on it. The Volume numbers enumerated by DiskPart are not the same as the HarddiskVolume numbers enumerated in the BCD. The BCD counts all partitions (with or without a file system) starting from Disk 0. Disk Management won't show them all. DiskPart will show them, this way...

DiskPart <<<Enter DiskPart

List Disk <<<List your 8 disks

Select Disk 0 <<<Focus on Disk 0

List Part <<<List its partitions

Select Disk 1

List Part

=== Continue with Disks 2 through 7 ===

Exit <<<Leave DiskPart

Looking at your prior listings, I now think the 8th partition down will be C. And EFI will be partition 9. Disks 0-5 will have 1 partition each, then Disk 6 shows...

Image

So -- HarddiskVolume8 is the Windows partition. (EFI is HarddiskVolume9). Yep, the BCD that is on C (shown with /Store) shows the letter...

Image

The one that is on EFI (S:) shows...

Image

We want the one on EFI (S:) to be the only one. Windows gets confused when there is more than one System partition.

Was this answer helpful?

10+ people found this answer helpful.
0 comments

72 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-04-20T22:41:51+00:00

    (1) No, the zero GUID /Info reported means none was found in the BCD for the Recovery partition.

    (2) The log isn't at gofile that I can find. And I'm leery of connecting to a strange cloud storage other than OneDrive anyhow. Just copy/paste C:\Windows\Logs\ReAgent\Reagent.log into the Search bar. Copy out the three command's output from the bottom, then paste it here.

    (3) That BCD /Set command moved {bootmgr} to the top of Displayorder where it does belong. I'm puzzled that it didn't remain there after a reboot.

    (a) Are you sure it was a reboot -- not a shutdown, then boot? Those are normally different.

    (b) I'm thinking (not really sure) you've got two BCDs. One is on HarddiskVolume8 which the {bootmgr} would use. That should be the EFI partition. The other is on C: which the direct boot to C: uses...

    Image

    I think HarddiskVolume8 is indeed the EFI partition, otherwise {bootmgr} would also say C: is the device. Let's put a letter on EFI to access its BCD directly. EFI is the FAT32 partition...

    Image

    DiskPart <<<Enter DiskPart

    List Vol <<<Show the volume numbers & letters

    Select Vol 7 <<<Focus on EFI -- IF it's still volume 7

    Assign Letter=S <<<Give it letter S

    Exit <<<Leave DiskPart

    DIR C:\EFI\Microsoft\Boot\BCD /a <<<Is there one on C?

    DIR S:\EFI\Microsoft\Boot\BCD /a <<<Is there one on S?

    BCDEdit /Store C:\EFI\Microsoft\Boot\BCD /Enum {fwbootmgr} <<Show fwbootmgr

    BCDEdit /Store C:\EFI\Microsoft\Boot\BCD <<<Show the boot manager & loader

    BCDEdit /Store S:\EFI\Microsoft\Boot\BCD /Enum {fwbootmgr}

    BCDEdit /Store S:\EFI\Microsoft\Boot\BCD

    Let's do that investigation, then decide how to fix it.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-04-20T10:54:51+00:00

    Image

    The above is before a reboot with those commands.
    Below is after a reboot
    Image

    Image Here is the log
    https://gofile.io/d/h0wBxV
    Edit- I feel like the identifier for the BCD shouldnt be all zeros? Is that a sign of something being broken?>

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-04-20T06:36:40+00:00

    (1) Now that you've got a new BCD, show us: BCDEdit /Enum {fwbootmgr}

    That is a window to the BIOS Boot Order screen. The earlier BCD showed BIOS was set to boot directly to C instead of to the Windows Boot Manager (bootmgr). A UEFI installation should always boot to the boot manager.

    Image

    Image

    If it still looks like that, move {bootmgr} to the top of the Displayorder this way...

    BCDEdit /Set {fwbootmgr} Displayorder {Bootmgr} /Addfirst

    BCDEdit /Enum {fwbootmgr} <<<Confirm it has moved to the top

    Reboot to put it into effect. It will automatically change in BIOS. Then show us the full BCD...

    BCDEdit /Enum All

    (2) Now try...

    ReagentC /Disable <<<Moves WinRE.wim to staging area

    ReagentC /Enable <<<Moves it to the Recovery partition

    ReagentC /Info <<<Show whether it is enabled

    If it isn't enabled, let's see C:\Windows\Logs\ReAgent\Reagent.log. Just copy/paste the output of those three commands from the bottom of the log.

    Was this answer helpful?

    0 comments
  4. Ramesh 181.6K Reputation points Volunteer Moderator
    2023-04-20T06:08:38+00:00

    Logs from 18th. that is before this thread was created:

    ***********

    2023-04-18 17:12:18, Info [ReAgentc.exe] ------------------------------------------------------

    2023-04-18 17:12:18, Info [ReAgentc.exe] -----Executing command line: Reagentc /info-----

    2023-04-18 17:12:18, Info [ReAgentc.exe] ------------------------------------------------------

    2023-04-18 17:12:18, Info [ReAgentc.exe] Enter WinReGetConfig

    2023-04-18 17:12:18, Info [ReAgentc.exe] Parameters: configWinDir: NULL

    2023-04-18 17:12:18, Info [ReAgentc.exe] WinRE config file path: C:\windows\system32\Recovery\ReAgent.xml

    2023-04-18 17:12:18, Info [ReAgentc.exe] Update enhanced config info is enabled.

    2023-04-18 17:12:18, Warning [ReAgentc.exe] winreGetWinReGuid open store failed: 0xc000000f

    2023-04-18 17:12:18, Info [ReAgentc.exe] winreGetWinReGuid returning 0X2

    2023-04-18 17:12:18, Info [ReAgentc.exe] ReAgentConfig::ReadBcdAndUpdateEnhancedConfigInfo WinRE disabled, WinRE Guid could not be determined (0x2)

    2023-04-18 17:12:18, Error [ReAgentc.exe] IOCTL_STORAGE_QUERY_PROPERTY failed: 0x1

    2023-04-18 17:12:18, Info [ReAgentc.exe] System is WimBoot: FALSE

    2023-04-18 17:12:18, Info [ReAgentc.exe] WinRE image validated

    2023-04-18 17:12:18, Info [ReAgentc.exe] Exit WinReGetConfig return value: 1, last error: 0x2

    **********

    2023-04-18 17:12:31, Info [ReAgentc.exe] --Install on target OS step 2: detect and fix if there is any issue for winre settings

    2023-04-18 17:12:31, Info [ReAgentc.exe] DetectAndFixWinReIssues (WinRE)WinRE is already installed, setting BCD entry (winre location \?\GLOBALROOT\device\harddisk6\partition4\Recovery\WindowsRE)

    2023-04-18 17:12:31, Warning [ReAgentc.exe] winreGetWinReGuid open store failed: 0xc000000f

    2023-04-18 17:12:31, Info [ReAgentc.exe] winreGetWinReGuid returning 0X2

    2023-04-18 17:12:31, Info [ReAgentc.exe] DetectAndFixWinReIssues Failed to get WinRE GUID.

    2023-04-18 17:12:31, Info [ReAgentc.exe] DetectAndFixWinReIssues Will fix the BCD entry.

    2023-04-18 17:12:31, Warning [ReAgentc.exe] winreSetRecoverySequence open store failed: c000000f

    *********

    That's proof that the BCD store had some issues. 0xc000000f = STATUS_NO_SUCH_FILE. It's inaccessible for some reason.

    Was this answer helpful?

    0 comments