Windows Updates Disk Space Usage Huge Increase
Base Windows system disk usage used to be under 20GB. Applying updates and now it is over 30GB. Run settings/storage/temporary to delete files. Run DISM /resetbase. And disk space usage is still over 30GB. Is this the new normal? Or do I need to do something else?
Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
4 answers
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Nam Bui (WICLOUD CORPORATION) 1,195 Reputation points • Microsoft External Staff • Moderator
Hi Stan Kasper,
Yes, a base system disk usage of 30GB or more is now typical for modern Windows systems such as Windows Server 2022 and Windows 11, especially after cumulative updates and added features. Below is a detailed explanation and additional steps you can take to further optimize disk usage.
Why disk usage increases:
Component Store (WinSxS) growth: Even after running
DISM /ResetBase, Windows retains some components (e.g., language packs, Features on Demand) that are not removed automatically.Cumulative update cache: Windows stores update payloads to support rollback and servicing. These files are not always removed by default cleanup tools.
Other hidden space consumers: Memory dump files (e.g.,
MEMORY.DMP), Shadow copies (Volume Snapshot Service), Hyper-V checkpoints or mounted ISO files, Delivery Optimization cacheAdditional cleanup steps:
- Analyze component store
Dism /Online /Cleanup-Image /AnalyzeComponentStore- Remove superseded components
Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase- Delete memory dump files
Remove-Item -Path "C:\Windows\MEMORY.DMP" -Force -ErrorAction SilentlyContinue- Delete shadow copies
Get-WmiObject Win32_ShadowCopy | ForEach-Object { $_.Delete() }- Clear Delivery Optimization cache
Remove-Item -Path "C:\Windows\SoftwareDistribution\DeliveryOptimization\*" -Recurse -Force -ErrorAction SilentlyContinue- Remove Windows Update residuals
Remove-Item -Path "C:\Windows\SoftwareDistribution\Download\*" -Recurse -Force -ErrorAction SilentlyContinueHope the above information is helpful!
