WinRE update KB5098815 fails to install (Win10 22H2 w/ ESU)

Question

WinRE update KB5098815 fails to install (Win10 22H2 w/ ESU)

JoMcKen-9333 60

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:
User's image

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.

0 comments

4 answers

Your answer

Answer 1

Ramesh 176.3K Volunteer Moderator

It's a slightly different error now. Error code 0xc1420117

Couldn't unmount the WIM.

Here are some options:

Copy Winre.wim from another Windows 10 computer running the same version/language

(or)

Update Winre.wim as we did earlier.

Please share your Farbar scan logs for analysis.

Download Farbar Recovery Scan Tool 64-bit FRST64.exe
If the OS language is not English, rename FRST64.exe to FRST64English.exe.
Run the program. Don't check or uncheck any options. Click "Scan".
Add the two logs, FRST.txt and Addition.txt, to a zip archive.
Share the zip file on OneDrive or GoFile.io, and post the link here.

Note: If Microsoft Edge or Chrome mislabels the Farbar Scanner executable as PUA/malware, choose to keep it by tapping … in the bottom bar, choosing Keep, and then choosing Keep anyway in the dialog that appears. See this screenshot. It's a safe tool used in most antimalware forums.

JoMcKen-9333 60 Reputation points

2026-06-13T04:54:07.91+00:00

I’d like to try copying winre.wim from my Win10 laptop first; hopefully that would be faster. The laptop is fully updated (it has no available Windows Updates), so its winre.wim should be good. (There is no winre.wim in my laptop’s System32\Recovery folder; hopefully we can extract a copy from its recovery partition?)

My FRST64 scan results: https://gofile.io/d/jwIoey

Answer 2

Ramesh 176.3K Volunteer Moderator

Please run:

Dism.exe /UnMount-Wim /MountDir:"C:\mount\winre" /Discard
Dism.exe /UnMount-Wim /MountDir:"C:\$WinREAgent\Scratch\Mount" /Discard
Dism.exe /UnMount-Wim /MountDir:"C:\Users\Noc\AppData\Local\Temp\AomeiDateBackupper25136\mount" /Discard
Dism.exe /Cleanup-Wim
reg query "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" /s

Post the output.

JoMcKen-9333 60

Seems the /unmount-wim commands didn’t work for some reason, but here’s the output anyway:

C:\Windows\system32>Dism.exe /UnMount-Wim /MountDir:"C:\mount\winre" /Discard

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636


Error: 50

The request is not supported.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>Dism.exe /UnMount-Wim /MountDir:"C:\$WinREAgent\Scratch\Mount" /Discard

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636


Error: 50

The request is not supported.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>Dism.exe /UnMount-Wim /MountDir:"C:\Users\Noc\AppData\Local\Temp\AomeiDateBackupper25136\mount" /Discard

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636


Error: 50

The request is not supported.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>Dism.exe /Cleanup-Wim

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Unmounting image at C:\$RECYCLE.BIN\S-1-5-21-3689859802-142097239-3138972455-1001\$R0ANO8P
[==========================100.0%==========================]
Unmounting image at C:\$RECYCLE.BIN\S-1-5-21-3689859802-142097239-3138972455-1001\$RHLC7QD
[==========================100.0%==========================]
Stale mount entry pointing to C:\Mount\WinRE removed
Stale mount entry pointing to C:\mount\winre removed
Scanning drive C for stale files
Scanning drive D for stale files
Scanning drive E for stale files
Scanning drive G for stale files
Scanning drive H for stale files
The operation completed successfully.

C:\Windows\system32>reg query "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" /s

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\15d0e365-c1ea-4f5e-b19a-0ea5aa27100e
    Mount Version    REG_DWORD    0x10001
    Image time high    REG_DWORD    0x1dbf2bf
    Image time low    REG_DWORD    0xaaa4ee2
    Status    REG_DWORD    0x3
    Mount Path    REG_SZ    C:\Users\Noc\AppData\Local\Temp\AomeiDateBackupper25136\mount
    WIM Path    REG_SZ    C:\Users\Noc\AppData\Local\Temp\AomeiDateBackupper25136\winpe.wim
    Image Index    REG_DWORD    0x1
    FileCount    REG_DWORD    0x3f3b
    Mount path high    REG_DWORD    0x1760000
    Mount path low    REG_DWORD    0x429c4

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\e3bd0f66-c8f3-44b1-b9bd-ec8fe5bf6287
    Mount Version    REG_DWORD    0x10001
    Image time high    REG_DWORD    0x1dc167d
    Image time low    REG_DWORD    0x1005cff3
    Status    REG_DWORD    0x3
    Mount Path    REG_SZ    C:\$WinREAgent\Scratch\Mount
    WIM Path    REG_SZ    C:\$WinREAgent\Scratch\update.wim
    Image Index    REG_DWORD    0x1
    FileCount    REG_DWORD    0x4025
    Mount path high    REG_DWORD    0x1320000
    Mount path low    REG_DWORD    0x42a8e

