.NET 3.5 Addition to Virgin Image - Error 0x800F0806 '[2054]: DISM update cleanup skipped due to pending changes on the image.

[bseklecki_ge]

Interesting message when I perform a simple DotNet3.5 addition/integration (Cab File Method) into a virgin Win10 Ent IOT LTSC 2021 image (Direct download from MicrosoftOEM.com)

So the question is: Is it possible that the RTM images from Microsoft have pending DISM changes that require the first step to be DISM cleanup task (alone) ?

This is coming from MicrosoftOEM.com [X22-81260 Win 10 IoT Enterprise LTSC 2021 21H2 x64 English OPK]

~BAS

Error 0x800F0806 '[2054]: DISM update cleanup skipped due to pending changes on the image. Next time when starting from an unpatched image, make sure to run the cleanup before integrating certain updates like .NET 3.5, the 'enablement package' or configuring features. If using NTLite to integrate, configure and cleanup in a single session, it will sequence these operations automatically.': DISM Clean update backup

 

[garlin]

Isn't .NET integration the pending change? This is the same as enabling the .NET FOD packages (which blocks cleanup).

 

[bseklecki_ge]

I'm seeing this on other platforms/scenarios.

Possibly related question:

On v1607/Server2016, we use NTLite to integrate KB4486129 [DotNet4.8 Feature pack]

However, if we also try to install the latest DotNet4.8 ServicePack [KB5020873] (December 2022), it integrates during the NTLite apply process, but rolls back immediately during OOBE.

Is it possible to to accomplish this in one-pass?

 

[bseklecki_ge]

Would it be possible to modify NTLite behavior so that this popup error is not blocking the continuation of the tasks/process in the background?