Disk at 100% in Task Manager: finding the cause

The game hitches, you open Task Manager, and the Disk column says 100%. Or the PC takes minutes to become usable after you sign in, with the disk pinned the whole time. Or it shows up mid-match and you wonder whether the drive is dying.

The number is real but narrow: it says the disk had work waiting the whole time, not how much work or whose. Finding whose is the job.

What 100% measures

On the Performance tab, select the disk. Task Manager describes its Active time as the percentage of time the disk is processing read or write requests, and Resource Monitor describes its Active Time (%) column as the percentage of time the disk is not idle. Microsoft's Ask Core team, explaining Performance Monitor's % Idle Time counter, defines idle as every request completed and none pending.

So 100% means no moment in the interval had nothing waiting. It says nothing about how much data moved or how full the drive is. The same page shows the rest: Read speed and Write speed, Average response time, Type (such as SSD or HDD) and System disk (whether Windows is on it).

Busy with a lot moving is a big job, such as an install, a copy or a patch. Busy with little moving and long response times means requests are waiting on the drive, and Microsoft's performance troubleshooting guide asks the question that matters then: is the disk overwhelmed, and if so, who is using it?

Find the process

On the Processes tab, select the Disk column header to sort by it. Many Windows services run inside Service Host processes, and since Windows 10 version 1703, on PCs with more than 3.5 GB of RAM, each service gets its own, with a few exceptions; Microsoft's service host documentation says that lets you look at Task Manager and know exactly which service is using what resources.

If you applied w0a's Consolidate service processes (svchost) setting, services share host processes again, and its page lists per-service figures in Task Manager as the cost (Memory tweaks).

For file-level detail, use Task Manager's Open Resource Monitor command, or press Win+R and run resmon. Its Disk tab has three lists:

Processes with Disk Activity lists Read (B/sec), Write (B/sec) and Total (B/sec) per process. Resource Monitor's own column descriptions call these averages over the last minute, so a short burst looks small and fades slowly.
Disk Activity lists each file being read or written, with its Response Time (ms). Tick a process in the pane above to filter this list to it.
Storage shows each drive's Active Time (%) and Disk Queue Length.

For a disk pinned right after sign-in, also check the Startup impact column on Task Manager's startup page, which measures CPU and disk activity during startup.

Windows jobs that use the disk

Several Windows jobs read or write files while they run:

Windows Update. Settings > Windows Update shows whether something is downloading or installing. Pause updates on the same page holds them for a while. In its latest form, Microsoft's page on pausing says, you pick an end date up to 35 days ahead and can extend it later within the same limit; when the pause ends, Windows checks for, downloads and installs the latest updates.
Delivery Optimization. The downloader behind Windows Update, Microsoft Store apps, Defender definition updates and Xbox Game Pass on PC, among others, according to Microsoft's list. It appears as a Service Host row of that name, and Microsoft's FAQ notes that, depending on the app, closing it may not stop the download.
Microsoft Defender Antivirus, listed as Antimalware Service Executable. A scan reads files, so it can show up in the Disk column while it runs, and Microsoft's troubleshooting page notes that by default it also scans after each security intelligence update. Antimalware Service Executable using CPU while gaming covers recording what it scans and moving its scheduled scan. Microsoft warns that exclusions reduce protection, and its list of folders you shouldn't exclude includes program folders for installed apps; a game is an installed app.
Search indexing, listed as Microsoft Windows Search Indexer. Microsoft's FAQ says the first indexing run can take up to a couple of hours, and that Windows then keeps updating the index as files change, so copying many files into indexed folders gives it new work. Its settings are under Settings > Privacy & security.
SysMain, a Service Host row, which Windows describes as maintaining and improving system performance over time. Microsoft's 2009 Windows 7 notes said Superfetch and prefetching were designed for hard drives, where random reads could be a major bottleneck; we found no current Microsoft page that says how Windows 11 handles it on SSDs. If a guide had you stop it and apps now launch slower, the Slow app launches card on w0a's Fix page restores Prefetch/SysMain memory preloading to the Windows default (enabled), as Slow app launches describes.
OneDrive. Microsoft's support page says syncing can be paused for 2, 8 or 24 hours from the OneDrive icon on the taskbar, and that it resumes by itself when the time is up.

When Windows is on a hard drive

If the busy disk is an HDD and it is the system disk, the drive itself sets the pace. The same Microsoft guide works it out from rotation: a 5,400 RPM disk should be able to read any block within about 11 ms, in theory. In Microsoft's 2009 Windows 7 engineering tests, 176 of 182 hard drive configurations scored between 0.8 and 1.6 MB/s on the random read test. So a hard drive serving scattered reads can be busy all the time while moving around a megabyte a second.

The guide also grades latency. For the Performance Monitor counters Avg. Disk sec/Read and Avg. Disk sec/Write, it calls under 15 ms healthy, over 25 ms a warning and over 50 ms critical; short spikes can be tolerated, and periods of over a minute are worth investigating. Task Manager's Average response time gives a quick reading in milliseconds; the thresholds were written for the Performance Monitor counters.

No setting makes a disk spin faster. SSD vs HDD for games covers what an SSD changes for games, and what it does not.

When the drive itself may be failing

If nothing in Resource Monitor accounts for the activity, or response times stay long while little is moving, check the drive. Without administrator rights, PowerShell gives Windows' own summary:

Get-PhysicalDisk | Format-Table DeviceId, FriendlyName, MediaType, HealthStatus

HealthStatus reads Healthy, Warning, Unhealthy or Unknown, which Microsoft calls a high-level indication of device health. For the drive's own counters, open PowerShell as administrator (without it, Windows refuses with an access-denied error) and run:

Get-PhysicalDisk | Get-StorageReliabilityCounter | Format-List DeviceId, Temperature, Wear, ReadErrorsUncorrected, WriteErrorsUncorrected, ReadLatencyMax

DeviceId matches the first command. Some fields can come back empty, as one does in Microsoft's own example. The reliability counter reference defines Wear as a percentage, where 100 means the estimated wear limit has been reached, and says a ReadLatencyMax (given in milliseconds) over 10 seconds may indicate a problem with the disk or the host bus adapter. The uncorrected counts are errors the drive itself could not correct.

CrystalDiskInfo reads the drive's S.M.A.R.T. data and rates it Good, Caution, Bad or Unknown. Its documentation says it watches the reallocated, current pending and uncorrectable sector counts on hard drives, and shows Caution on an SSD with 10% or less of its life remaining. If any of these readings look wrong, copy what matters off the drive first.

What does not help

Memory optimizer tools. Microsoft's performance guidance says so-called memory optimizers force the kernel to delete its disk cache and trim the working sets of processes, and that all this does is cause a lot of unnecessary disk I/O.
Removing the page file. Paging is disk activity, but removing the page file lowers how much memory Windows can promise programs; The page file and games explains why that backfires.
Switching Delivery Optimization off to stop downloads. Microsoft's FAQ says disabling it doesn't prevent content from downloading to your devices; for holding updates back, it points to each component's own policies, such as those for Windows Update or the Store.

Did this page help?

What was missing, or what did not work? We read every one of these.

If this page did not solve it, write to us — say which article you read, and we will fix the article.