Ramesh 176.3K Reputation points Volunteer Moderator

2026-06-13T02:31:54.15+00:00
Rerun the commands.

If the stale images can't be unmounted, please open Regedit.exe and delete the subkeys of the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images

JoMcKen-9333 60

I ran the commands again and received the same output:

C:\Windows\system32>Dism.exe /UnMount-Wim /MountDir:"C:\mount\winre" /Discard

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636


Error: 50

The request is not supported.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>Dism.exe /UnMount-Wim /MountDir:"C:\$WinREAgent\Scratch\Mount" /Discard

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636


Error: 50

The request is not supported.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>Dism.exe /UnMount-Wim /MountDir:"C:\Users\Noc\AppData\Local\Temp\AomeiDateBackupper25136\mount" /Discard

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636


Error: 50

The request is not supported.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>Dism.exe /Cleanup-Wim

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Unmounting image at C:\$RECYCLE.BIN\S-1-5-21-3689859802-142097239-3138972455-1001\$R0ANO8P
[==========================100.0%==========================]
Unmounting image at C:\$RECYCLE.BIN\S-1-5-21-3689859802-142097239-3138972455-1001\$RHLC7QD
[==========================100.0%==========================]
Scanning drive C for stale files
Scanning drive D for stale files
Scanning drive E for stale files
Scanning drive G for stale files
Scanning drive H for stale files
The operation completed successfully.

C:\Windows\system32>reg query "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" /s

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\15d0e365-c1ea-4f5e-b19a-0ea5aa27100e
    Mount Version    REG_DWORD    0x10001
    Image time high    REG_DWORD    0x1dbf2bf
    Image time low    REG_DWORD    0xaaa4ee2
    Status    REG_DWORD    0x3
    Mount Path    REG_SZ    C:\Users\Noc\AppData\Local\Temp\AomeiDateBackupper25136\mount
    WIM Path    REG_SZ    C:\Users\Noc\AppData\Local\Temp\AomeiDateBackupper25136\winpe.wim
    Image Index    REG_DWORD    0x1
    FileCount    REG_DWORD    0x3f3b
    Mount path high    REG_DWORD    0x1760000
    Mount path low    REG_DWORD    0x429c4

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\e3bd0f66-c8f3-44b1-b9bd-ec8fe5bf6287
    Mount Version    REG_DWORD    0x10001
    Image time high    REG_DWORD    0x1dc167d
    Image time low    REG_DWORD    0x1005cff3
    Status    REG_DWORD    0x3
    Mount Path    REG_SZ    C:\$WinREAgent\Scratch\Mount
    WIM Path    REG_SZ    C:\$WinREAgent\Scratch\update.wim
    Image Index    REG_DWORD    0x1
    FileCount    REG_DWORD    0x4025
    Mount path high    REG_DWORD    0x1320000
    Mount path low    REG_DWORD    0x42a8e

I then manually deleted the two keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images, and then ran the last two commands again, confirming the images have apparently been unmounted:

C:\Windows\system32>Dism.exe /Cleanup-Wim

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Scanning drive C for stale files
Scanning drive D for stale files
Scanning drive E for stale files
Scanning drive G for stale files
Scanning drive H for stale files
The operation completed successfully.

C:\Windows\system32>reg query "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" /s


C:\Windows\system32>

Ramesh 176.3K Reputation points Volunteer Moderator

2026-06-13T03:02:18.4133333+00:00
Please delete the following folder:

C:\$WinREAgent

Rename the following file:

C:\Windows\system32\Recovery\Winre.wim

Install the WinRE update now.
JoMcKen-9333 60 Reputation points

