WinRE update KB5087371 fails to install (Win10 22H2)

JoMcKen-9333 80 Reputation points
2026-04-15T04:40:00.4433333+00:00

This is the third time in the last year I’ve been forced to ask for help with installing a WinRE update. I’m starting to think I’m cursed.

Earlier today (April 14, Patch Tuesday), several security updates dropped for Windows 10, all but one of which I installed without issue. The remaining update – KB5087371, “Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: April 14, 2026” – fails to install with an unspecified error every time I try.

Now, the last time I couldn’t install a WinRE security update was due to insufficient free space in the recovery partition. To remedy that, I doubled the partition’s size to 1 GB, which allowed me to install the update I was dealing with at the time without further issue. I just checked, and the partition presently has over 500 MB of free space, more than double the 250 MB requirement listed in the update’s info page. Yet it refuses to install.

Disk Management screenshot showing 1000 MB recovery partition

Microsoft Windows [Version 10.0.19045.7184]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk2\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: ac6d8547-f2bf-11f0-bd8a-401c83cf49bd
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.


C:\Windows\system32> dir c:\windows\system32\recovery /a
 Volume in drive C is System (HD1)
 Volume Serial Number is FA7B-E6ED

 Directory of c:\windows\system32\recovery

01/17/2026  03:24    <DIR>          .
01/17/2026  03:24    <DIR>          ..
01/17/2026  03:24             1,139 ReAgent.xml
               1 File(s)          1,139 bytes
               2 Dir(s)  258,051,788,800 bytes free

As always, any help would be appreciated.

Windows for home | Windows 10 | Windows update

Locked Question. 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

AI answer

2026-04-15T04:40:32.46+00:00

KB5087371 is a WinRE (Windows Recovery Environment) update, and these follow the same servicing rules as earlier WinRE updates for Windows 10 21H2/22H2.

From the existing WinRE update documentation for Windows 10 21H2/22H2:

  1. The WinRE update is only offered and installed if all of the following are true:
    • WinRE is enabled (reagentc /info shows Windows RE status: Enabled).
    • The recovery partition has at least 250 MB of free space.
    • The WinRE image version is less than the minimum version specified for that update.
    • The WinRE partition exists on disk.
    KB5057589 documents this explicitly and KB5068164/KB5075039 follow the same pattern.
  2. If the WinRE image is already at or above the version required by a newer WinRE update, Windows Update will not install the new package. KB5057589 states that the update is not offered when the WinRE image version is greater than or equal to 10.0.19041.5728, and KB5075039 raises this minimum to 10.0.19041.6807.
  3. For systems where the recovery partition is large enough (as in this case, 1 GB with >500 MB free), the other common cause of WinRE update failures is that the WinRE image has already been updated manually or by a previous WinRE update. KB5057589 notes that if the WinRE partition was manually updated using the procedure in Add an update package to Windows RE, or if the WinRE image version is already at or above the threshold, the WinRE update will not be offered or applied.

Given the information provided:

  • reagentc /info confirms WinRE is enabled and points to the expected recovery partition.
  • The recovery partition is 1 GB with ample free space, exceeding the 250 MB requirement documented for KB5057589, KB5068164, and KB5075039.

The most likely explanations, consistent with the existing WinRE update guidance, are:

  • The WinRE image on the recovery partition is already at or above the version required by KB5087371 (for example, due to KB5075039 or another Safe OS Dynamic Update already having been applied), or
  • The WinRE image was previously updated manually using the WinRE servicing procedure, so Windows Update is treating the image as already up to date.

In both cases, Windows Update may still show a transient failure entry, but the underlying WinRE image is already updated and functional. This behavior is similar to the known issue described for KB5057589, where Windows Update can report an error even though the WinRE update has been applied successfully; that issue was later corrected by a subsequent cumulative update.

