Does enabling DISM ResetBase feature still create issues?

I

InnerBrat

Member
Messages
30
Reaction score
0
Hi,

I've searched this forum and a bit online and found that the reason why this is disabled by default is that it can supposedly break "reset my pc".
But someone says it was more about a specific build of Win10.
The last info that I find here is from 2020, so I wonder what's the situation now and what benefit or issue there would be activating it.
Thanks!
 
DISM ResetBase is considered safe for currently supported W10/11 releases, there were some issues on obsolete W10 versions (which no one should be really using anyway). Quoting myself from another post:

DISM Compatible & DISM ResetBase cleanup both remove superseded (patched) component files, shrinking the image.​
​
W8 and later Windows releases allow ResetBase which "collapses" the updates so you cannot uninstall them. The last version of a component permanently becomes the component's new minimum version (reset the base).​
​
When you have a live system, the option to roll back a bad update is very important.​
When doing a clean install, there isn't a real need to roll back since you would replace failed images with a newer one.​
​
Windows will continue to service (update) both types of cleaned images.​
 
Yes I had read that. But I could not be sure if it was talking of the so called "true" resetbase which is only activated when this setting is enabled.
Which btw, do I understand correctly that when this setting is disabled the /resetbase command still works but Windows performs more of a compression than of a "true" resetbase?
Or is it rather so, that when this setting is disabled, the resetbase command doesn't work at all?
 
NTLite ResetBase is basically the same as DISM /resetbase. Custom cleanup is a NTLite-only feature which doesn't guarantee backwards compatibility with either DISM mode.

You're not obligated to use DISM cleanup when preparing an image. Normally you would use DISM cleanup on an offline image, since you don't care about rolling back. When you're using NTLite on a live system to install updates, you might not want to run DISM cleanup as to allow removing an update without reinstalling Windows.

DISM cleanup isn't "compression", it's removing the superseded versions of a component. Because Windows is designed to have cumulative updates, every new version of a component is a complete replacement for its predecessor.
 
garlin said:
NTLite ResetBase is basically the same as DISM /resetbase.
Click to expand...
We might be talking of different things.
I'm working on an offline image for a clean install.
I refer to what I suppose it's a setting that affects how resetbase will work in windows after I will do the clean install.
This setting is in the category "configure", tab "settings", group "system", between "disk quota" and "display the lock screen".
It seems to me that you refer to what NTLite would be doing at the moment of applying the changes made to an image?

garlin said:
DISM cleanup isn't "compression", it's removing the superseded versions of a component.
Click to expand...
I refer to THIS post in this forum.
I have no idea what they're talking about but I thought that it was related to this setting, and that therefore if I don't enable this setting Windows will not perform a real resetbase (and I mean windows, after the clean install. Not NTLite).
 
You must log in or register to reply here.
Back
Top