Hello,

I noticed two out of three of my Windows 10 (W10) machines' Disk Cleanup's Clean up system files' Windows Update Cleanup option still shows left over after cleaning them up. I know it says a reboot might be required, but I already rebooted W10 and reran Disk Cleanup to still see left overs. Why can't it remove all? Or is that by design?

Thank you for reading and hopefully answering soon. :)
--
"Accept him whose faith is weak, without passing judgment on disputable matters." --Romans 14:1. Slammy Mon. & maybe weekdays. VBox' updates broke stuff again. 4(.5?) hrs. of Z 4 this old ant on Veterans & updates (Moz & MS) Tues. :(
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Ant wrote on 11/11/2025 5:36 PM:

Hello,

I noticed two out of three of my Windows 10 (W10) machines' Disk Cleanup's Clean up system files' Windows Update Cleanup option still shows left over after cleaning them up. I know it says a reboot might be required, but I already rebooted W10 and reran Disk Cleanup to still see left overs. Why can't it remove all? Or is that by design?

Thank you for reading and hopefully answering soon. :)

Results experienced are the norm.

--
...w­¤?ñ?¤

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Tue, 11/11/2025 7:36 PM, Ant wrote:

Hello,

I noticed two out of three of my Windows 10 (W10) machines' Disk Cleanup's Clean up system files' Windows Update Cleanup option still shows left over after cleaning them up. I know it says a reboot might be required, but I already rebooted W10 and reran Disk Cleanup to still see left overs. Why can't it remove all? Or is that by design?

Thank you for reading and hopefully answering soon. :)

Some of what Windows does, is achieved via Compression and NOT by deletion.

From my notes file:

fsutil behavior query disablecompression # Normally compression is enabled

fsutil behavior set disablecompression 1 # disable new compression (done with Reparse Points, not ATTRIB bit setting)
# This prevents the OS from being naughty and wasting your time while
# you stare at the screen and beg for mercy. When Windows does discretionary
# compression, it is the New Compression type, for maximal annoyance.

# If you're on one of those 32GB tablets, DO NOT do this.
# Disabling compression is for "roomy" drives that can take it.
# Disabling compression makes it easier to do maintenance from Linux.
# Like Jasons "ntfs.sys" repair would be easy-as-pie, if compression was disabled
# and Linux was used to put a working one back in place.

# This applies to all the disks in the machine. It's all or nothing.
# A reboot is required for the policy to "take".

fsutil behavior set disablecompression 0 # You should turn compression back on, if a WinRE update is incoming.
# Some $ folders in the root of C: will be "pregnant" if a WinRE is required soon.
# What this means is, Windows did the prep, and your disable-ment of
# compression, prevents the completion of the WinRE update. As soon as
# compression is turned on, the operation completes. When the $ folders
# return to a couple megabytes, now you can disable compression again with "1".

The above fetish with New Compression, is mainly to allow a Linux run to achieve a result.
If you don't use Linux for occasional problem solving, you don't need this and you can keep viewing fluffy kitten photos if you want.

For the Windows Update cleanup, this thread [elevenforums, below] DISM is being called.
CleanMgr is calling DISM. You could attempt to verify this with ProcMon
or ProcExp from Sysinternals.

Cleanmgr will not be requesting a "rebase". This is a bridge too far.

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Various other forms of DISM.

dism.exe /Online /Cleanup-image /ScanHealth \
dism.exe /Online /Cleanup-image /CheckHealth \___ In increasing order of "activism"
dism.exe /Online /Cleanup-image /RestoreHealth /

dism.exe /Online /Cleanup-image /StartComponentCleanup # My GUESS for a cleanmgr option.
# If two libraries were present, and one not used,
# that obsolete library gets removed. Something like that.

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase # What Mayayana would use.

# Sample thread with discussions along these lines.

https://www.elevenforum.com/t/disk-cleanup-doesnt-clear-windows-update-cleanup.6694/

cleanmgr has three possible results:

1) Simple command execution ("del") that really works. Thumbnails maybe.

2) Attempted "del" that is piss-weak and does not work to anyones satisfaction. %temp% maybe.
Erasing %temp% by hand works most of the time. Only material with open handles, won't delete.

3) Devious schemes where you are not told exactly what style of fix is underway.
It could be compression or it could be a DISM of some sort. Personally, I would
prefer these were explained (a balloon over the tick box). If an operation is
going to take *three hours* to complete, the user should be informed of this.

Paul

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

...w??? <winstonmvp@gmail.com> wrote:

Ant wrote on 11/11/2025 5:36 PM:

