DISM - Error 0x800f0806 [2054], Windows 10 1803

F

fishingfish

Member
I integrated in windows 10 x64 1803 latests updates from whdownloader + intel microcode + netfx 4 + 3.5, then selected "dism" in clean update backup (and nothing else, no removals, not anything) and i receive this error message. I tried to start from fresh, integrating them again but I keep getting it. I dont know what it is.

I dont get an error if I select "compatible" in clean update backup.
 
nuhi said:
It's a Windows feature, message will state in the future something like "pending changes on this image, DISM cleanup unsupported".

Will work on auto-inserting DISM cleanup between updates that support it and those that lock it, like Feature Upgrade CAB from 1903->1909 and 2004->2009 - after those or feature config cleanup is not possible, that message.
Click to expand...

Never heard of something like that message and when will it show up? So, is it a Windows problem and I'd also have this message if not using NTLite?

Also, in the future after choosing one of the 2 NTLite DISM settings one won't have any message regarding it when creating the image? Also, will one of these settings break any component?
 
Last edited:
Windows 10 User said:
Never heard of something like that message and when will it show up? So, is it a Windows problem and I'd also have this message if not using NTLite?

Also, in the future after choosing one of the 3 NTLite DISM settings one won't have any message regarding it when creating the image? Also, will one of these settings break any component?
Click to expand...
The error 2054 is that message, just will write it in human form.

Correct, it's a DISM limitation to not support cleanup after certain updates and feature config, basically certain pending changes.

Custom cleanup even now doesn't have that message, but that one isn't DISM, it's NTLite's custom engine, so I cannot guarantee 100% future-proofing as Microsoft keeps changing the servicing stack almost each month.
Been some time since any issues, just being honest/paranoid.
 
nuhi said:
The error 2054 is that message, just will write it in human form.

Correct, it's a DISM limitation to not support cleanup after certain updates and feature config, basically certain pending changes.

Custom cleanup even now doesn't have that message, but that one isn't DISM, it's NTLite's custom engine, so I cannot guarantee 100% future-proofing as Microsoft keeps changing the servicing stack almost each month.
Been some time since any issues, just being honest/paranoid.
Click to expand...

Ok, so just go be sure, it isn't NTLite's fault, there's no way to stop having this error prompt (even in the future, I'd still have it if I did this manually (so, not in NTLite) and I may ignore it because Windows will still do it's supposed to do after choosing one of the 2 settings?
 
Last edited:
To my experience (have not read the whole thread yet) but this error occurs most when integrating any .Net - since july updates include .Net 4.8 it can create that issue. But you can use dism manually of course to integrate updates and not use NTLite for that part - but then still you would run into some issues - for example dism resetbase to clean up will give an error and without .Net updates it will not function well.
I hear so much: don't bother to integrate updates, just run latest CU after installation - but I don't agree, sometimes it is needed to integrate them.
But M$ is doing a good job to make life hard for us :)

nuhi: we communicated about this too, maybe you can wave your magic fingers and help us? I know, M$ makes this time consuming, maybe it's not worth all that time.
 
Last edited:
Brutser said:
To my experience (have not read the whole thread yet) but this error occurs most when integrating any .Net - since july updates include .Net 4.8 it can create that issue. But you can use dism manually of course to integrate updates and not use NTLite for that part - but then still you would run into some issues - for example dism resetbase to clean up will give an error and without .Net updates it will not function well.
I hear so much: don't bother to integrate updates, just run latest CU after installation - but I don't agree, sometimes it is needed to integrate them.
But M$ is doing a good job to make life hard for us :)
Click to expand...

So, .NET 4.8 update already includes .NET itself? Anyway, I've been having this problem before the .NET july updates.
 
I don't say this is causing the issue with NTLite, only nuhi can answer that - All I know from manually using DISM, is that .net integration needs to be handled separately or it can cause issues with dism.
 
It's not related to NTLite.
What I'm interested from the next version onwards is to get reports of any similar situation which locks that cleanup to automate all, to be cleaned as much as possible in a single sequence.
 
nuhi said:
It's not related to NTLite.
What I'm interested from the next version onwards is to get reports of any similar situation which locks that cleanup to automate all, to be cleaned as much as possible in a single sequence.
Click to expand...

So, if we did that on Windows we'd also have that error prompt? And we won't have that error prompt interrupting the process in the next NTLite version?
 
Last edited:
Windows 10 User said:
So, if we did that on Windows we'd also have that prompt? And we won't have that prompt interrupting the process in the next NTLite version?
Click to expand...
On Windows as in after install? Once the pending operations are done, after install, then DISM is again unlocked.

Goal is to automatically pause the integration, insert the cleanup, then continue the integration and feature config that locks it in the next version, yes - on the beta first.
 
nuhi said:
On Windows as in after install? Once the pending operations are done, after install, then DISM is again unlocked.

