A Windows Server that runs out of disk does not fail gracefully. Services stop, the event log stops writing, Windows Update fails with error 0x80070070, and backup jobs die quietly half-way through a VSS snapshot. On a VPS the root volume is usually 60\u2013120 GB, so the usual Windows growth patterns \u2014 WinSxS from cumulative updates, pagefile sizing for 16 GB of RAM, and IIS or .NET logs nobody rotates \u2014 matter far more than they do on a physical server with spare bays. This is the cleanup order that reclaims space without breaking servicing, and the settings that stop it refilling.<\/p>\n\n
Start with the free-space baseline, and record the top-level directories by size rather than opening Explorer and guessing. Before you start deleting, size the volume against realistic growth \u2014 the plan tiers on the Windows VPS plan comparison<\/a> list the disk allocation you actually get, which is the number that decides whether 60 GB is enough.<\/p> The only supported tool is Superseded update packages are the second-largest consumer after WinSxS. Disk Cleanup still works headlessly and is scriptable, which is why it survives on servers without the GUI role. Be careful with On a small VPS it is also worth capping the update cache rather than deleting it repeatedly. The pagefile is not junk. Windows uses it for crash dumps, for commit charge beyond physical RAM, and for trimming working sets under memory pressure. On a VPS with 8 GB of RAM and a .NET workload, disabling it entirely is a reliable way to produce What you can do is set a fixed size instead of letting it grow, so the file does not fragment and the disk reservation is predictable. A common rule for a VPS is 1.5\u00d7 RAM up to 8 GB, then 1\u00d7 beyond that, with a hard cap at 16 GB.<\/p> Logs are the quietest consumer and the easiest win. A single IIS site writing 50 MB of W3C logs a day consumes 18 GB a year; SQL Server error logs, CBS logs, and .NET PerfMon logs all behave the same way. Set retention in the product where possible rather than relying on a script to delete files later.<\/p> The W3C format adds one file per site per day by default, and nothing in IIS enforces a total-size limit for the folder as a whole \u2014 If cleanup keeps coming back every month, the volume is undersized rather than badly managed \u2014 compare the disk allocations on the main Windows VPS hosting page<\/a> before buying extra storage you will not fill.<\/p>","protected":false},"excerpt":{"rendered":"Get-ChildItem -Recurse<\/code> on C:\\Windows<\/code> can take several minutes on a busy server; it is still cheaper than restoring a broken component store.<\/p>Get-Volume | Where-Object DriveLetter -eq 'C' |\n Select-Object DriveLetter, FileSystemLabel, @{n='FreeGB';e={[math]::Round($_.SizeRemaining\/1GB,1)}}, @{n='SizeGB';e={[math]::Round($_.Size\/1GB,1)}}\n\nGet-ChildItem C:\\ -Directory -Force -ErrorAction SilentlyContinue |\n ForEach-Object {\n [pscustomobject]@{\n Path = $_.FullName\n GB = [math]::Round((Get-ChildItem $_.FullName -Recurse -Force -File -ErrorAction SilentlyContinue |\n Measure-Object Length -Sum).Sum \/ 1GB, 2)\n }\n } | Sort-Object GB -Descending | Select-Object -First 12<\/code><\/pre>WinSxS: use DISM, never Explorer<\/h2>
DISM \/Online \/Cleanup-Image<\/code>, and the order matters: analyze, clean, then optionally reset the base. Analysis reports how much is reclaimable before you commit to a change that removes the ability to uninstall recent updates; each pass takes 10\u201340 minutes on a shared CPU, so run it from a console session that survives a dropped RDP connection.<\/p>\/ResetBase<\/code> removes the superseded versions that allow uninstalling the most recent update. On a VPS that is usually the right trade-off \u2014 you want the space more than you want to roll back a cumulative update \u2014 but run it after a patch cycle has been validated, not in the middle of one. The PowerShell equivalent, Optimize-WindowsImage<\/code> on a mounted WIM, does not apply to an online installation; do not mix the two up.<\/p>Cleanup target<\/th> Typical reclaim on a 100 GB VPS<\/th> Safe to run online<\/th> Notes<\/th><\/tr><\/thead> DISM StartComponentCleanup<\/td> 1.5\u20134 GB<\/td> Yes<\/td> Removes superseded components older than 30 days<\/td><\/tr> DISM StartComponentCleanup \/ResetBase<\/td> adds 0.5\u20132 GB<\/td> Yes<\/td> Blocks uninstall of the last installed update<\/td><\/tr> Windows Update Cleanup (cleanmgr)<\/td> 2\u20136 GB<\/td> Yes<\/td> Overlaps with DISM; run one, then the other<\/td><\/tr> Delivery Optimization cache<\/td> 1\u20133 GB<\/td> Yes<\/td> Clear-DeliveryOptimizationCache<\/td><\/tr> CBS, DISM and MSI logs<\/td> 200\u2013800 MB<\/td> Yes<\/td> Logs grow without bound; rotate or delete<\/td><\/tr> IIS logs (daily W3C)<\/td> 0.5\u20135 GB<\/td> Yes<\/td> Depends entirely on traffic<\/td><\/tr> Hibernation file<\/td> 40% of RAM<\/td> Yes on VPS<\/td> Disable unless you need hybrid sleep<\/td><\/tr> Pagefile<\/td> fixed or system managed<\/td> Reboot needed<\/td> Never disable on a low-RAM VPS<\/td><\/tr><\/tbody><\/table> Windows Update cleanup and Delivery Optimization<\/h2>
\/sagerun<\/code> on a production host, though: it also empties the Recycle Bin and clears temp directories for every profile it can reach, including an application pool identity. If an in-flight deployment stages files under C:\\Windows\\Temp<\/code>, schedule the task outside deployment windows.<\/p>HKLM\\SOFTWARE\\Policies\\Microsoft\\Windows\\DeliveryOptimization<\/code> accepts MaxCacheSize<\/code> as a percentage of disk; 5% of a 100 GB volume leaves about 5 GB of peer cache, enough for a single host to stop re-downloading the same cumulative update every month.<\/p># Configure once interactively, then run unattended\ncleanmgr \/sageset:1 # tick Windows Update Cleanup, DoS files, logs, temp\ncleanmgr \/sagerun:1\n\n# Delivery Optimization cache and its own cleanup\nGet-DeliveryOptimizationStatus | Select-Object FileId, FileSizeInBytes\nClear-DeliveryOptimizationCache -Force<\/code><\/pre>Pagefile and hibernation on a constrained VPS<\/h2>
OutOfMemoryException<\/code> under load even when Task Manager shows free memory.<\/p>$cs = Get-WmiObject Win32_ComputerSystem\nif ($cs.AutomaticManagedPagefile) { $cs.AutomaticManagedPagefile = $false; $cs.Put() }\n\n$pf = Get-WmiObject Win32_PageFileSetting -Filter \"Name='C:\\\\pagefile.sys'\"\nif (-not $pf) { $pf = (Get-WmiObject Win32_PageFileSetting).CreateInstance() }\n$pf.Name = \"C:\\\\pagefile.sys\"\n$pf.InitialSize = 8192\n$pf.MaximumSize = 8192\n$pf.Put()\n\n# Hibernation: powercfg \/h off frees hiberfil.sys\npowercfg.exe \/hibernate off<\/code><\/pre>Log files that grow without a cap<\/h2>
truncateSize<\/code> caps each individual log file, not the directory. On a server hosting a dozen small sites that distinction alone can mean 15 GB of logs where you expected 1 GB, so combine the configuration below with a folder-level retention job.<\/p># IIS: cap total log volume per site, in bytes\nSet-WebConfigurationProperty -PSPath 'IIS:\\' `\n -Filter \"system.applicationHost\/sites\/siteDefaults\/logFile\" `\n -Name truncateSize -Value 1073741824\nSet-WebConfigurationProperty -PSPath 'IIS:\\' `\n -Filter \"system.applicationHost\/sites\/siteDefaults\/logFile\" `\n -Name periodicRestart.time -Value \"00:00:00\"\n\n# Older than 30 days, from a scheduled job\nGet-ChildItem C:\\inetpub\\logs\\LogFiles -Recurse -Filter *.log |\n Where-Object LastWriteTime -lt (Get-Date).AddDays(-30) | Remove-Item -Force<\/code><\/pre>\n