Hello,

I noticed two out of three of my Windows 10 (W10) machines' Disk Cleanup's Clean up system files' Windows Update Cleanup option still shows left over after cleaning them up. I know it says a reboot might be required, but I already rebooted W10 and reran Disk Cleanup to still see left overs. Why can't it remove all? Or is that by design?

Thank you for reading and hopefully answering soon. :)

Results experienced are the norm.

Thank you for confirming that. I was expecting all of that to be cleaned up.
--
"May the Lord make your love increase and overflow for each other and for everyone else, just as ours does for you." --1 Thessalonians 3:12. Slammy tirey Tuesday.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Wed, 12 Nov 2025 00:36:08 -0000 (UTC), Ant wrote:

I noticed two out of three of my Windows 10 (W10) machines' Disk Cleanup's Clean up system files' Windows Update Cleanup option still shows left over after cleaning them up. I know it says a reboot might be required, but I already rebooted W10 and reran Disk Cleanup to still see left overs. Why can't it remove all? Or is that by design?

Thank you for reading and hopefully answering soon. :)

1. Check your word wrap settings.

2. Want to go crazy? Take a look at the size of C:\Windows\WinSxS.

--
s|b

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Wed, 11/12/2025 3:18 PM, s|b wrote:

On Wed, 12 Nov 2025 00:36:08 -0000 (UTC), Ant wrote:

I noticed two out of three of my Windows 10 (W10) machines' Disk Cleanup's Clean up system files' Windows Update Cleanup option still shows left over after cleaning them up. I know it says a reboot might be required, but I already rebooted W10 and reran Disk Cleanup to still see left overs. Why can't it remove all? Or is that by design?

Thank you for reading and hopefully answering soon. :)

1. Check your word wrap settings.

2. Want to go crazy? Take a look at the size of C:\Windows\WinSxS.

There generally isn't a lot of excess material in WinSxS.
You can squeeze a bit more out of it by doing a re-base.
It has multiple versions of libraries, because some applications
use the different versions.

# In an administrator terminal

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

WinSxS files are hardlinked into other places in the OS folders.
Hardlinked, means there are two file pointers but only one
set of clusters. "Deleting" one of the file pointers, does not
save a lot of space. That's part of the reason that the file size
issue is as much an accounting issue, as it is anything else. The
OS does not have an effective means of displaying files that
share space. All that we can say with certainty, is the pie
chart properties display of the file system size, it can be
accurate. But the accuracy dipped when Microsoft started
fooling around with $BITMAP. Users will sometimes notice a large
error in the pie chart, that may correct itself on a reboot
and re-evaluation. A long time ago in the past, $BITMAP was
always accurate (when all we had was HDD for storage).
SSDs have forced a tradeoff on "not burning up the SSD"
versus "storage precision".

Paul

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: WinSxS (was: Re: W10's Disk Cleanup (cleanmgr.exe) can't remove all of WU Cleanup.)

On 2025/11/12 22:59:53, Paul wrote:

On Wed, 11/12/2025 3:18 PM, s|b wrote:

[]

2. Want to go crazy? Take a look at the size of C:\Windows\WinSxS.

Mine is 9592 MBytes (according to one scanner) - not huge (though I've
only had the machine since May), though would be nice to get some of
that back.

There generally isn't a lot of excess material in WinSxS.
You can squeeze a bit more out of it by doing a re-base.
It has multiple versions of libraries, because some applications
use the different versions.

# In an administrator terminal

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Is that safe to do?>

WinSxS files are hardlinked into other places in the OS folders.
Hardlinked, means there are two file pointers but only one
set of clusters. "Deleting" one of the file pointers, does not
save a lot of space. That's part of the reason that the file size
issue is as much an accounting issue, as it is anything else. The
OS does not have an effective means of displaying files that
share space. All that we can say with certainty, is the pie
chart properties display of the file system size, it can be

