Feel like I should know this - but is there a way to "replace" an existing source image in NT Lite?

[Sonicmojo]

Unlike many here - I do not build ISO's with a rapid weekly/monthly cadence. I tend to pick very specific times to build out a new ISO - usually when a major OS change is in the works. I have one coming up very soon - moving one of my last key machines from Windows 10 to Windows 11 this weekend.

I build using official MSDN images (as part of MyVisualStudio enterprise sub) and using the June images - built out my Win 11 Pro 25H2 ISO - about a month ago (June 21).

I installed it into a VM, tested it and found a few things I would like to correct and a handful of reg keys I would like to add - BEFORE I build this new PC this weekend

That existing layout is still sitting within NT Lite. Yesterday - I received my July images and was wondering if it's possible to simply swap these new July files right into the June layout. Is this even possible - or recommended?

Or should I simply load a clean July image (as a new workbench), reload my saved NT Lite preset (from June), make the changes I need to make and call it a day with a new ISO?

S

 

[nuhi]

The second one, it's always best to use the starting official ISO and integrate latest update at the moment you need it.
Keep all decisions in one preset so that kind of a swap is easy.

Of course if you did not remove components and spent a lot of time hand-crafting an ISO, you can also just integrate a new one over it, but due to how Windows componentization works, it will never be as clean as integrating from scratch.

 

[Sonicmojo]

The second one, it's always best to use the starting official ISO and integrate latest update at the moment you need it.
Keep all decisions in one preset so that kind of a swap is easy.

Of course if you did not remove components and spent a lot of time hand-crafting an ISO, you can also just integrate a new one over it, but due to how Windows componentization works, it will never be as clean as integrating from scratch.

Nuhi

As I suspected. Thanks for the update.

Did want to mention to you - that in my June ISO build - I removed the Eye Control app and that triggered a whole mess of hurt during SFC /scannow and my usual DISM commands when checking the build after install.

Is this Eye Control thing off limits? Could have swore I have always removed it with little to no impact.

S

 

[nuhi]

Did want to mention to you - that in my June ISO build - I removed the Eye Control app and that triggered a whole mess of hurt during SFC /scannow and my usual DISM commands when checking the build after install.

Is this Eye Control thing off limits? Could have swore I have always removed it with little to no impact.

Hm, was Servicing Stack compatibility turned on while that component was being removed?
There is nothing special about it, I can test it if you tell me how.

 

[Sonicmojo]

Hm, was Servicing Stack compatibility turned on while that component was being removed?
There is nothing special about it, I can test it if you tell me how.

Let me load up this July ISO and take another run here - I will circle back a bit later.

Update - I see Eye Control is directly related to Mixed Reality - which is always something I ditch. Makes no sense for this to complain when being removed.

Also - Compatibility is on.

S

 

[Sonicmojo]

Nuhi

Just installed my new "july" build - and stuck will all my usual removal.

While this command came back just fine:

Dism.exe /Online /Cleanup-Image /RestoreHealth

This:

sfc /scannow

Results in this:

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

I then run (at an Admin cmd prompt):

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > "%userprofile%\Desktop\sfcdetails.txt"

To get a look at the errors in the CBS log and find this mess in the sfcdetails.txt:




Just a pile of crap surrounding that goofy Eye Control app, Webview2 being out of wack and a host of other stuff that I do not recall removing or touching at all?

Is any of this critical to the OS running correctly - becuase it appears that SFC will repair it all.

Just wondering what I did to break all of this in the first place?

Cheers

S