Practical steps based on the documented behavior:

  1. Verify WinRE version
    • Follow the "Methods to verify the WinRE version installed" section referenced in the WinRE update KBs (for example in KB5057589 and KB5075039) to check the actual version of winre.wim on the recovery partition.
    • If the version is greater than or equal to the minimum version documented for the latest WinRE update (analogous to 10.0.19041.6807 for KB5075039), no further action is required; the image already contains the necessary Safe OS Dynamic Update.
  2. Confirm partition size is not the blocker
    • The current 1 GB recovery partition already satisfies the documented requirement of 250 MB free space for WinRE updates (KB5057589, KB5068164, KB5075039). No additional resizing is required.
  3. If Windows Update continues to show a failure but WinRE version is current
    • This matches the pattern of the known issue described in KB5057589, where error codes are cosmetic and cleared by a later cumulative update. Installing the latest cumulative update for Windows 10 (once available) should clear any stale failure status.

If, after checking, the WinRE version is below the required level and the update still fails, the next step consistent with Microsoft guidance would be to:

  • Use the WinRE partition resize and servicing instructions in KB5028997 together with the "Add an update package to Windows RE" procedure to manually update the WinRE image, then rerun Windows Update.

References:

AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

2 people found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. AlecF 0 Reputation points
    2026-04-24T16:53:46.2033333+00:00
    1. Check that WinRE is enabled reagentc /info
    2. Check that Recovery partition is big enough (Currently my winre.wim is about 900MB, plus you want some wiggle room on top of it -- 1.2G recommended). Resize if needed. (Look up KB5028997 for instructions, but please DO NOT try to follow it if you don't understand exactly what's described in the article. You are better off without working WinRE than with a massive data loss.)
    3. Check system partition for leftover $WinREAgent directory in the root. Delete it if it exists.
    4. Check that you don't have any other partition with Windows installation on your PC. Physically disconnect any extra drives before doing update. (In my case updater created update.wim where it should be, but then tried to open it from a different drive that had unmounted partition with a different windows installation.)
    5. If all fails check %WINDIR%\Logs\WinREAgent directory for logs. Or you can start with that, actually :D %SYSTEMDRIVE%\$WinREAgent\WinREServicingManager.xml also has some information on which steps were and weren't successfully completed.

    Good luck!

    Was this answer helpful?

    1 person found this answer helpful.
  2. H6733 0 Reputation points
    2026-04-20T00:24:20.7533333+00:00

    I just went thru this whole mess. I think the solution is also hurry up and wait, if you are compliant with the KB5037871 requirements.

    Copilot advised me that if you have WinRE version 6807, this is the minimum requirement for KB5037871, though 7177 is the current version.

    winre.wim is a hidden system file. I found mine on my recovery partition, which is the \?... path you have. This involved assigning a drive letter to the hidden winRE partition, which you can use diskpart in an admin terminal. There's a powershell script to do this, https://support.microsoft.com/en-us/topic/methods-to-verify-the-winre-version-installed-46d08ea2-07a8-4fa8-9228-2404955a30aa
    but there's also a couple other ways:

    1. Get-WindowsImage -ImagePath '\\?\GLOBALROOT\device\harddiskX\partitionY\Recovery\WindowsRE\winre.wim' -Index 1 | Select-Object Version, ModifiedTime You can get the values for X and Y via diskpart, list disk, then select disk z, and list partition for each disk z until you find the winRE partition, assign drive letter, and step thru the path. Copilot also stated to remove the letter assignment when you're done.
    2. Confirm WinRE Version (from copilot)
    • After installing KB5087371, the WinRE version must be ≥ 10.0.19041.7177.
    • To check your currently installed WinRE version:
      1. Navigate to the recovery partition using the instructions in the official KB5087371 guidance.
      2. Use: 
     dism /image:<WinRE_path> /Get-CurrentEdition
 ```
    1. Compare the version number to the minimum requirement.

    After I got this far, Copilot led me to this post and I think the "cumulative updates to fix a 'cosmetic' error" is where i'm at.

    The bummer right now is that there are still a few more updates after this that need to be complete, and this is stalling everything.

    Was this answer helpful?

    0 comments