Ok so what I have done for this example here does not include anything other than drivers and updates, all other parts of ntlite blank for these 2 isos I made.
Having reading posts everywhere i decided to make a new base image for my tinkering that would already have updates and drivers integrated.
What I did on the first one was to fetch the online update list, I left the default updates ticked and imported the .net 3.5 template.
I then made the image using dism (compatibility) option and also the parallel + cache.
I have since booted that iso and from what I can tell it worked perfect. The install.wim was 3.94GB and boot.wim 640.6MB
--
I then did a second pass on the edit cache and integrated virtio drivers, on install.wim and both options on boot.wim, these I know were already working as was integrating previously, but wanted this done on base so i wouldnt have to keep redoing boot.wim.
After this was done however I observed the new iso was about 200MB smaller.
I then extracted both iso's to each have their own edit cache, and opened up wiz tree to compare, the install.wim is fine, but the boot.wim is now 200MB smaller on the newer image. I fear the driver integration may have undone dynamic update or something?
I also tested this second iso, and it appears fine, drivers working, no new CU or new .NET CU.
But something tells me the boot.wim shrinking there is something wrong? Or can I ignore this and move on? Maybe I should have done drivers before updates?
If I have to do in single pass I will do, but DISM is very slow so prefer to not have to redo that process every time.
Having reading posts everywhere i decided to make a new base image for my tinkering that would already have updates and drivers integrated.
What I did on the first one was to fetch the online update list, I left the default updates ticked and imported the .net 3.5 template.
I then made the image using dism (compatibility) option and also the parallel + cache.
I have since booted that iso and from what I can tell it worked perfect. The install.wim was 3.94GB and boot.wim 640.6MB
--
I then did a second pass on the edit cache and integrated virtio drivers, on install.wim and both options on boot.wim, these I know were already working as was integrating previously, but wanted this done on base so i wouldnt have to keep redoing boot.wim.
After this was done however I observed the new iso was about 200MB smaller.
I then extracted both iso's to each have their own edit cache, and opened up wiz tree to compare, the install.wim is fine, but the boot.wim is now 200MB smaller on the newer image. I fear the driver integration may have undone dynamic update or something?
I also tested this second iso, and it appears fine, drivers working, no new CU or new .NET CU.
But something tells me the boot.wim shrinking there is something wrong? Or can I ignore this and move on? Maybe I should have done drivers before updates?
If I have to do in single pass I will do, but DISM is very slow so prefer to not have to redo that process every time.
Last edited: