Possible to compare my reference (state) against a live installation?

Hvergelmir

Hvergelmir

New Member
Hi,

say I create a preset, disabling or removing certain components, features ... whatnot ... and then I install the result. Now let's say that I have run this for some time. Several of the descriptions inside NTLite indicate that Windows 10 will end up "repairing" itself through cumulative updates and that this may also restore components I previously disabled.

Is there a way for me to compare my reference state of the installation against the live installation that has now been in use for some time?

Thanks.
 
Hvergelmir said:
Is there a way for me to compare my reference state of the installation against the live installation that has now been in use for some time?
Click to expand...

If you have updated Windows 10 and want to know if there are returned componentsalready removed, yes.

Open NTLite and load the Live install.
Open a second instance of NTLite and load the source or extract the ISO used for installation.
Compare "Window to Window" or use only one instance and select all components and save the preset, do the same on both and compare the presets.
 
Kasual said:
Open NTLite and load the Live install.
Open a second instance of NTLite and load the source or extract the ISO used for installation.
Compare "Window to Window" or use only one instance and select all components and save the preset, do the same on both and compare the presets.
Click to expand...
Ugh, sounds tedious. Is that the only way? I currently have the problem already that I cannot limit the view to items that are set to non-standard values (i.e. have been customized by me).
 
http://www.blueproject.ro/systracer/

I use that to double check if any CU changes something or not. Just take a snapshot of all files + registry + apps before the CU (or even before doing a host refresh or even a in-place upgrade to a new Windows version in order to see if there are new services, etc.) and after the CU. Then you can easily view all changes to the filesystem, the registry, but also for services / drivers and their current state and if it changed to what it was before and if there are new ones etc. Very easy.
 
lvau said:
http://www.blueproject.ro/systracer/

I use that to double check if any CU changes something or not. Just take a snapshot of all files + registry + apps before the CU (or even before doing a host refresh or even a in-place upgrade to a new Windows version in order to see if there are new services, etc.) and after the CU. Then you can easily view all changes to the filesystem, the registry, but also for services / drivers and their current state and if it changed to what it was before and if there are new ones etc. Very easy.
Click to expand...
Hi, this looks like an interesting tool indeed, going by the screenshots. Alas, no can do. This is a tool that isn't open source but isn't coming with a code-signed installer. Won't run on my system however good it may be. 2019 and no code-signing is a no go for anything that I can't build from scratch on my own ....
 
To be honest, I give a damn about code signing or any pseudo-Windows-security. Just don´t use it then.
 
lvau said:
To be honest, I give a damn about code signing or any pseudo-Windows-security. Just don´t use it then.
Click to expand...
Wow, don't take my response personally. I mean I get it: YMMV. And while one can argue about the CA system and centralized trust and all that stuff, code-signing surely adds to the overall safety, even if it's not a sufficient protection on its own. No offense meant.
 
Another easy solution is to load the live install and your preset.
Go see components greyed out and see what subcomponents tickoffs' you made in your preset.
On the Apply section you can have the overview and also see if any features, settings or services are changed.
 
You must log in or register to reply here.
Back
Top