Skip to Content

Windows Server: System Drive (C:) Full

By OdooBot · Published 02/07/2026 · 3 views

Windows Server: System Drive (C:) Full

Category: Windows Server · Audience: Technicians · Est. time: 15–30 min

Summary

A full C: drive on a server causes service failures, failed updates, and outages. These are the safe, high‑yield places to reclaim space on a Windows Server.

⚠️ Never bulk‑delete files you don't recognise on a server. Move/clear only the known‑safe items below, and confirm backups are healthy first.

Find what's using space

  • Use WizTree or TreeSize (technician tools) to see the biggest folders fast — far quicker than clicking around.

Safe things to clear

  1. Temp files & Update cache. Run Disk Cleanup (cleanmgr) → Clean up system files → tick Windows Update Cleanup, Temp, delivery optimisation. Or clear C:\Windows\Temp and %temp%.
  2. Old Windows Update files. In Terminal (Admin):
Dism /Online /Cleanup-Image /StartComponentCleanup
  1. IIS / app logs. Web servers accumulate huge logs at C:\inetpub\logs\LogFiles. Archive/delete old logs (keep recent). Check app‑specific log folders too.
  2. Windows Event Logs — if massive, archive and clear from Event Viewer (right‑click log → Clear, save first if needed).
  3. User profiles / downloads on RDS/terminal servers — old profiles and Downloads folders add up. Remove stale profiles via System → Advanced → User Profiles (confirm the user has left).
  4. Volume Shadow Copies (if oversized): review with vssadmin list shadowstorage and resize if appropriate (careful — these are restore points).

Things that are often the real cause

  • A runaway log from an application or antivirus filling C:.
  • SQL / database files or backups on C: (should be on a data volume) — move them, don't delete.
  • Windows.old after a feature update (20+ GB) — remove via Disk Cleanup.
  • Page file / memory dumps — a full‑memory crash dump can be huge; set dump type to smaller if not needed.

If that doesn't work

  • If C: is simply undersized, plan a volume expansion (VM disk grow + extend in Disk Management) or move data roles to another volume.
  • Escalate to BBN Support with the server name and the biggest folders found by WizTree/TreeSize.

Prevention

  • Keep databases, backups, and heavy logs off C:; monitor free space so BBN is alerted before it fills.

Was this article helpful?

Yes No

Didn't find what you were looking for?

Submit a Ticket