{"id":729,"date":"2026-09-09T22:57:19","date_gmt":"2026-09-09T22:57:19","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/?p=729"},"modified":"2026-09-16T22:06:21","modified_gmt":"2026-09-16T22:06:21","slug":"windows-server-disk-cleanup-vps","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/windows-server-disk-cleanup-vps\/","title":{"rendered":"Windows Server Disk Cleanup on a VPS: WinSxS, IIS Logs, and Shadow Copies Explained"},"content":{"rendered":"\n

Windows Server fills up a VPS disk far faster than most admins expect. A 100 GB system volume on a busy Windows VPS typically loses 20\u201340 GB per year to component store growth, IIS logs, Windows Update caches, and shadow copies. This guide walks through the exact folders that consume space, how to measure them safely, and which cleanup actions are reversible \u2014 because “delete everything in WinSxS” is the fastest way to break servicing on a production server.<\/p>\n\n\n\n

Measure First: Where the Space Actually Goes<\/h2>\n\n\n\n

Never clean a drive you have not measured. Run these from an elevated PowerShell session. The first command gives you top-level folder sizes on the system drive in a few minutes on a typical VPS.<\/p>\n\n\n\n

Get-ChildItem C:\\ -Directory -Force |\n  ForEach-Object {\n    $size = (Get-ChildItem $_.FullName -Recurse -File -Force -ErrorAction SilentlyContinue |\n             Measure-Object -Property Length -Sum).Sum\n    [PSCustomObject]@{ Folder = $_.FullName; GB = [math]::Round($size\/1GB,2) }\n  } | Sort-Object GB -Descending | Select-Object -First 15<\/code><\/pre>\n\n\n\n
For the component store, which is usually the largest single consumer, use the dedicated analyzer instead of Explorer:<\/p>\n\n\n\n
Dism.exe \/Online \/Cleanup-Image \/AnalyzeComponentStore<\/code><\/pre>\n\n\n\n
\n\n
Location<\/th>Typical size<\/th>Safe to clean?<\/th><\/tr><\/thead>\n
C:\\Windows\\WinSxS<\/td>8\u201320 GB<\/td>Only via DISM \u2014 never manually<\/td><\/tr>\n
C:\\Windows\\SoftwareDistribution\\Download<\/td>2\u201310 GB<\/td>Yes, after stopping wuauserv<\/td><\/tr>\n
C:\\Windows\\Logs\\CBS<\/td>1\u20135 GB<\/td>Yes, .log and .cab files<\/td><\/tr>\n
C:\\inetpub\\logs\\LogFiles<\/td>1\u201330 GB<\/td>Yes, archive or delete old W3C logs<\/td><\/tr>\n
C:\\Windows\\Temp and %TEMP%<\/td>0.5\u20135 GB<\/td>Yes<\/td><\/tr>\n
System Volume Information (shadow copies)<\/td>5\u201350 GB<\/td>Trim via vssadmin, keep at least one<\/td><\/tr>\n
C:\\Windows\\Installer<\/td>2\u20138 GB<\/td>No \u2014 breaks uninstall\/repair<\/td><\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n
Safe High-Value Cleanups, In Order<\/h2>\n\n\n\n
1. Component store (WinSxS) via DISM<\/h3>\n\n\n\n
The supported cleanup reclaims superseded components without touching the active ones. Expect 2\u20136 GB on a server that has taken a year of cumulative updates.<\/p>\n\n\n\n
Dism.exe \/Online \/Cleanup-Image \/StartComponentCleanup \/ResetBase<\/code><\/pre>\n\n\n\n
Caution: \/ResetBase<\/code> makes all currently installed updates non-uninstallable. That is usually acceptable on a VPS where you would rebuild rather than roll back, but skip it if you are mid-way through validating a patch cycle.<\/p>\n\n\n\n
2. Windows Update download cache<\/h3>\n\n\n\n
Stop-Service wuauserv, bits -Force\nRemove-Item C:\\Windows\\SoftwareDistribution\\Download\\* -Recurse -Force -ErrorAction SilentlyContinue\nStart-Service wuauserv, bits<\/code><\/pre>\n\n\n\n
3. IIS and CBS logs with age-based retention<\/h3>\n\n\n\n
# Delete W3C logs older than 30 days\nGet-ChildItem C:\\inetpub\\logs\\LogFiles -Recurse -File -Filter *.log |\n  Where-Object LastWriteTime -lt (Get-Date).AddDays(-30) | Remove-Item -Force\n\n# Compress CBS logs instead of deleting them outright\nCompress-Archive -Path C:\\Windows\\Logs\\CBS\\CBS.log -DestinationPath C:\\Windows\\Logs\\CBS\\CBS-archive.zip -Force<\/code><\/pre>\n\n\n\n
Better than deleting IIS logs is preventing unbounded growth at the source: in IIS Manager open the site’s Logging<\/em> feature and set Log File Rollover<\/em> to a schedule with a maximum file size, and disable logging entirely for healthy static sites. Our IIS application pool recycling guide<\/a> covers the related housekeeping that keeps worker processes from leaking memory while you are at it.<\/p>\n\n\n\n
4. Shadow copy storage<\/h3>\n\n\n\n
vssadmin list shadowstorage\nvssadmin resize shadowstorage \/for=C: \/on=C: \/maxsize=10GB<\/code><\/pre>\n\n\n\n
Volume Shadow Copy is the usual hidden culprit on VPS plans with snapshots enabled by the provider. Cap the storage and let older restore points age out naturally rather than deleting the whole shadow copy set, which would break application-consistent backups on SQL Server.<\/p>\n\n\n\n
Automate It With a Scheduled Maintenance Task<\/h2>\n\n\n\n
Manual cleanup does not survive contact with a busy quarter. Register a monthly task that logs reclaimable space before and after, so you can prove the cleanup is working and catch runaway log growth early.<\/p>\n\n\n\n
$action  = New-ScheduledTaskAction -Execute 'powershell.exe' `\n  -Argument '-NoProfile -Command \"Dism.exe \/Online \/Cleanup-Image \/StartComponentCleanup; Get-ChildItem C:\\inetpub\\logs\\LogFiles -Recurse -File | Where-Object LastWriteTime -lt (Get-Date).AddDays(-30) | Remove-Item -Force\"'\n$trigger = New-ScheduledTaskTrigger -Monthly -DaysOfMonth 1 -At 3am\nRegister-ScheduledTask -TaskName 'Monthly Disk Maintenance' -Action $action -Trigger $trigger `\n  -User 'SYSTEM' -RunLevel Highest<\/code><\/pre>\n\n\n\n
How Much Space You Actually Need on a VPS<\/h2>\n\n\n\n
For planning purposes, size the system volume to include the OS baseline plus<\/em> growth. The table below reflects what we see on real production Windows VPS instances.<\/p>\n\n\n\n
\n\n
Windows Server role<\/th>Baseline OS<\/th>Recommended system volume<\/th><\/tr><\/thead>\n
Core install, file\/app server<\/td>~12 GB<\/td>60 GB<\/td><\/tr>\n
IIS + .NET hosting<\/td>~18 GB<\/td>80\u2013100 GB<\/td><\/tr>\n
SQL Server Express + IIS<\/td>~25 GB<\/td>120 GB (separate data volume)<\/td><\/tr>\n
RDS session host with profiles<\/td>~30 GB<\/td>150 GB+<\/td><\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n
If you are repeatedly cleaning to survive the month, the disk is undersized \u2014 not the OS. A Windows VPS from InterServer<\/a> starts at $0.01 for the first month with promo code TRYINTERSERVER<\/strong>, and their plans are price-locked, so scaling to a larger NVMe system volume does not mean a surprise renewal hike. Storage tiers are compared in detail in our NVMe vs SSD vs HDD guide<\/a>, and the windows-vps.org<\/a> homepage lists current Windows plan specs side by side.<\/p>\n\n\n\n
Common Mistakes That Cost You a Rebuild<\/h2>\n\n\n\n