Goal is to automatically pause the integration, insert the cleanup, then continue the integration and feature config that locks it in the next version, yes - on the beta first.
Click to expand...

Yes, I was asking if one would have that error prompt after doing it (if possible) after installing Windows.
 
Last edited:
First version supporting this is released in build 7580.
Let me know if you guys still get the DISM cleanup error and provide a preset with the update list, should be simple enough to adapt going forward.
For Win8.1 it is known that some updates cause this, could not squeeze that in before the release, feedback is welcome to speed that up as well.

Thanks.
 
nuhi said:
First version supporting this is released in build 7580.
Let me know if you guys still get the DISM cleanup error and provide a preset with the update list, should be simple enough to adapt going forward.
For Win8.1 it is known that some updates cause this, could not squeeze that in before the release, feedback is welcome to speed that up as well.

Thanks.
Click to expand...

Thanks. Just to be sure, even if we don't have that error may we have prlblems after installing Windows like being unable to install updates? Which one of the 3 NTLite DISM settings shouls we choose to have less problems? Maybe I should keep choosing the "None" setting.

EDIT: Two PCs are messed up and are unable to update (for instance). Since I can't to clean installs on them (they're not mine) should I run the setup.exe from an image NTLite created or use this image via NTLite's host refresh feature?
 
Last edited:
Windows 10 User said:
Thanks. Just to be sure, even if we don't have that error may we priblems after installing Windows like being unable to install updates? Which one of the 3 NTLite DISM settings shouls we choose to have less problems? Maybe I should keep choosing the "None" setting.

EDIT: Two PCs are messed up and are unable to update (for instance). Since I can't to clean installs on them (they're not mine) should I run the setup.exe from an image NTLite created or use this image via NTLite's host refresh feature?
Click to expand...
DISM compatible should be fine.

Yes, setup.exe or NTLite' host refresh is the same thing, just easier - that is a nice way to refresh the system if there are any issues.
Just make sure it offers you Keep files and applications option.
 
nuhi said:
DISM compatible should be fine.

Yes, setup.exe or NTLite' host refresh is the same thing, just easier - that is a nice way to refresh the system if there are any issues.
Just make sure it offers you Keep files and applications option.
Click to expand...

Thanks. Why do you say host refresh is easier and how can it offer to keep files and applications? Only setup.exe does that, I think.
 
Last edited:
I think he says that because the NTLite Host Refresh is basically running setup.exe, but with its own custom GUI.

Whatever, I have used NTLite's Host Refresh to update 1903 to 1909. It offered to keep my files and applications. And it did.
 
nuhi said:
First version supporting this is released in build 7580.
Let me know if you guys still get the DISM cleanup error and provide a preset with the update list, should be simple enough to adapt going forward.
For Win8.1 it is known that some updates cause this, could not squeeze that in before the release, feedback is welcome to speed that up as well.

Thanks.
Click to expand...

Nuhi, now I have a different error prompt (on Windows 10 Enterprise 19041.1 x64 pt-pt) after choosing the DISM (Compatible) setting. It states: "DISM update cleanup skipped due to pending changes on the image. Next time make sure to run the cleanup before integrating certain updates like the 'enablement package' or configuring features.".

nuhi said:
DISM compatible should be fine.

Yes, setup.exe or NTLite' host refresh is the same thing, just easier - that is a nice way to refresh the system if there are any issues.
Just make sure it offers you Keep files and applications option.
Click to expand...

Thanks but could you tell why is it the same thing but easier? Is it worth running setup.exe or using NTLite's host refresh setting from/with a new image if a new NTLite version that came out is able to remove a component the previous versions couldn't or should I only do that when having major issues on Windows?

Also, what problems may I have if I remove the Windows Firewall (which is now possible on a deployed image)?

pmikep said:
I think he says that because the NTLite Host Refresh is basically running setup.exe, but with its own custom GUI.

Whatever, I have used NTLite's Host Refresh to update 1903 to 1909. It offered to keep my files and applications. And it did.
Click to expand...

I didn't know it may do that but does it have the latest DU like an ISO may have if extracting it to its source folder? Anyway, after doing an in-place upgrade installs I still have problems and even new ones. What should I do in this case (I can't do clean installs)? IIRC, setup.exe asks me if I want to download updates before doing an in-place upgrade (this was before I even knew about DU so maybe after extracting it to the sources folder I won't be asked this) install so is it a DU? If I agree the install fails many times, but it doesn't if I disagree (and if the latter the install takes less time because I won't lose time downloading what I think is a DU). Why is this?
 

Attachments

  • Captura de Ecrã (15).png
    Captura de Ecrã (15).png
    82.8 KB
  • preset.xml
    31.2 KB
Last edited:
I have never removed the Windows Firewall. But I know that when I disabled its service in Win8.1, I could not share printers in my home network.
 
You must log in or register to reply here.
Back
Top