2026-06-13T03:06:07.8166667+00:00

Deleted C:\$WinREAgent.

To clarify, should I rename …\Recovery\Winre.wim to something specific, or should I just change its name to anything other than the original?
Ramesh 176.3K Reputation points Volunteer Moderator

2026-06-13T03:06:56.2933333+00:00

You may move that file to some other directory.
JoMcKen-9333 60 Reputation points

2026-06-13T03:12:47.03+00:00

All right, I renamed it to Winre.wim.BAK (I assume this accomplishes the same thing).

Unfortunately, both KB5098815 and KB5042320 then failed to install with “internal error” messages.
JoMcKen-9333 60 Reputation points

2026-06-13T03:15:28.8+00:00

I took the liberty of uploading a new ZIP of the WinREAgent logs folder, in case it’s useful: https://gofile.io/d/Onz7ce

Answer 3

Ramesh 176.3K Volunteer Moderator

The system encountered the error 0xc1420127 when mounting or unmounting the WinRE image.

2026-06-11 03:05:30, Error                        0xc1420127 in WinREAgent::PrepareWinRE::InternalExecute (base\diagnosis\srt\winreagent\lib\operations\src\preparewinre.cpp:304): Failed to mount winre image[gle=0x0000007a]
2026-06-11 03:05:30, Error                        0xc1420127 in WinREAgent::Operation::Execute (base\diagnosis\srt\winreagent\lib\operations\src\operation.cpp:167): Internal failure to execute operation[gle=0x0000007a]
2026-06-11 03:05:30, Error                        0xc1420127 in WinREAgent::Executor::Stage (base\diagnosis\srt\winreagent\dll\executor.cpp:1027): Failed to execute operation [PrepareWinRE][gle=0x0000007a]
2026-06-11 03:05:30, Error                        0xc1420127 in WinREAgent::WinREServicingManager::Stage (base\diagnosis\srt\winreagent\dll\winreservicingmanager.cpp:485): Failed to stage WinRE servicing[gle=0x0000007a]
2026-06-11 03:05:30, Error                        0xc1420127 in wmain (base\diagnosis\srt\winreagent\tools\winreupdateinstaller\main.cpp:118): [WinREUpdInst] Failed to stage WinRE servicing operation[gle=0x0000007a]

Please post the output of the following commands:

DISM /Get-MountedWiminfo

reg query "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" /s

JoMcKen-9333 60

The output you requested:

C:\Windows\system32>DISM /Get-MountedWiminfo

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Mounted images:

Mount Dir : C:\$RECYCLE.BIN\S-1-5-21-3689859802-142097239-3138972455-1001\$R0ANO8P
Image File : C:\Users\Noc\AppData\Local\Temp\AomeiDateBackupper25136\winpe.wim
Image Index : 1
Mounted Read/Write : Yes
Status : Invalid

Mount Dir : C:\$RECYCLE.BIN\S-1-5-21-3689859802-142097239-3138972455-1001\$RHLC7QD
Image File : C:\$WinREAgent\Scratch\update.wim
Image Index : 1
Mounted Read/Write : Yes
Status : Invalid

The operation completed successfully.