What pie chart display would that be? (I'm using the Steffen Gerlach one.)

accurate. But the accuracy dipped when Microsoft started
fooling around with $BITMAP. Users will sometimes notice a large
error in the pie chart, that may correct itself on a reboot
and re-evaluation. A long time ago in the past, $BITMAP was
always accurate (when all we had was HDD for storage).
SSDs have forced a tradeoff on "not burning up the SSD"
versus "storage precision".

Paul

--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

All that glitters has a high refractive index.

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Thu, 11/13/2025 6:58 AM, J. P. Gilliver wrote:

On 2025/11/12 22:59:53, Paul wrote:

On Wed, 11/12/2025 3:18 PM, s|b wrote:

[]

2. Want to go crazy? Take a look at the size of C:\Windows\WinSxS.

Mine is 9592 MBytes (according to one scanner) - not huge (though I've
only had the machine since May), though would be nice to get some of
that back.

On W11 24H2, my WinSxS reads

Size: 21,124,122,973 bytes
Size on disk: 12,127,719,424 bytes

You can never be too wealthy and have too many... whatsits.

Part of the size diff, is the files that
store their content in the $MFT 1KB slot. Maybe
even some of the directories in there are
also in the $MFT.

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Is that safe to do?>

Golly, I don't know.

The thread here, suggests there is a registry setting that governs
whether anything happens. Who knew ? You could look and see if yours
is switched off or not. Mine matches the picture here.

https://www.elevenforum.com/t/dism-online-cleanup-image-startcomponentcleanup-resetbase-not-working.7774/

DisableResetbase REG_DWORD 0x00000001

It's good of them to tease us like this. I feel "used".

What pie chart display would that be? (I'm using the Steffen Gerlach one.)

Select a disk icon in File Explorer (for This PC) and do Properties on it.
A Pie Chart is displayed with current partition size shown.

I have seen errors of 10-20GB in there, but they will eventually
resolve after the OS "re-computes" $BITMAP from first principles.

We use that disk size information for activity planning, so it
is fairly important that it be accurate. I would hate to throw
out my fluffy cat picture collection in an effort to free up
space, only to discover later (after a re-calc) that there
was lots of space all along. I think I got caught once that
way, when I was just about to do a Repair Install and the
pie chart was telling me I didn't have enough space to do that.

You can take the cluster count information from nfi.exe and
use that as an approximation to disk size. If you want to do a
calculation on the spot. I might have made a script to scan
the nfi output at some point and give me a number (for lack
of a hobby).

You CANNOT calculate the fullness of C: by using the file
size fields of the Everything.exe CSV file listing for the partition.
This is because hardlinked files (everything in WinSxS) get
counted twice. There will be a huge error by summing them all.
That's why the calc has to be based on a cluster level analysis.

So if there was an ntfs.sys file in WinSxS and it was
hardlinked into Drivers folder, there is only one set of
clusters, but an Everything file list would list two files
of identical size, and they are both using the same set of
clusters for their data. Summing those would double-count
the space.

A data disk does not typically have or use hardlinks,
so the space calc there is not as perilous. Most
of your attempted accountancy methods will work then.

Paul

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Subject: Re: WinSxS (was: Re: W10's Disk Cleanup (cleanmgr.exe) can't remove all of WU Cleanup.)

On Thu, 13 Nov 2025 11:58:03 +0000, J. P. Gilliver wrote:

On 2025/11/12 22:59:53, Paul wrote:

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Is that safe to do?>

I don't pretend to understand exactly what it does (besides decrease the
size of Winsxs), but I've run that command several times in the past. I
always make sure I have a backup image first, but I've never needed it.

--
s|b

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2025/11/14 13:56:53, s|b wrote:

On Thu, 13 Nov 2025 11:58:03 +0000, J. P. Gilliver wrote:

On 2025/11/12 22:59:53, Paul wrote:

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Is that safe to do?>

I don't pretend to understand exactly what it does (besides decrease th

e

size of Winsxs), but I've run that command several times in the past. I

always make sure I have a backup image first, but I've never needed it.

I just tried it (admin. cmd):

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

C:\Windows\system32>dism.exe /Online /Cleanup-Image / StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6456



Error: 0x800f0806

The operation could not be completed due to pending operations.

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

C:\Windows\system32>

dism.log is 25,096 KB.



--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

Science isn't about being right every time, or even most of the time. It
is about being more right over time and fixing what it got wrong.
- Scott Adams, 2015-2-2

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

J. P. Gilliver wrote on 11/14/2025 4:42 PM:

On 2025/11/14 13:56:53, s|b wrote:

On Thu, 13 Nov 2025 11:58:03 +0000, J. P. Gilliver wrote:

On 2025/11/12 22:59:53, Paul wrote:

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Is that safe to do?>

I don't pretend to understand exactly what it does (besides decrease the
size of Winsxs), but I've run that command several times in the past. I
always make sure I have a backup image first, but I've never needed it.

I just tried it (admin. cmd):

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

C:\Windows\system32>dism.exe /Online /Cleanup-Image / StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6456



Error: 0x800f0806

The operation could not be completed due to pending operations.

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

C:\Windows\system32>

dism.log is 25,096 KB.

