using Windows LTSC 1809 x64 image (original install.wim size 3.84GB):
when integrating updates with following commands:
dism /export-image /sourceimagefile:C:\WIM\install.wim.orig /sourceindex:1 /destinationimagefile:c:\WIM\install.wim
Mount-WindowsImage -ImagePath "c:\WIM\install.wim" -Index 1 -Path "c:\mount" -ScratchDirectory "c:\temp"
Add-WindowsPackage -PackagePath "c:\updates\Servicing" -Path "c:\mount" -ScratchDirectory "c:\temp" -LogLevel WarningsInfo
Add-WindowsPackage -PackagePath "c:\updates\Flash" -Path "c:\mount" -ScratchDirectory "c:\temp" -LogLevel WarningsInfo
Add-WindowsPackage -PackagePath "c:\updates\Micro" -Path "c:\mount" -ScratchDirectory "c:\temp" -LogLevel WarningsInfo
Add-WindowsPackage -PackagePath "c:\updates\MonthlyCU" -Path "c:\mount" -ScratchDirectory "c:\temp" -LogLevel WarningsInfo
...
Save-WindowsImage -Path "c:\mount" -ScratchDirectory "c:\temp"
Dismount-WindowsImage -Path "c:\mount" -ScratchDirectory "c:\temp" -CheckIntegrity -Save
Doing this results in wim.install size of about 5.1GB (already I feel that is way too big considering the total updates size)
On the line where the dots (...) are, I normally enter:
Dism /Image:c:\mount /Cleanup-Image /AnalyzeComponentStore (which will return that we need to do a clean-up)
Dism /Image:c:\mount /Cleanup-Image /StartComponentCleanup /ResetBase
After this when I perform again:
Dism /Image:c:\mount /Cleanup-Image /AnalyzeComponentStore >> this will now say there is no clean-up needed and the winsxs is shrink by ~2-3GB or so.
Then when dismounting and completing the process, the resulting install.wim is 5.4GB (!!!) - even bigger than without these clean-up commands.
Anyone can replicate this process and let me know if this is not just happening with me?
Any expert can think of a reason and maybe even know a solution to this?
Thanks!
when integrating updates with following commands:
dism /export-image /sourceimagefile:C:\WIM\install.wim.orig /sourceindex:1 /destinationimagefile:c:\WIM\install.wim
Mount-WindowsImage -ImagePath "c:\WIM\install.wim" -Index 1 -Path "c:\mount" -ScratchDirectory "c:\temp"
Add-WindowsPackage -PackagePath "c:\updates\Servicing" -Path "c:\mount" -ScratchDirectory "c:\temp" -LogLevel WarningsInfo
Add-WindowsPackage -PackagePath "c:\updates\Flash" -Path "c:\mount" -ScratchDirectory "c:\temp" -LogLevel WarningsInfo
Add-WindowsPackage -PackagePath "c:\updates\Micro" -Path "c:\mount" -ScratchDirectory "c:\temp" -LogLevel WarningsInfo
Add-WindowsPackage -PackagePath "c:\updates\MonthlyCU" -Path "c:\mount" -ScratchDirectory "c:\temp" -LogLevel WarningsInfo
...
Save-WindowsImage -Path "c:\mount" -ScratchDirectory "c:\temp"
Dismount-WindowsImage -Path "c:\mount" -ScratchDirectory "c:\temp" -CheckIntegrity -Save
Doing this results in wim.install size of about 5.1GB (already I feel that is way too big considering the total updates size)
On the line where the dots (...) are, I normally enter:
Dism /Image:c:\mount /Cleanup-Image /AnalyzeComponentStore (which will return that we need to do a clean-up)
Dism /Image:c:\mount /Cleanup-Image /StartComponentCleanup /ResetBase
After this when I perform again:
Dism /Image:c:\mount /Cleanup-Image /AnalyzeComponentStore >> this will now say there is no clean-up needed and the winsxs is shrink by ~2-3GB or so.
Then when dismounting and completing the process, the resulting install.wim is 5.4GB (!!!) - even bigger than without these clean-up commands.
Anyone can replicate this process and let me know if this is not just happening with me?
Any expert can think of a reason and maybe even know a solution to this?
Thanks!