Summary
On a Windows Server system, drive C can display a low disk space warning even if File Explorer shows available disk space and no unusually large folders. This situation typically occurs when one or more applications generate large temporary files in hidden or system-protected folders. These folders aren't reported accurately by standard file management or monitoring tools.
This article explains the most common cause of this issue, and provides steps to identify and remove the files that are consuming excessive disk space.
Symptoms
You experience the following symptoms:
- Drive C displays a low disk space warning in Windows Server.
- A review of folder sizes in File Explorer doesn't indicate any unusually large folders.
- No recent configuration changes, installations, or updates (including Windows updates) occurred that could explain the sudden loss of free space.
- The issue persists for multiple days.
Cause
The usual cause of this issue is large temporary files that might not be discoverable by File Explorer. These files are generated by one or more applications, and aren't part of the Windows operating system. They might be stored in hidden or system-protected locations on drive C. Therefore, folder size metrics might not include the files. Over time, these files accumulate and consume available disk space.
Resolution
To resolve the issue, follow these steps:
-
Look for large temporary files, especially hidden files. For example, at a Windows PowerShell command prompt, run a command that resembles the following command:
Get-ChildItem -Path "C:\" -Recurse -ErrorAction SilentlyContinue | Sort-Object Length -Descending | Select-Object FullName, Length -First 20At a Windows Command Prompt, you can run commands that resemble the following example:
dir C:\ /s /a /o-s[!NOTE]
When you use these parameters, thedircommand recurses subdirectories, includes hidden and system files, and sorts the results by size in descending order. -
Back up the system or the folders that contain the temporary files.
-
Determine which application generates the large temporary files. Focus on recently used applications and applications that run continuously.
-
Contact the application vendor to determine whether the temporary files are required, and to configure the application to manage the temporary files more effectively.
-
Remove temporary files that you don't need anymore.
-
To help detect future issues early, monitor folder growth. You can use monitoring tools, PowerShell scripts, or commands such as
dir /allto track this information.
Data collection
If you need assistance from Microsoft Support or your application vendor, collect the following information:
- Windows Server version and build details
[!NOTE]
To see the exact version and build number, runwinverat a command prompt on the affected computer. - A list of installed applications and their versions.
- Directory size reports from tools such as WinDirStat or from PowerShell cmdlets.
- Timestamps and file paths of the largest files on drive C.
- Event data that covers the period when available disk space started decreasing. You can export this information from Event Viewer.
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