I've run it many times, without any problems. However, you should be
aware that on recent Windows versions, the /reset base option really
doesn't do much. It can simply compress the data but still leave it there.

If you don't use the /ResetBase option, does it work OK?

If you're having lots of problems, sometimes the best idea is to
download the windows ISO and do a repair/upgrade install over the
current image. You can keep all your programs, data, etc. It simply
writes the windows system anew.

Good luck.


--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2025/11/14 23:23:45, Hank Rogers wrote:

J. P. Gilliver wrote on 11/14/2025 4:42 PM:

[]

I just tried it (admin. cmd):

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

C:\Windows\system32>dism.exe /Online /Cleanup-Image /
StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6456



Error: 0x800f0806

The operation could not be completed due to pending operations.

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

C:\Windows\system32>

dism.log is 25,096 KB.

I've run it many times, without any problems. However, you should be
aware that on recent Windows versions, the /reset base option really
doesn't do much. It can simply compress the data but still leave it th

ere.

If you don't use the /ResetBase option, does it work OK?

C:\Windows\system32>dism.exe /Online /Cleanup-Image /StartComponentClean
up

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6456



Error: 0x800f0806

The operation could not be completed due to pending operations.

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

C:\Windows\system32>

If you're having lots of problems, sometimes the best idea is to
download the windows ISO and do a repair/upgrade install over the
current image. You can keep all your programs, data, etc. It simply
writes the windows system anew.

Good luck.

Not having any problems at all: just tried it as there was some
suggestion earlier in this thread that it might reduce the size of
WinSxS, though perhaps not by much. (Still 10.7 GBytes. Not _that_ large.
)


--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

What?s the point of having laurels if you can?t rest on t
hem?
- Tom Lehrer

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2025-11-14 22:42, J. P. Gilliver wrote:

I just tried it (admin. cmd):

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

C:\Windows\system32>dism.exe /Online /Cleanup-Image / StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6456



Error: 0x800f0806

The operation could not be completed due to pending operations.

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

C:\Windows\system32>

dism.log is 25,096 KB.

This bit ...

Error: 0x800f0806

The operation could not be completed due to pending operations.

... reads to me like there is a reboot pending after an update.

--

Fake news kills!

I may be contacted via the contact address given on my website: www.macfh.co.uk


--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Fri, 11/14/2025 5:42 PM, J. P. Gilliver wrote:

On 2025/11/14 13:56:53, s|b wrote:

On Thu, 13 Nov 2025 11:58:03 +0000, J. P. Gilliver wrote:

On 2025/11/12 22:59:53, Paul wrote:

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Is that safe to do?>

I don't pretend to understand exactly what it does (besides decrease the
size of Winsxs), but I've run that command several times in the past. I
always make sure I have a backup image first, but I've never needed it.

I just tried it (admin. cmd):

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

C:\Windows\system32>dism.exe /Online /Cleanup-Image / StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6456



Error: 0x800f0806

The operation could not be completed due to pending operations.

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

C:\Windows\system32>

dism.log is 25,096 KB.

https://www.reddit.com/r/Windows10/comments/m2g1er/dism_startcomponentcleanup_not_working/

"Is a pending.xml file in the folder C:\Windows\WinSxS ?"

Weird if true.

Paul

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2025/11/15 3:18:15, Paul wrote:

On Fri, 11/14/2025 5:42 PM, J. P. Gilliver wrote:

On 2025/11/14 13:56:53, s|b wrote:

On Thu, 13 Nov 2025 11:58:03 +0000, J. P. Gilliver wrote:

On 2025/11/12 22:59:53, Paul wrote:

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Is that safe to do?>

I don't pretend to understand exactly what it does (besides decrease

the

size of Winsxs), but I've run that command several times in the past.

I

always make sure I have a backup image first, but I've never needed i

t.

I just tried it (admin. cmd):

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

C:\Windows\system32>dism.exe /Online /Cleanup-Image /
StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6456



Error: 0x800f0806

The operation could not be completed due to pending operations.

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

C:\Windows\system32>

dism.log is 25,096 KB.

https://www.reddit.com/r/Windows10/comments/m2g1er/dism_startcomponentc

leanup_not_working/

"Is a pending.xml file in the folder C:\Windows\WinSxS ?"

Weird if true.

Paul

According to Everything, I have no pending.xml files anywhere.


--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

"Going to church doesn't make you a Christian anymore than going to a
garage makes you a car." - Laurence J. Peter

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Sat, 11/15/2025 7:18 AM, J. P. Gilliver wrote:

On 2025/11/15 3:18:15, Paul wrote:

