So, how to stop the ISO from getting bigger with every cumulative Windows update every month? Besides, doing it from scratch? Cause if I do it from scratch it only grabs the latest cumulative update, so the iso will be much smaller than adding the latest cumulative update to an iso which had an older cumulative update added to it before.
How to stop the ISO from getting bigger with every Windows and framework cumulative updates?
- Thread starter xShARkx
- Start date
- Messages
- 1,200
- Reaction score
- 237
I always do it from scratch (just the checkpoint and LCU), but normally, the latest CU only adds the files, etc... that have been modified (cumulative) if the previous CU is present and shouldn't "grow" the ISO too much
To shrink the ISO a little, you can delete the update backup (Manifest Backup) this removes "duplicates", etc... (see info in description)
To shrink the ISO a little, you can delete the update backup (Manifest Backup) this removes "duplicates", etc... (see info in description)
Cumulative updates imply Windows is slowly growing larger over time. If you perform a DISM ResetBase cleanup, then the oldest versions of any superseded (replaced) component will be removed. The drawback is you cannot uninstall the last update, which is fine if you're doing a clean install since you can always replace a bad install image.
In reality, because Monthly Updates are cumulative most of the packaged components are the same from month to month. So overlaying a newer update, where most of the internal components are already duplicated, won't grow the image that much from the previous one. Only newer components cause the real growth.
Replacing a component with the same version again doesn't make Windows bigger.
What is wasteful is keeping the earlier update versions around, and adding them to the processing queue.
In reality, because Monthly Updates are cumulative most of the packaged components are the same from month to month. So overlaying a newer update, where most of the internal components are already duplicated, won't grow the image that much from the previous one. Only newer components cause the real growth.
Replacing a component with the same version again doesn't make Windows bigger.
What is wasteful is keeping the earlier update versions around, and adding them to the processing queue.
