Unsolved
1 Rookie
•
13 Posts
0
81
December 22nd, 2025 22:53
Precision 3571 WinRE issue – reagentc error b7
Hello Dell Community,
I’m looking for guidance on restoring the Windows Recovery Environment (WinRE) on a Dell Precision 3571 after a disk layout change.
System information
Model: Dell Precision 3571
OS: Windows 11 (Build 10.0.26200.7462)
Boot mode: UEFI
Disk: GPT
System boots and runs normally
Background
I was extending the C: drive, which required deleting the existing recovery partition.
After extending C:, I manually recreated a recovery partition and attempted to re-enable WinRE.
Since then, WinRE cannot be enabled again.
Current behavior
Running:
reagentc /enable
Always fails with:
REAGENTC.EXE: Operation failed: b7
And:
reagentc /info
Shows:
Windows RE status: DisabledBCD identifier: 00000000-0000-0000-0000-000000000000
No WinRE BCD entry is created.
What I have already verified
Windows boots and functions normally
Recovery partition exists and is healthy
Recovery partition details:
GPT type:
de94bba4-06d1-4d40-a16a-bfd50179d6acGPT attributes:
0x8000000000000001Hidden = Yes, Required = Yes
NTFS, ~1 GB in size
Winre.wimexists and is readable at:\Recovery\WindowsRE\Winre.wimdism /get-wiminfoconfirms the image is validreagentc /setreimagesucceedsRecovery partition has no drive letter
ReAgent.xmlwas resetBCD was rebuilt using:
bcdboot C:\Windows /f UEFI
Despite all of this, reagentc /enable continues to fail with error b7, and WinRE remains disabled.
Question
Is this a Dell OEM–specific behavior on Precision systems?
Specifically:
Does the Precision 3571 require Dell OEM recovery components or BCD entries that
reagentccannot recreate?Is there a supported way to restore WinRE without using the Dell OS Recovery USB?
Or is the expected and supported approach to rely on external Dell recovery media once the original OEM recovery environment has been removed?
I want to ensure I’m following Dell-supported recovery practices for this system and not attempting something that isn’t intended to be rebuilt manually.
Any guidance from Dell engineers or users who have encountered this on Precision or Latitude systems would be greatly appreciated.
Thank you.
0 events found