On Fri, 11/14/2025 5:42 PM, J. P. Gilliver wrote:

On 2025/11/14 13:56:53, s|b wrote:

On Thu, 13 Nov 2025 11:58:03 +0000, J. P. Gilliver wrote:

On 2025/11/12 22:59:53, Paul wrote:

dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase

Is that safe to do?>

I don't pretend to understand exactly what it does (besides decrease the >>>> size of Winsxs), but I've run that command several times in the past. I >>>> always make sure I have a backup image first, but I've never needed it. >>>>

I just tried it (admin. cmd):

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

C:\Windows\system32>dism.exe /Online /Cleanup-Image /
StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6456



Error: 0x800f0806

The operation could not be completed due to pending operations.

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

C:\Windows\system32>

dism.log is 25,096 KB.

https://www.reddit.com/r/Windows10/comments/m2g1er/dism_startcomponentcleanup_not_working/

"Is a pending.xml file in the folder C:\Windows\WinSxS ?"

Weird if true.

Paul

According to Everything, I have no pending.xml files anywhere.

If I run your error message again, I find this as a suggestion.
This means you're in the middle of an update, and this command
is supposed to back you out of unfinished updates. Normally, the situation
for the usage of this, would be the second form. If there is nothing
to revert, the command returns quickly and shares that info with you.

The reason for doing an operation like this "offline" is the system no longer boots.
The Windows Update broke it, the update is half done, and by doing it in the offline state, you are preparing to reboot and finding an update
unfinished now because it was rolled back.

https://superuser.com/questions/1599312/dism-exe-resetbase-error-on-windows-server-2016

dism /online /Cleanup-Image /RevertPendingActions # This is when the OS is online

DISM /Image:C:\ /Cleanup-Image /RevertPendingActions # (This version, not in the thread, is for doing
it from a Win10 installer DVD, Troubleshooting,
then Command Prompt window.)

A question would be, where are the "PendingActions" kept that it "Reverts" ?

Still no closer to finding it.

https://www.bleepingcomputer.com/forums/t/570797/im-stuck-in-an-updatesystem-repair-loop/page-3

Part of reboot time activity, is checking for "PendMoves", which for a Windows Update
are a series of file moves done as the system is about to shut down. The C: is closer
to being quiet at that time, making file movements less intrusive to continued operation.
While some of this might happen after the reboot, I don't know the details of the
"30%+" operations done then. While a software could notice that there are items in
PendMoves, I don't know if that has anything to do with a DISM not finishing properly.

Paul

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On Fri, 14 Nov 2025 22:42:40 +0000, J. P. Gilliver wrote:

I just tried it (admin. cmd):

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

C:\Windows\system32>dism.exe /Online /Cleanup-Image / StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6456



Error: 0x800f0806

The operation could not be completed due to pending operations.

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

C:\Windows\system32>

dism.log is 25,096 KB.

I've had no problems in the past. I just tried it again - on W11 - and
it still works for me.

--
s|b

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2025/11/16 18:51:6, s|b wrote:

On Fri, 14 Nov 2025 22:42:40 +0000, J. P. Gilliver wrote:

I just tried it (admin. cmd):

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

C:\Windows\system32>dism.exe /Online /Cleanup-Image /
StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6456



Error: 0x800f0806

The operation could not be completed due to pending operations.

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

C:\Windows\system32>

dism.log is 25,096 KB.

I've had no problems in the past. I just tried it again - on W11 - and
it still works for me.

Trying again (I think I've done a restart of some sort since last time). Looking (with scanner) before I do, my WinSxS is "only" 9241 MBytes (it
was over 10 last time I did). The command seems to be doing something
this time:

C:\Windows\system32>dism.exe /Online /Cleanup-Image
/StartComponentCleanup /ResetBase

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.6575

[===== 10.0% ]

It got to 10% roughly immediately, and has been stuck there for some
minutes now.
I tried a Ctrl-C; nothing seemed to happen, but next time I looked it
was showing

[===== 10.0% ]


Error: 1223

Operation was incomplete because of a cancel request.

Trying again: this time shot to 19.0% immediately, then slow - but has
moved to 20% ... now 100%. Long pause, then

[==========================100.0%==========================]
The operation completed successfully.

Re-scanning: WinSxS now seems to be 8484 MBytes. So not a huge reduction
(from 9241), but I'd say worth having; thanks.

--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

"OLTION'S COMPLETE, UNABRIDGED HISTORY OF THE UNIVERSE
Bang! ...crumple." - Jery Oltion

--- PyGate Linux v1.5
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)