C:\Windows\system32>reg query "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" /s

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\15d0e365-c1ea-4f5e-b19a-0ea5aa27100e
    Mount Version    REG_DWORD    0x10001
    Image time high    REG_DWORD    0x1dbf2bf
    Image time low    REG_DWORD    0xaaa4ee2
    Status    REG_DWORD    0x3
    Mount Path    REG_SZ    C:\Users\Noc\AppData\Local\Temp\AomeiDateBackupper25136\mount
    WIM Path    REG_SZ    C:\Users\Noc\AppData\Local\Temp\AomeiDateBackupper25136\winpe.wim
    Image Index    REG_DWORD    0x1
    FileCount    REG_DWORD    0x3f3b
    Mount path high    REG_DWORD    0x1760000
    Mount path low    REG_DWORD    0x429c4

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\96e84ec8-f671-43f1-9a19-2820dc7bfd9a
    Mount Version    REG_DWORD    0x10001
    Image time high    REG_DWORD    0x1dc8764
    Image time low    REG_DWORD    0xa3d19ca
    Status    REG_DWORD    0x3
    Mount Path    REG_SZ    C:\Mount\WinRE
    WIM Path    REG_SZ    C:\WinRE\winre.wim
    Image Index    REG_DWORD    0x1
    FileCount    REG_DWORD    0x3f3b
    Mount path high    REG_DWORD    0x2480000
    Mount path low    REG_DWORD    0x1ac0

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\a05eb7b0-1860-42a4-a6b7-dabf0f32b2ac
    Mount Version    REG_DWORD    0x10001
    Image time high    REG_DWORD    0x1dc173e
    Image time low    REG_DWORD    0x3399e569
    Status    REG_DWORD    0x3
    Mount Path    REG_SZ    C:\mount\winre
    WIM Path    REG_SZ    C:\winre\winre.wim
    Image Index    REG_DWORD    0x1
    FileCount    REG_DWORD    0x40b3
    Mount path high    REG_DWORD    0x4840000
    Mount path low    REG_DWORD    0x1a642

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images\e3bd0f66-c8f3-44b1-b9bd-ec8fe5bf6287
    Mount Version    REG_DWORD    0x10001
    Image time high    REG_DWORD    0x1dc167d
    Image time low    REG_DWORD    0x1005cff3
    Status    REG_DWORD    0x3
    Mount Path    REG_SZ    C:\$WinREAgent\Scratch\Mount
    WIM Path    REG_SZ    C:\$WinREAgent\Scratch\update.wim
    Image Index    REG_DWORD    0x1
    FileCount    REG_DWORD    0x4025
    Mount path high    REG_DWORD    0x1320000
    Mount path low    REG_DWORD    0x42a8e

I have to assume “AomeiDateBackupper25136\winpe.wim” is a leftover from when I used Aomei Partition Assistant (amongst other tools) to re-partition my drive during the convoluted re-imaging process … last August.

JoMcKen-9333 60 Reputation points

2026-06-12T11:57:42.67+00:00

What on earth is going on with this site’s automod? I am very tired of my replies being deleted upon posting.

Will try again.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
JoMcKen-9333 60 Reputation points

2026-06-12T12:00:00.56+00:00

FFS.

Maybe I should send my reply by email or Ouija or something, since the site apparently thinks posting my CMD output here is a “violation of [its] Code of Conduct”.

Trying one last time, just the raw output.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
JoMcKen-9333 60 Reputation points

2026-06-12T12:03:34.57+00:00

Amazing. Maybe if I screencap it?

Fingers crossed!
JoMcKen-9333 60 Reputation points

2026-06-12T12:06:29.15+00:00

Well, that worked, at least.

As I was trying to say in my now-deleted posts: I have to assume “AomeiDateBackupper25136\winpe.wim” is a leftover from when I used Aomei Partition Assistant (amongst several other apps) to re-partition my disk during the convoluted re-imaging process … last August.
JoMcKen-9333 60 Reputation points

2026-06-12T12:23:41.52+00:00

Quick update, both because it might be relevant and because I’m not sure what to do about it: I went to create a System Restore point just now, and “Windows RE tools” – the label I assigned to my recovery partition, per the instructions in the guides linked in the OP – shows up under “Available Drives”.

I’m reasonably sure my recovery partition shouldn’t be showing up as a System Restore drive …

Answer 4

Ramesh 176.3K Volunteer Moderator

Hi,

I would especially love it if we can make it so that WinRE updates normally via Windows Update once and for all.

For some reason, the system is unable to unmount the serviced WinRE image, as seen in your other threads.

Please copy the following folder to your desktop. Zip the folder and share it on OneDrive or GoFile.io.

C:\Windows\Logs\WinREAgent

JoMcKen-9333 60 Reputation points

2026-06-12T08:19:50.05+00:00

Thanks. Here’s the WinREAgent folder: https://gofile.io/d/sRr3DH
JoMcKen-9333 60 Reputation points

2026-06-12T09:27:53.3+00:00

Quick update/FYI: As of the steps taken in the OP, I now have two Windows Updates that fail to install, the aforementioned KB5098815 as well as KB5042320, which was one of the updates that you helped me with last August (since recreating the recovery partition restored the WinRE image to its stock state from the Win10 ISO, and it apparently doesn’t have the latest updates applied to it).

Share via

WinRE update KB5098815 fails to install (Win10 22H2 w/ ESU)

4 answers

Your answer