What do the different tasks of the Image Cleanup do?

[AlterNate37]

Hi,

coming from MSMG Toolkit, where there only are two options for cleanup, a normal one and a full reset one, I as a tech-affine yet not tech-savvy person feel confused by the many choices in the "choose a task" drop-list of the Image Cleanup.
I "searched" the Help Topics (which btw lack a ctrl+f ability to be searched) and I've also searched the Discussions here, but found nothing.
Could someone explain them?

I simply want to cleanup the image before creating the ISO.
Tbh I am not even sure what happens if an image doesn't get a cleanup, if it's just a matter of the ISO (and then the bootable USB) being bigger, or if all that extra and not needed stuff will be also brought into the OS, or why one does a cleanup in the first place.
But I've read that I'm supposed to do it and I'd like to know more about how to do it with the options given by DISMTools.

Thanks :)

[CodingWonders]

I simply want to cleanup the image before creating the ISO.

This task is it:

Tbh I am not even sure what happens if an image doesn't get a cleanup, if it's just a matter of the ISO (and then the bootable USB) being bigger, or if all that extra and not needed stuff will be also brought into the OS, or why one does a cleanup in the first place.

Your image will work correctly if it isn't cleaned up. Cleaning up the image (in this context) refers to cleaning up the component store and performing some maintenance on it. You should do this if you have installed updates. Debloating the Windows image by removing apps most likely won't require this action.

But I've read that I'm supposed to do it and I'd like to know more about how to do it with the options given by DISMTools.

The screenshot above is the answer.

You can find more info here: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-operating-system-package-servicing-command-line-options?view=windows-11#cleanup-image

[AlterNate37]

Thanks, I didn't install updates but I did integrate drivers.
Does the component store cleanup have relevance in this case too? Or is it really only with updates?

In case it is only with updates, does it mean that no change whatsoever would be made to the image if I run this cleanup?
I wonder why with DISMTools the ISO is 6.8GB while with MSMG Toolkit is 5.2GB.
I removed the same packages and apps.
The only difference besides the lack of cleanup here, is that here the drivers have been added from the online installation, because adding folders didn't work (I'll open an issue about it later). While in MSMG I simply copy paste the downloaded drivers which I want into the project's drivers folder.
But, 1.6GB difference?

Oh, btw, I notice now that in your screenshot you have the reset database option selected.
Is it the same as MSMG Toolkit's "full reset" option in the tweaks?
I've read lot of controversial stuff about that.
Why do you select it? Is it better to avoid conflict with Windows Update or something like that?

[CodingWonders]

Does the component store cleanup have relevance in this case too? Or is it really only with updates?

I think that it is only really applicable to updates, so nothing will happen.

Is it the same as MSMG Toolkit's "full reset" option in the tweaks?
I've read lot of controversial stuff about that.

I haven't dealt with MSMG Toolkit's feature set, so I can't tell.

Why do you select it? Is it better to avoid conflict with Windows Update or something like that?

It can help further reduce the size because all updates that you may have installed become permanent. The link I provided talks more about this command.

While in MSMG I simply copy paste the downloaded drivers which I want into the project's drivers folder.
But, 1.6GB difference?

Drivers can increase the size of the image when you install them.

[AlterNate37]

I haven't dealt with MSMG Toolkit's feature set, so I can't tell.

Oh, as you mention it in your description of DISMTools, I thought you were familiar with it.
I've found this:

So, yeah, it's the same.

I don't remember why some people in the MSMG thread in MyDigitalLife find resetbase problematic. I can't ask them, because I didn't receive the confirmation email and so I can't post. That's also why I write here and not in your thread there.

I've tried to investigate between DuckDuckGo and Copilot, but it's a bit confusing.
On one hand, Copilot says that resetbase "might remove components that are still needed by certain applications or system processes".
And that this could also potentially lead to some future updates not installing properly.
On the other hand, in tenforums I read "When you use /resetbase switch, Dism will clean up Windows update components that deny you to uninstall those installed Windows updates.", which seems to hint that actually resetbase might solve and not cause update issues?

Also, in the link which you provided I read that "StartComponentCleanup cleans up the superseded components and reduces the size of the component store".
So, it already removes stuff.
I guess that what Copilot meant is that resetbase removes even more stuff and so potentially also things which "in theory" aren't needed but might still be needed (because it's Windows, you know...)?

Within the scope of this thread and for future references, can you explain your understanding of the difference between what kind and amount of superseeded components does StartComponentCleanup remove without and with the resetbase option?
Why removing anyway? What does one achieve by doing that? A faster installation? Or a smoother OS?
Isn't there an automatic filter like with drivers, which during a clean install would recognize the needed components and install only these?

Could you also share your opinion and experience about if resetbase can increase or decrease the chances of having no issues 1. with the OS in general, and 2. with installation of future updates?

Thanks :)