# Windows Disk Usage at 100%: Trace the Process, Files and Latency When a PC stalls, Task Manager may show an idle CPU and a disk stuck at 100%. Start by identifying the work the disk is handling. Game downloads, archive extraction, synchronization and paging can all keep it busy, but they call for different actions. ## Read activity, latency and capacity separately Select the disk under Task Manager's Performance tab and compare active time, average response time, read speed and write speed. Active time describes the share of time the disk is busy servicing requests. Transfer speed measures data per second. Free capacity appears separately under This PC in File Explorer. | Reading | What it tells you | What it cannot establish alone | | --- | --- | --- | | Active time | Whether the disk stays busy | Which app or operation causes the work | | Read/write speed | How much data moves per second | Whether small-file access is slow | | Average response time | How long requests take on average | Whether the drive has failed | | Free space | How much more content fits | Why the current app is unresponsive | Consider two hypothetical tasks: copying one large video at a high transfer rate, and repeatedly reading small files scattered across storage. The latter can be slow despite modest throughput. Neither a 100% reading nor a low MB/s value alone proves that the drive is reaching its advertised sequential speed. [Microsoft's performance troubleshooting guide](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/troubleshoot-performance-problems-in-windows) correlates disk latency with process activity and distinguishes spikes from sustained delays. Its server-oriented thresholds are not universal health limits for laptops. ## Follow the process to the files it touches Press `Ctrl + Shift + Esc`, sort Processes by Disk and note the busiest app. Press `Win + R`, enter `resmon` and inspect Disk activity for that process. Some system-process information requires administrator privileges; missing rows under ordinary permissions do not prove inactivity. A path can narrow the explanation. A game-library file may be undergoing extraction, a OneDrive file may be syncing, and a project folder may be compiling or indexing. Paging-file activity calls for checking available and committed memory too. The filename alone cannot diagnose a failing drive. Compare reads, writes, total activity and response times. Process I/O and physical disk throughput need not add up identically because caching, shared access and sampling windows affect the readings. ## Pause one identified task and repeat the problem Pause cloud synchronization inside its app, pause a game installation in its launcher, or save your work before cancelling your own build. Change one task at a time. Repeat the operation that stalled and check whether latency and responsiveness improve together, then resume the task to see whether the symptom returns. [Microsoft's PC performance guidance](https://support.microsoft.com/en-us/windows/experience/performance-optimization/tips-to-improve-pc-performance-in-windows) handles background apps, storage and updates as separate concerns. Avoid disabling Defender, Windows Update, system services or the paging file merely to lower the graph.
Trace the work, then test one change
A paused workload is evidence only when the original operation and its latency improve together.
## Capture useful evidence when the delay persists If extraction has finished but storage remains slow and file reads produce errors, copy important files to independent storage and open the copies before further diagnosis. Record the drive model, process, path and exact error for the PC or drive manufacturer. Unusual noises, repeated disconnections and failed reads matter more than the percentage alone; preserve your only copy before stress testing. When the basic tools do not reveal the file source, [Process Monitor](https://learn.microsoft.com/en-us/sysinternals/downloads/procmon) can capture file operations. Filter a short capture to the identified process, stop recording and inspect it. The trace shows operations rather than certifying drive failure. Recording also consumes storage, and traces can contain personal paths. ## Verify the original task after making space For low free capacity, use the [C-drive guide](/windows/blog/windows-c-drive-full). For frequent paging, read about [memory pressure](/windows/blog/windows-high-memory-usage). Mole's Analyze page helps locate large folders; a large file is not necessarily the file currently causing disk activity. Repeat the original workload after cleanup before attributing better responsiveness to it. Canonical: https://mole.fit/windows/blog/windows-disk-100-percent