NTLite Forums
Captured a WIn11 23h2 image from sysprep VM, updated to 22631.3007. Used the same preset to lite-n it using NTLite v2023.12.9553 --here are some findings:
Resulting install.wim (not .esd) is 0.03 bigger than Dec 2023 build state. -- not much, but then I removed a few additional components in this current build vs the Dec one. The difference in size lies mainly in \Program Files\WindowsApps. It appears there are some additional runtimes present in the .3007 build. On the Dec build it retained Microsoft.UI.Xaml.2.7.x (one instance, x64 only), whereas in this current .3007 build it retained both arches for .Xaml.2.7x AND 2.8.x as you can see in the screenshot below (Dec build left; .3007 build right). Again same for the VCLibs.140 which also occurs dual arch. I don't know whether the inclusion of x86 runtimes there is new since I did not specify removal of these for the Dec build, and yet x86 runtimes are absent in the NTLite'd Dec image. See:
Perhaps this will be useful. Attached is my preset.
Resulting install.wim (not .esd) is 0.03 bigger than Dec 2023 build state. -- not much, but then I removed a few additional components in this current build vs the Dec one. The difference in size lies mainly in \Program Files\WindowsApps. It appears there are some additional runtimes present in the .3007 build. On the Dec build it retained Microsoft.UI.Xaml.2.7.x (one instance, x64 only), whereas in this current .3007 build it retained both arches for .Xaml.2.7x AND 2.8.x as you can see in the screenshot below (Dec build left; .3007 build right). Again same for the VCLibs.140 which also occurs dual arch. I don't know whether the inclusion of x86 runtimes there is new since I did not specify removal of these for the Dec build, and yet x86 runtimes are absent in the NTLite'd Dec image. See:
Perhaps this will be useful. Attached is my preset.