Anonymous Internet User
Active Member
- Messages
- 191
- Reaction score
- 32
Sorry, the steps were numbered wrong in that post: 1, 2, 2, 3. I fixed that.This is great info. Can you expand on how you handle moving from Steps 1-2 etc.
Example - once you "build" the actual ISO in Step 1 - is that .wim considered your "step 1" preset?
And when you move to Step 2 etc - are you actually loading the "modified" .wim (from Step 1) and applying your REG files etc to this *.wim.?
Effectively creating a "new" *.wim and building it up in layers?
I have always started from a clean ISO - every time. And I have also only ever applied a master preset (end to end) each time.
Have never really taken the time to consider working in stages - and maybe I should
Any info you can share would be great.
S
There is no preset yet after step 1. This step only integrates Windows Updates, no other modifications are done. After that, I backup entire NTLite working and program directories and move the backups aside and continue working on the existing build normally. Maybe I'm doing this the hard way but I found this to be the easiest way to go back to a previous, good build.
There is one thing I don't actually fully understand about Windows Updates integration as it seems that only the Cumulative Update actually gets installed, integrated in the image itself. But that's OK, since this is the biggest one to integrate. Also, at step 1 you may remove unneeded editions from the image. This takes a while too, so preserving this step alone will save you some time if you ever have to revert.
So, this is my first clean base to go back to, I keep a copy untouched. After that I go to step 2 and add all the stuff in that step Then, if it passes testing in a VM, I save that one too, both the working directory and the program directory, separately from the first backup. This is why a fast SSD is needed because the working dir can grow over 30GB and have hundreds of thousands of files. So this my second base build, just additions, no removals. This is the stuff that can be changed easily if something breaks or is set wrong. Set this one aside too.
Now, I start step 3 and start actual removals. If I build and test an image after this step and it's broken, then I literally trash both NTLite program and working directories and copy both from step 2 and start removals over from scratch. (Note: You can use FreeFileSync to do all this backing up and copying so it only copies files that are different but you need to be careful how you set up FFS; but it will speed things up signidicantly). This is because you can't go back and undo most removals the way you can udo REG files, post-install or settings.
Maybe there is a better way, I tried achieving this by reusing the XML files but I got into problems. This is why I just backup the whole thing and go back to it if stuff breaks. Also, I take screenshots and notes of what I'm removing so it's easier to find the culprit that broke the image. And this is also why I start with known things and leave uncertain removals for later. Once I get a working image with all the basic things removed then I backup that one too. Each consecutive backup becomes by base to revert to. I do not move/copy presets, I keep whatever preset was copied along with the last backup.
So yeah, I end up with 100-200GB of stuff. But once I install the image on actual hardware and use it for a while, I only keep the first backup (Updates Only) and the last good one; and trash the intermediate backups. I use 7zip Store mode to archive this in small segments and save it to an external disk.
Not sure if this makes sense the way I'm trying to explain it, ask if you need any clarification.
This may seem convoluted but I used this methodology with Win 11 24H2 and 25H2 and got very good results. I was able to go back to previous backups instead of starting from scratch.
Even if you don't do all these backups, working in stages and testing intermediate builds seem like a good idea to me.
Last edited:




