After copying winre.wim and enabling Windows RE, run:
dism /Get-WimInfo /WimFile:\\?\GLOBALROOT\device\harddisk2\partition4\Recovery\WindowsRE\winre.wim /index:1
WinRE update KB5098815 fails to install (Win10 22H2 w/ ESU)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 73%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ9%3C/text%3E%3C/svg%3E)
JoMcKen-9333
80
Reputation points
This is the fourth time in less than one year that I’ve had trouble installing a WinRE update. I am most definitely cursed.
A quick rundown, because I don’t know what might be relevant info at this point:
Last August, I re-imaged my system drive using Acronis True Image, which nuked my original recovery partition; after manually recreating it, a couple WinRE updates refused to install, until Ramesh Srinivasan kindly helped me get them working.
Then in January, WinRE security update KB5068164 refused to install due to insufficient free space in the recovery partition. Ramesh walked me through expanding and updating it manually – my thanks again.
Then in April, WinRE update KB5087371 refused to install. The site’s AI answer suggested that a WinRE image that had been manually updated (as was the case with mine) can cause the update to fail, and that my WinRE image version indicated the update wasn’t necessary anyway, and that if I ignored the update a subsequent Windows cumulative update would remove it from the update queue, which it did. I figured things might finally be settled.
Well, another WinRE update is here, and guess what’s back? This time it’s WinRE update KB5098815, and once again it’s failing to install with an unspecified error. Out of an abundance of caution, I went ahead and doubled the recovery partition size to 2 GB (using the instructions in this guide), just to make extremely sure it isn’t failing to update due to insufficient space, but it is still failing. (I also used this other guide to solve the “Windows RE image was not found” error I received when trying to re-enable WinRE after following the first guide.)
Disk Management:
Command Prompt readout showing reagentc /info, recovery partition free space (1.7 GB), and System32\Recovery directory contents:
Microsoft Windows [Version 10.0.19045.7417]
(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: ac6d8549-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>fsutil volume diskfree \\?\GLOBALROOT\device\harddisk2\partition4\Recovery\WindowsRE
Total free bytes : 1,862,246,400 (1.7 GB)
Total bytes : 2,348,806,144 (2.2 GB)
Total quota free bytes : 1,862,246,400 (1.7 GB)
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
06/11/2026 03:07 <DIR> .
06/11/2026 03:07 <DIR> ..
06/11/2026 03:04 1,109 ReAgent.xml
12/03/2023 22:37 466,404,365 Winre.wim
2 File(s) 466,405,474 bytes
2 Dir(s) 257,129,537,536 bytes free
(I’d provide a link to a ZIP archive containing my System32\Recovery files, but the last time I added that to a post in a previous thread the site’s daft filters kept auto-deleting my post, and I don’t wanna risk being forced to retype this whole post again.)
Once more, any assistance would be really appreciated. I would especially love it if we can make it so that WinRE updates normally via Windows Update once and for all.
Windows for home | Windows 10 | Windows update
Answer accepted by question author
Ramesh
181.6K
Reputation points
Volunteer Moderator
-
JoMcKen-9333 80 Reputation points
2026-06-15T06:25:36.6233333+00:00 And that did it! Successfully applied the updated winre.wim, and
dism /get-wimwinfoconfirms I’m now on WinRE v10.0.19041.7417. I then took the liberty of tweaking your previously providedwinreversion.regby editing "WinREVersion" to the current version, merged it, and at long last, KB5098815 has now disappeared from the Windows Update queue.The problem is, for now, solved.
Now, given that my PC seems unable to update WinRE by itself, I’m considering what to do about future WinRE updates. I have no problem with manually applying an updated winre.wim image by following the steps you’ve provided here. My question: Is there a way to reliably download an updated winre.wim (like the ones you uploaded)?
Sign in to comment
8 additional answers
Sort by: Oldest
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T04:22:17.3633333+00:00 On the subject PC, run:
reagentc /disable dir c:\windows\system32\recovery /aPost the output.
-
JoMcKen-9333 80 Reputation points
2026-06-15T04:28:15.46+00:00 Going to post sceencaps from now on to avoid getting auto-deleted; I hope that’s all right.
Please ignore the “Winre.wim.BAK”; it’s a copy I created a few days ago so that it wouldn’t get auto-deleted, but I have now deleted it.
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T04:30:28.2566667+00:00 Rename
C:\Windows\System32\Recovery\Winre.wimtoWinre.wim.bak2Now, copy the downloaded
Winre.wimto that folder.Run:
reagentc /enable reagentc /info -
JoMcKen-9333 80 Reputation points
2026-06-15T04:36:55.93+00:00 Output:
(The
reagentc /enableoperation predictably deleted the new winre.wim from the…\System32\Recoveryfolder, so I created a BAK of that file as well. Let me know if I should delete it.) -
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T04:47:05.44+00:00 Run:
dism /Get-WimInfo /WimFile:\\?\GLOBALROOT\device\harddisk2\partition4\Recovery\WindowsRE\winre.wim /index:1 -
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T04:52:07.4866667+00:00 Download winreversion.reg.txt
Rename it to
winreversion.regDouble-click the file to run it. Click Yes to confirm.
Check for updates.
-
JoMcKen-9333 80 Reputation points
2026-06-15T04:56:25.3966667+00:00 Registry file merged. Checked for updates. KB5042320 has now disappeared from the queue, but KB5098815 remains (and still fails to install).
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T04:59:28.7233333+00:00 Looks like my the latest WinRE update (19041.7417) hasn't been offered for my system.
My WinRE version remains at 10.0.19041.7177.
Strange. Will see if I can get the latest Winre image from a VM.
-
JoMcKen-9333 80 Reputation points
2026-06-15T05:06:13.5+00:00 Ah, that explains it. Gradual rollout, I suppose?
Also – do you have any idea why my laptop, which is otherwise fully updated, isn’t showing any WinRE updates despite having a functioning, outdated recovery partition?
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T05:11:10.45+00:00 Per Microsoft:
"This update will not be offered if your Windows Recovery Environment (WinRE) meets any of the following conditions:"
-
JoMcKen-9333 80 Reputation points
2026-06-15T05:21:12.24+00:00 Ah, right. Just checked, and my laptop’s recovery partition only has 80 MB of free space. That explains it.
Honestly, unless updating WinRE is crucial, I’m leaning towards leaving it be, since with my luck expanding its partition and recreating it is only going to result in two computers that refuse to update their recovery partitions.
Sign in to comment -
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T05:26:59.8633333+00:00 Update:
I found that, unlike the earlier WinRE updates, the June 2026 WinRE update strictly requires 250 MB of free space. If it's less, the update is not offered.
Here's the latest → Winre.wim.
On the subject computer, run:
reagentc /disable del /a C:\Windows\System32\Recovery\Winre.wimNow, copy the downloaded Winre.wim to
C:\Windows\System32\Recovery.Run:
reagentc /enable reagentc /info `` -
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T06:29:24.5133333+00:00 Glad that helped.
Now, given that my PC seems unable to update WinRE by itself, I have no problem with manually applying an updated winre.wim image by following the steps you’ve provided here. My question: Is there a way to reliably download an updated winre.wim (like the ones you uploaded)?
Chances are a filter driver is preventing the mounting of WIM files on your system. Veracrypt adds some filter drivers.
You may also try a repair install using the Windows 10 Media Creation Tool.
Note:
Windows 10 ESU support end in October 2026. There won't be any more updates. Until then, you may simply follow the Winre.wim copy workaround after every update is released.
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T06:31:07.8866667+00:00 Is there a way to reliably download an updated winre.wim (like the ones you uploaded)?
You can copy the latest Winre.wim from your laptop. But, the laptop's WinRE must be fixed first. We can resize the Recovery partition on that system or more winre.wim to the C drive. Please start a new thread for that system.
-
JoMcKen-9333 80 Reputation points
2026-06-15T07:03:33.2166667+00:00 My laptop is also encrypted with VeraCrypt, same as my desktop, and shares many of its apps and configurations. I think it’s very likely that resizing its partitions, recreating a recovery partition, etc. will leave it in the same state as my desktop – with an outdated WinRE that still can’t update automatically. And whilst uninstalling VeraCrypt might let me update WinRE, it would be far more trouble to have to decrypt everything, uninstall VC, and then reinstall VC and re-encrypt everything afterwards, every time a WinRE update is released.
Is there no other way to obtain an updated Winre.wim easily, such as from Microsoft itself? I would have thought MS would let you download it somewhere, same as it does with individual WU updates and even entire Windows ISOs.
If not, then my other options would be to either manually update the WinRE image offline – which would require instructions, and whilst I have no problem following them for each future update, I hesitate to ask for even more of your time after everything you’ve already done to help me – or to simply ignore WinRE updates until the end of ESU support.
How risky would it be if I simply ignored WinRE updates?
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T07:06:24.2533333+00:00 - If you don't use BitLocker, you can skip the WinRE update.
- I don't know if Veracrypt IS the root cause. I'm only guessing because it adds one or more filter drivers.
- I'd still suggest starting a new thread for your laptop. If we can fix WinRE on that system, you can simply copy its winre.wim to your desktop PC for future updates.
- Alternatively, you can download the latest Windows 10 ISO from uupdump and extract Winre.wim from it.
-
JoMcKen-9333 80 Reputation points
2026-06-15T09:00:31.2133333+00:00 1 – Ah, so WinRE updates are only/mainly helpful for folks who use BitLocker? (I indeed don’t use BL.)
4 – This is my first time hearing of UUP dump, and it looks like an amazing resource. However:
I successfully created an ISO from the latest update (2026-06 Cumulative Update), and from it extracted install.wim → winre.wim. However, it seems that this winre.wim is still outdated:
Did I do something wrong? Is there a specific option or method that creates an updated Winre.wim?
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T09:42:27.59+00:00 Regarding #1: I think my earlier statement is incorrect. The WinRE security updates not only fix the BitLocker vulnerabilities, but may also include other fixes (e.g., secure boot fixes) and improvements. So, please install these updates anyway. But if you don't plan to use WinRE, you can disable it using reagentc /disable. In that case, the updates won't be offered. You can still access WinRE using the Windows 10 USB setup disk.
#4: When you downloaded the ISO from uupdump, did you enable the Include updates checkbox?
I'm downloading it right now. As you can see below, it's patching the winre.wim with the latest WinRE update.
Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_SafeOSDU~31bf3856ad364e35~amd64~~19041.7417.1.6 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.19041.3636 Image Version: 10.0.19041.7417 [========================== 45.7% ] -
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T09:48:06.8766667+00:00 Done. Here's the Winre.wim version:
Details for image : E:\winre.wim Index : 1 Name : Microsoft Windows Recovery Environment (x64) Description : Microsoft Windows Recovery Environment (x64) Size : 2,126,397,588 bytes WIM Bootable : No Architecture : x64 Hal : <undefined> Version : **10.0.19041** ServicePack Build : **7417** ServicePack Level : 0 Edition : WindowsPE Installation : WindowsPE ProductType : WinNT ProductSuite : System Root : WINDOWS Directories : 4069 Files : 17242 Created : 12/7/2019 - 12:41:48 PM Modified : 6/15/2026 - 3:11:45 PM Languages : en-US (Default) The operation completed successfully. -
JoMcKen-9333 80 Reputation points
2026-06-15T09:53:43.5066667+00:00 #1: Yeah, I like having WinRE on my machine on a just-in-case basis.
#2: I did indeed check that box! Really not sure what happened. Must’ve messed something else up.
Funnily enough, after creating that ISO, I then realized I could configure the creation process further (disabling installation of Microsoft apps, etc.). So I plan to try building a new ISO anyway (this time with install.ESD, which will hopefully shave off a GB or two). Maybe it’ll work this time?
That said – whilst putzing around I found this article with instructions for updating an offline WinRE image, just as you walked me through doing months ago. I decided to try it, and I think I’ve succeeded – I have a 505 MB Winre.wim image that DISM tells me is v10.0.19041.7417. Will now try applying it to my WinRE (after backing up the current Winre.wim, just in case this one is messed up somehow) and reboot to test it. If it works, then I’ve finally learned how to update an offline image myself … and it’s probably for nothing if I can just generate an updated WIM from the UUP method. 🥴But, one thing at a time. Testing the manually updated image now.
-
JoMcKen-9333 80 Reputation points
2026-06-15T10:10:51.96+00:00 Update: It worked! Though I’m still not sure why the Winre.wim I updated manually is about 70 MB smaller than the Winre.wim you sent me earlier. Seems like quite the difference. 🤔
Now I’ll try creating a new ISO with UUP. Hopefully it works this time.
-
JoMcKen-9333 80 Reputation points
2026-06-15T10:16:55.5766667+00:00 Stupid automod. As I said: The new WinRE works, though I’m not sure why the manually updated Winre.wim is 70 MB smaller than the Winre.wim you sent me earlier.
Will now create a new ISO with UUP. Hopefully it’ll create an updated Winre.wim this time.
-
JoMcKen-9333 80 Reputation points
2026-06-15T10:18:41.8566667+00:00 Forgot to ask: I exclusively use Win10 Pro, so when choosing my UUP package I deselect “Windows Home”. Could this possibly affect the Winre.wim somehow?
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T10:31:24.17+00:00 Winre.wim should be the same for all editions.
Though I’m still not sure why the Winre.wim I updated manually is about 70 MB smaller than the Winre.wim you sent me earlier.
The /StartComponentCleanup /ResetBase command may have trimed down the WIM by removing old updates.
-
JoMcKen-9333 80 Reputation points
2026-06-15T10:33:21.3833333+00:00 Ah, that makes sense. Thanks.
Running through the UUP script now. Will be a while, but I’m keeping an eye on it, hoping to catch that Winre.wim update when it goes by.
-
JoMcKen-9333 80 Reputation points
2026-06-15T11:28:57.6666667+00:00 Welp, created a new ISO, and once again the version is outdated, with a build of
1. Didn’t see thePackage_for_SafeOSDU~31bf3856ad364e35~amd64~~19041.7417.1.6update you screenshotted at all during the process. Though, as always with my cursed system, there were a bunch of “folders could not be deleted” and “image could not be fully unmounted” errors during the process, as always due to the “this directory is not empty” error that’s been bugging me for years, so that might well have something to do with it.Come to think of it though, my laptop’s never had that issue. So maybe I should try building the ISO on it. (Though it’s much older, so it’ll take forever … but whatevs. Will try that some other time.)
At any rate, the whole ISO-building process honestly takes way longer than manually updating the Winre.wim image does, so I think I’ll just stick to doing that in the future, now that I actually know how to do it.
So, yeah. I now know how to update my WinRE, and this should stick with future updates, so the issue is definitely solved.
Once again, thank you so very much for all the help, you’ve been beyond kind and patient. It’s much appreciated. 🙂
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T11:33:35.3833333+00:00 Yes. Please download the ISO from another system for future updates. Or post a reply in this thread so that I can upload the required Winre.wim.
Once again, thank you so very much for all the help, you’ve been beyond kind and patient. It’s much appreciated. 🙂
Glad to help. 👍
-
JoMcKen-9333 80 Reputation points
2026-06-15T13:47:01.74+00:00 Actually, there is one last little thing, if you truly don’t mind …
In the System Restore window, my recovery partition appears in the list of available drives, labeled “Windows RE tools” (the label I assigned to it in the guide I followed in the OP, using the command
format quick fs=ntfs label="Windows RE tools". I don’t suppose it’s a huge deal, but I’m pretty sure it’s not supposed to be listed there, and I wonder if it might indicate something deeper is wrong with it, since it was never there before.At any rate, how do I stop my recovery partition from appearing in System Restore?
-
Ramesh 181.6K Reputation points Volunteer Moderator
2026-06-15T14:39:06.84+00:00 Last I checked, the partition appears if it's greater than or equal to 1 GB. Shrinking the partition to 950 MB should help. It can be done using Diskpart or AOMEI.
-
JoMcKen-9333 80 Reputation points
2026-06-15T14:41:04.72+00:00 Ah, all right then. Thanks for the info!
-
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 76%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
sylvio 0 Reputation points2026-07-21T02:06:55.0133333+00:00 I got successful by copying wimre.wim in the Recovery folder of Windows and running enable disable with reagentc command. And used Windows repair tool from Tweaking.com the best! Otherwise my system always
crashed with a stopcode
Sign in to comment -