Windows Recovery Environment missing after update

You boot your Windows 10 or 11 machine, hit F11 at the logo to get into recovery, and nothing happens. Or you try Advanced Startup from Settings, and it throws an error or just reboots you right back to the desktop. That's the Windows Recovery Environment (WinRE) missing in action.

I see this most often after a feature update — like the jump from 22H2 to 23H2 — or after running Disk Cleanup and telling it to delete "Windows Update Cleanup" files. The update process sometimes shrinks or corrupts the recovery partition. Or the boot configuration data (BCD) entry for WinRE gets erased. Happened to a client last month who ran Disk Cleanup on a lark and couldn't get into Safe Mode the next day.

What's actually broken?

WinRE lives in a separate partition on your drive — usually a small 500MB or 1GB partition set aside by Windows during installation. The bootloader points to a file called C:\Windows\System32\WinRE\Winre.wim, but that file is actually stored on that hidden partition. Two things go wrong:

1. The partition itself gets its drive letter changed or gets wiped.
2. The BCD entry that tells the bootloader where to find WinRE gets deleted or points to the wrong spot.

Windows uses a tool called reagentc to manage all this. If you run reagentc /info in an admin command prompt and get "Windows RE status: Disabled" or "Boot Configuration Data (BCD) store is missing", you've confirmed the issue.

How to fix it — step by step

Grab a Windows 10 or 11 installation USB (same version as your OS). Boot from it. On the first screen, click Repair your computer in the bottom left corner. Then go to Troubleshoot > Command Prompt. You'll be in the Windows PE environment, which is basically WinRE itself.

Step 1: Identify your partitions

diskpart
list disk
select disk 0
list partition

Look for the partition labeled "Recovery" or one that's about 500MB-1GB and doesn't have a drive letter. Note the partition number.

Step 2: Assign a drive letter to the recovery partition

select partition 4  (replace with your recovery partition number)
assign letter=R
exit

Now the recovery partition is accessible as R:. Don't close the command prompt yet.

Step 3: Check if the Winre.wim file exists

dir R:\Recovery\WindowsRE

If you see Winre.wim in there, you're in luck — the file is intact. If the folder is empty or missing, you'll need to copy the file from your Windows installation media.

Step 4: Copy Winre.wim if missing

md R:\Recovery\WindowsRE
xcopy C:\Windows\System32\Recovery\WindowsRE\Winre.wim R:\Recovery\WindowsRE\Winre.wim /h

Note: In WinPE, your C: drive might be D: or E: depending on how Windows assigned letters. Run notepad then go to File > Open to browse and find the actual Windows drive. Usually it's D: in the WinPE environment.

Step 5: Re-register WinRE

reagentc /disable
reagentc /setreimage /path R:\Recovery\WindowsRE
reagentc /enable
reagentc /info

You should see "Windows RE status: Enabled" and the path pointing to your recovery partition. If you get an error about the BCD, run this next.

Step 6: Fix the BCD entry manually

bcdedit /enum all

Look for an entry with "identifier {current}" and another with "identifier {ramdiskoptions}". If the ramdiskoptions entry points to a nonexistent file, delete and recreate it:

bcdedit /delete {ramdiskoptions} /f
bcdedit /create {ramdiskoptions} /d "Ramdisk options"
bcdedit /set {ramdiskoptions} ramdisksdidevice partition=R:
bcdedit /set {ramdiskoptions} ramdisksdipath \Recovery\WindowsRE\boot.sdi

Then create a new WinRE entry:

bcdedit /create /application osloader

That command returns a GUID. Let's say it's {12345678-...}. Use it in the next commands:

bcdedit /set {12345678-...} device partition=R:
bcdedit /set {12345678-...} path \Recovery\WindowsRE\Winre.wim
bcdedit /set {12345678-...} osdevice partition=R:
bcdedit /set {12345678-...} systemroot \Windows
bcdedit /set {12345678-...} winre yes

Then set it as the default recovery entry:

bcdedit /set {current} recoveryenabled yes
bcdedit /set {current} recoverysequence {12345678-...}

If it still fails

Sometimes the recovery partition itself is toast — corrupted beyond repair. In that case, don't bother fighting it. Just rebuild a fresh one:

1. Shrink your main C: partition by about 1GB using Disk Management.
2. Create a new simple volume from that unallocated space, format it as NTFS, label it "Recovery".
3. Assign it a letter temporarily (say R:).
4. Run these commands from an admin command prompt:
   reagentc /disable
reagentc /setreimage /path R:\Recovery\WindowsRE /target C:\Windows
reagentc /enable
5. Remove the drive letter after verifying WinRE works.

If reagentc /enable still fails, you might be dealing with a corrupt OS image. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated command prompt. Had a case where a third-party antivirus had hosed the system files — uninstalling it fixed the WinRE issue.

Last resort: backup your data and do a fresh Windows install with the installation USB. Use the "Keep personal files and apps" option — it'll keep your data but rebuild the entire system partition structure, which always fixes WinRE.

I've fixed this on maybe fifty machines. The BCDedit route takes the longest but works when nothing else does. If you're in a hurry, nuke the old recovery partition and create a new one — that's my go-to for client machines because it's repeatable and doesn't require hunting down GUIDs.