How can I use Win 10 LTSC 21H2 as starting point for creation of a custom Win 10 Pro 22H2?

N

Nokturnal

New Member
Messages
3
Reaction score
0
Hello dear dev team and people here,

I'm having the following case here:
1. I would like to use Win 10 LTSC 21H2 as starting point in the customization process of Win 10 Pro 22H2,
because it's the cleanest Windows 10 version released by Microsoft itself and untouched by anyone else.
2. I'm aware that I can use the "Preset > Save > Extract current image state" in order to export the LTSC's
image state in XML file as a Preset.
3. The problem occurs when the Preset is loaded over the Win 10 Pro 22H2 version...
- it doesn't uncheck everything which isn't present/available in the LTSC version.
Here is an example screenshot of what is available in the LTSC 21H2 version:
View attachment 10286

Here is the result after the Loading of the extracted LTSC Preset:

View attachment 10287

View attachment 10288

Just a very few things are affected by the Preset and most of the unwanted apps and features are still there.
It's very possible that I'm doing something wrong during the Preset creation?!
In case I'm doing it the right way, I would love to see an option, that will allow me to uncheck everything that doesn't match Preset file, in NTLite, while
loading it. The goal is to end-up with Win 10 Pro 22H2 as clean as Win 10 Enterprise LTSC 21H2 as starting point for further customization. :)
Currently I can't manage to create such a Preset file, or what I'm trying to do isn't still possible in NTLite.
I would be very thankful if someone of you could give a hint how to make it possible. :)

Best wishes,
Nokturnal

P.S: The Preset file is attached if someone would like to conduct any tests.
 

Attachments

Preset -> Extract current image state appears to be broken, in regards to correctly reporting all Apps on the image. I imagine it's a bug.

What you're thinking about (overlaying two different editions) used to work, but we'll have to wait for NTLite to get fixed.
 
garlin said:
Preset -> Extract current image state appears to be broken, in regards to correctly reporting all Apps on the image. I imagine it's a bug.

What you're thinking about (overlaying two different editions) used to work, but we'll have to wait for NTLite to get fixed.
Click to expand...
Hi garlin,
Thank you very much for your reply!
I have tried Preset > Save > Extract current image state function by exporting the image state of ReviOS 10(which is an edited Windows 10 Pro version, while Windows 10 LTSC is an Enterprise). When the ReviOS Preset is loaded over the original Win 10 22H2 Pro image, everything looks as it should.
I'm going to attach the ReviOS Preset, too, for further investigation from the team. Both XML files, attached by me, are created with the very same NTLite version.
I have noticed that there are a serious amount of differences in the both Enterprise LTSC and ReviOS XML files. No matter that the many apps and features were removed from ReviOS, NTLite was able to correctly detect the changes made during the ReviOS image creation process. Most probably NTLite was used for this purpose, as it's the most powerful tool for Windows image customization.
On the other side Windows 10 Enterprise LTSC isn't a modified version of Win 10 Pro, it's just different one which never had most the apps, bloatware and features available in Windows 10 Pro.
I don't know how NTLite is designed and how it was able to correctly identify what is removed/changed in ReviOS. Probably it integrates some, hidden, "info file" in the image which can be detected only by the app in further editing?!
I'm not quite sure if it's a bug, regarding the Enterprise LTSC Preset, or just the Preset Loading feature needs a small improvement to allow us to "uncheck", or "include" all things that don't match the Preset file?! :)
 

Attachments

There isn't a perfect one-to-one mapping of all components between different Windows editions. The only part which is designed to be modular is Features, which you can repeatedly enable/disable on a live system.

Some of us have discussed here, for comparison purposes, the diff'ing of NTLite's export list (previously known as "listallcomponents" based on the old NTLite command line) for ReviOS and other trimmed OS'es. A few use NTLite for removals, others do not.

NTLite already does what you're looking for. When you load an extracted preset to a clean ISO, it should (more or less) try to make what changes are required to match the preset's target. Again, the component mappings aren't perfect so some removals are skipped.

For example, applying your ReviOS preset to a clean W10 22H2:

View attachment 10305

The other half of modding is the custom reg edits and scripting. NTLite can't extract any of that, gives you a head start on the base image.
 
Hello garlin,

Thank you for the reply! :)

I would like to introduce to the NTLite team a feature that exists in one the apps that I'm using on a daily basis.
The Library Manager in Dorico 4 and 5:

It's really well designed for project comparison and advanced custom decisions. It could bring some inspiration for
for the image comparison improvements.
Similar tool would make possible even the comparison between two Presets, making of modifications on preset basis and saving it (creating a preset out of two others).
For example comparing the Enterprise LTSC and ReviOS presets, making the wanted changes in both of them and saving as new preset.
Such a tool will make NTLite even more powerful. :)
 
You must log in or register to reply here.
Back
Top