reagentc /enable not working: how to fix WinRE in Windows 11 and 10

Applies to: Windows 11 and Windows 10. All commands need an administrator Command Prompt or Terminal: right-click Start and choose Terminal (Admin) or Command Prompt (Admin).

Check the current WinRE status

Windows Recovery Environment (WinRE) is the blue recovery menu behind Startup Repair, Reset this PC and Advanced startup. reagentc is the tool that turns it on and off. Start by seeing what it thinks is set up:

reagentc /info

• Windows RE status: Enabled with a location such as \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE means WinRE already works; you don’t need to enable it.
• Windows RE status: Disabled with an empty location means it’s off. When WinRE is disabled, Windows normally keeps Winre.wim in C:\Windows\System32\Recovery so it can move it back to the recovery partition when you enable it.
• Note the exact error reagentc /enable gives you, then jump to the matching fix below.

Fix 1: “The Windows RE image was not found”

This means Winre.wim isn’t where reagentc expects it. The file is hidden and a system file, so check with:

dir /a C:\Windows\System32\Recovery

If Winre.wim is listed, point reagentc at it and enable again:

reagentc /setreimage /path C:\Windows\System32\Recovery
reagentc /enable

If the file is missing (it can get deleted by cleanup tools, disk cloning or a failed update), copy it from Windows installation media that matches your version and language:

1. Download the Windows 11 or Windows 10 ISO from Microsoft, then right-click it and choose Mount. Note its drive letter, for example E:.
2. Check whether the ISO has install.wim or install.esd in its sources folder. If it’s install.esd, convert it first; our install.esd guide shows how.
3. Create a folder and mount the image (index 1 is fine for this; use a higher index if you want your exact edition):

mkdir C:\mount
DISM /Mount-Image /ImageFile:E:\sources\install.wim /Index:1 /MountDir:C:\mount /ReadOnly
copy C:\mount\Windows\System32\Recovery\Winre.wim C:\Windows\System32\Recovery
DISM /Unmount-Image /MountDir:C:\mount /Discard

Then run reagentc /setreimage /path C:\Windows\System32\Recovery and reagentc /enable. Using a Winre.wim from a much older or newer build usually works, but one that matches your Windows version is best.

Fix 2: Reset ReAgent.xml

ReAgent.xml in C:\Windows\System32\Recovery stores where WinRE lives. After cloning a disk, changing partitions or a failed update it can point to a partition that no longer exists, and reagentc /enable fails with a vague error. Reset it:

reagentc /disable
ren C:\Windows\System32\Recovery\ReAgent.xml ReAgent.old
reagentc /enable

Windows creates a fresh ReAgent.xml when you enable WinRE. This only works if Winre.wim is in C:\Windows\System32\Recovery; if it isn’t, do Fix 1 first.

Fix 3: “Unable to update Boot Configuration Data”

WinRE is linked to Windows through the boot menu (BCD). If reagentc can’t write to it, check the boot entries:

bcdedit /enum all

• Under Windows Boot Loader with identifier {current}, look for recoverysequence and recoveryenabled. If recoveryenabled is No, run bcdedit /set {current} recoveryenabled yes, then try reagentc /enable again.
• On PCs that dual-boot, or where the disk was cloned, reagentc may be looking at the wrong boot store. Make sure you’re running it from the Windows installation you started.
• If BitLocker is on, suspend it before changing boot settings, and keep your recovery key handy; see BitLocker suspended for how suspending and resuming works.
• If bcdedit itself reports that the boot configuration data store can’t be opened, the boot files are damaged. Repair them from recovery media, or follow the steps in how to run SFC offline from recovery.

Back up the boot store before you change anything with bcdedit /export C:\bcdbackup.

Fix 4: Recovery partition too small or missing

Newer WinRE images are larger than older ones. If the recovery partition doesn’t have enough free space, enabling WinRE or installing a WinRE update fails; Windows Update shows this as error 0x80070643. Microsoft’s fix is to shrink the Windows partition slightly and recreate the recovery partition with more space, using diskpart, as described in KB5028997 (linked below).

1. Run reagentc /disable first, so Winre.wim is copied back to C:\Windows\System32\Recovery.
2. Follow Microsoft’s KB5028997 steps exactly: they shrink the OS partition by about 250 MB, delete the old recovery partition and create a new one with the right type and attributes for GPT or MBR disks.
3. Run reagentc /enable and check reagentc /info.

Be careful: deleting or creating partitions with the wrong number can wipe data. Back up first and read each command twice. If the recovery partition is between C: and another partition, or the disk layout looks unusual, a similar problem may be explained in we couldn’t update the system reserved partition.

Check WinRE works

After reagentc /info shows Enabled, test it: go to Settings > System > Recovery and select Restart now next to Advanced startup (on Windows 10, Settings > Update & Security > Recovery). The PC should restart into the blue Choose an option screen. Select Continue to go back to Windows.

Related guides

• install.esd: what it is and how to use, convert or delete it
• SFC offline: how to run sfc /scannow from recovery in Windows 11 and 10
• BitLocker suspended: what it means and how to resume protection
• We Couldn’t Update the System Reserved Partition: How to Fix It

Official sources: for more detail, see Microsoft’s own pages:

• Microsoft Learn: REAgentC command-line options
• Microsoft Support: KB5028997, manually resize your partition to install the WinRE update

Frequently asked questions

Is it safe to run reagentc /disable?

Yes. It turns WinRE off and copies Winre.wim back to C:\Windows\System32\Recovery. Your files and Windows aren’t affected, but recovery options won’t work until you enable it again.

Do I need WinRE enabled?

It’s strongly recommended. Without it you can’t use Reset this PC, Startup Repair or Advanced startup from Windows, and you’d need a USB recovery drive if Windows stops booting.

Why is Winre.wim missing?

Common causes are disk cleanup or “debloat” tools, cloning to a new drive without the recovery partition, deleting the recovery partition to free space, and failed WinRE updates.

Can I create the recovery partition without reinstalling Windows?

Yes. Shrink the Windows partition, create a new partition and set it up as Microsoft describes in KB5028997, then copy Winre.wim to C:\Windows\System32\Recovery and run reagentc /enable; Windows moves the image into the new partition.