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 No 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 No comments

72 additional answers

Sort by: Most helpful
  1. Ramesh 181.6K Reputation points Volunteer Moderator
    2023-04-20T06:01:21+00:00

    I beg to differ. I repeat, the specific command Regaentc /setreimage does NOT touch the BCD. You're wrong.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-04-20T05:56:53+00:00

    Reagentc does touch the BCD, I hope I am clear. It does tell the BCD store where the Winre.wim is, that is the purpose for the commands.

    And don't ever use the "I hope I am clear" phrase again, especially when you are wrong.

    C:\Windows\System32>reagentc /setreimage /?

    Sets the location of the custom Windows Recovery Environment (Windows RE) image.

    REAGENTC.EXE /setreimage /path <dir_name> [/target <dir_name>] [/logpath <file_path>]

    /path <dir_name> - Specifies the directory that contains the custom

                          Windows RE image (winre.wim). 
    

    /target <dir_name> - Specifies the Windows installation. If this argument

                          is not specified, the running operating system is 
    
                          used. 
    

    /logpath <file_path> - Specifies the path of log file. If this argument is

                          not specified, the default path is Windows\Logs\ 
    
                          Reagent\Reagent.log. 
    

    Example:

    REAGENTC.EXE /setreimage /path r:\Recovery\WindowsRE /logpath C:\Temp\Reagent.log 
    
    REAGENTC.EXE /setreimage /path r:\Recovery\WindowsRE /target C:\Windows
    

    Was this answer helpful?

    0 comments No comments
  3. Ramesh 181.6K Reputation points Volunteer Moderator
    2023-04-20T05:27:20+00:00

    And FYI, Regaentc /setreimage doesn't even touch the BCD.

    It's the final command, ReAgentc /enable that actually writes to the BCD.

    I hope I'm clear.

    Was this answer helpful?

    0 comments No comments
  4. Ramesh 181.6K Reputation points Volunteer Moderator
    2023-04-20T05:20:25+00:00

    The BCD entry wasn't there in the first place. Please check his previous thread where he had just formatted the EFI partition and rebuilt it.

    Moreover, reverting it to R:\ is an easy task, by rerunning /setreimage. The command updates the ReAgent.xml. So, that's no way the issue here. The problem here is the BCD is inaccessible [0xc0000034 is STATUS_OBJECT_NAME_NOT_FOUND].

    Was this answer helpful?

    0 comments No comments