DISM Update cleanup failing for me (Error 0x800F0806)

P

pmikep

Active Member
Messages
891
Reaction score
153
NTLite v 2025.3.10345

I have a working Lite'd Win 8 U3 wim, that was patched with updates early on in the wim build process.

I just tried cleaning it using DISM Compatible.

Two problems.

First, it errored out, claiming "pending changes." See the photograph of my computer screen for the message.

View attachment 14013

Second, the Error Message text does not wrap around in the box. Nor can slide the side of the window. The only thing that I can change is the diagonal on the window. Which still does not cause the text to wrap.

I had to hold my mouse cursor over the text and then it changed into a ToolTip sort of box.

When I've had DISM errors in the past, it's been because I had Comodo's HIPS enabled, which blocked DISM from running. But this error is with HIPS disabled.
 
Last edited:
Usually when DISM refuses to clean due to pending changes, it's something like integrated .NET 3.5 or features configuration.
Then Windows wants to deploy first to process the pending changes.

If you have a preset demonstrating this, starting from an original ISO with NTLite also integrating updates to it so I can replicate from the ground up.
NTLite also sorts these operations properly, so if you select all at once, it should be cleaned as much as possible.
 
Thanks for the quick reply.

Yes, what you said above is the message that I saw in NTLite.

So, if I understand correctly, when you say that "Windows wants to dsploy first to process the pending changes," that means that NTLite might not be able to do a cleanup here before Windows is installed? (Which means that one has to run NTLite on the now live image.)

Here's the Preset of only updates to a fresh iso.

But, to be fair, I did not choose ALL the updates that NTLite offered. Perhaps that confuses NTLite?
 

Attachments

When .NET packages are integrated into an image, they stage pending operations which are designed to be run on the live system, and require a subsequent reboot (whenever it happens) to finish. As such, they block cleanup until the pending operation has cleared.

One solution is to install all updates, except for the .NET packages, and perform a DISM cleanup. After the cleanup is done, reload the image and apply the .NET updates. The image will have pending operations, but you've cleaned most of the non-pending backups.

After Windows has installed, and rebooted a few times, you can manually run a DISM cleanup or use a licensed copy of NTLite on the live host to do the same.
 
I find myself again chasing all the never ending Rabbit Holes in 'Lite'ing, where, just as one thinks one is finished, there is always just one more thing to do.

So I suppose I will start again and patch the original iso with all but .NET packages and clean that wim using NTLite. Then I can append Presets to get to the final stage and use Windows' Disk Clean to clean up the .NET leftovers.

As it was, I ended up using Disk Clean from inside installed Windows to clean up the drive. (Which took almost an hour to remove about 4 GB.)
 
It's mandatory to clean up Windows every time after an update.
After a RemoveReinstalls or run a previous preset over a live updated install - what Disk Clean do is basically just a cmd with:
@Echo off
Dism /Online /Cleanup-Image /AnalyzeComponentStore
Pause
Dism /online /Cleanup-Image /StartComponentCleanup
Pause

Exit
Click to expand...
Remember to turn off Windows Security so first line cmd reaches 100% to get to the bottom of cleanup.
Everything % less, restart and try again.
 
Well everyone, I started again with a fresh Win8.1 Bing iso. I selected most patches older than 11/ 2022, removed .NET related, and also omitted the latest cummulative update. I set NTLite to clean via DISM.

It still fails to clean with a similar (if not the exact - I didn't pay attention) message as in my first post at the top.

(Now using the latest version of NTLite, v2025.03.10349.)
 

Attachments

I saw, in the Preset, what francis11 was telling me. That NTLIte is simply calling the Windows DISM command.

So, apparently, this is a Windows problem of some sort.

Either DISM changed in my Win10 Host via updates, or perhaps some Win8 update is triggering the failure. Or both.

Whatever, apparently not a NTLite problem proper.
 
francis11 said:
It's mandatory to clean up Windows every time after an update.
After a RemoveReinstalls or run a previous preset over a live updated install - what Disk Clean do is basically just a cmd with:

Remember to turn off Windows Security so first line cmd reaches 100% to get to the bottom of cleanup.
Everything % less, restart and try again.
Click to expand...
That would explain why I have problems with running dism (no resetbase). Before even resetbase wasn't a problem on my system.
The problems begann with first update in january für 24h2.

Even now - I first tryed safe mode it tops on 97.x percent and now it stops at 70%. I'm seeing reinstall Windows for the next patch...

Tried /restore health and sfc scannow. The error won't disappear. BUT after I thaught I bricked WinSx with dism once more I gave /resetbase a chance and the process runs through to 100% but it was very very fast. Hope this wasn't just an optical error.

I'm running 26100.3467
 

Attachments

Last edited:
Try pay attention to the order commands are executed when using NTL.
When run a preset with updates always only integrate updates first and only - exactly same way Windows do monthly.
After reload updated image - and then run removals without reset (Dism Compatible) - coz it at this time don't no what to reset as updated Components is'nt removed yet.
Reload 3. time and manually do the Dism Compatible reset in last run.
But actually doing it with cmd lines supposed after install will reduce install more.
Thank you.
 
Last edited:
Unlike Windows 10 1607 and later, most updates will trigger offline pending status for Windows 8.1 / 7

you need to install the image in Audit mode, run cleanup, sysprep and capture new install.wim
 
You must log in or register to reply here.
Back
Top