How to See Disk Activity per Process in Windows
To see the disk activity of any process in Windows, open Task Manager with Ctrl-Shift-Esc and look at the Disk column on the Processes tab. For total bytes read and written per process, add the I/O read bytes and I/O write bytes columns on the Details tab. Process Explorer and Resource Monitor offer the same data with more detail.
This guide covers these tools, what each number means, and which one fits which question: finding a process that thrashes the drive, or checking how much a program writes to an SSD.
Task Manager Processes tab: the quick check
The Processes tab in Task Manager shows live disk activity per process in its Disk column, and it is visible by default in current Windows versions.
Press Ctrl-Shift-Esc, stay on the Processes tab, and click the Disk column header to sort. The process with the highest value is the one using the drive most right now. The percentage at the top of the column is the busy time of the drive overall, not a single process.

This view answers "what is hammering my drive at this moment?" It does not show totals over time, so a process that wrote a lot ten minutes ago can look idle. For totals, use the Details tab below. If Task Manager looks different from the screenshot, you may be on the redesigned version; see our look at the new Fluent-style Task Manager.
Task Manager Details tab: I/O read bytes and I/O write bytes
The Details tab of Task Manager can display I/O read bytes and I/O write bytes per process, but both columns are hidden by default.
- Press Ctrl-Shift-Esc to open Task Manager. If you see the compact view on Windows 8 or newer, click "More details".
- Switch to the Details tab.
- Right-click any column header and select "Select columns".
- Check I/O reads, I/O writes, I/O read bytes and I/O write bytes.
- Click OK.

Click a column header to sort. The values are cumulative counters in bytes, so they grow from the moment a process starts, and they reset when the process closes. I/O write bytes is the useful column if you want to know which programs write the most to a solid state drive. Treat the numbers as a relative ranking between processes rather than an exact count of data that reached the physical disk. A byte converter helps with the large values.
Process Explorer: per-process disk columns
Process Explorer, the free Sysinternals tool from Microsoft, can show read and write bytes for every process once you enable its disk columns.
The program is portable: download it from the Microsoft Learn Process Explorer page and run procexp.exe, or start it directly from Sysinternals Live without installing anything. The current release, version 17.21, lists Windows 11 as its supported client.
- Start Process Explorer.
- Select View > Select Columns.
- Open the Process Disk tab. The tab name can differ between versions, so pick the tab that contains the Read Bytes and Write Bytes options.
- Check Read Bytes and Write Bytes, then click OK.

The new columns appear on the right side of the table, so you may have to scroll. Click a header to put the biggest readers or writers on top.

Treat these columns as running totals as well, and compare processes with each other rather than reading the numbers as an exact count of data written to the physical drive.
Resource Monitor and Process Monitor: live rates and file-level detail
Resource Monitor shows per-process disk speeds in bytes per second, and Process Monitor shows which files a process touches.
For Resource Monitor, search for it in the Start menu, open the Disk tab, and read the "Processes with Disk Activity" list. It shows read and write speeds for each process, and the Disk Activity list below it breaks the traffic down by file.
When you need to know why a process is busy, use Process Monitor from Sysinternals. It records file system, registry and process activity in real time, attributes each event to a process, and lets you filter by process name or path. It produces a lot of data, so set a filter before you start capturing.
Which tool for which question
Use Task Manager for a quick look, Process Explorer or the Details tab for totals, and Resource Monitor or Process Monitor to dig deeper.
| Tool | Shows | Best for |
|---|---|---|
| Task Manager, Processes | Current disk use per process | Finding what slows the PC now |
| Task Manager, Details | Cumulative read and write bytes | Comparing SSD writes between programs |
| Process Explorer | Read and write bytes per process | Same, plus process tree and handles |
| Resource Monitor | Live bytes per second, per file | Seeing which files are active |
| Process Monitor | Every file operation | Finding the cause of the activity |
If the cause is a full drive rather than a busy process, a disk space analyzer such as WizTree helps. For CPU, memory and GPU load next to the disk numbers, see how to display CPU, GPU and RAM usage natively on Windows 11.
Related: New Task Manager in Windows 11, CPU, GPU and RAM usage on Windows 11, What is wsappx
I’m doing a backup of Outlook by exporting all the files to a thumb drive and would like to be able to monitor the copy/paste activity as the backing-up process takes place that way I can easily tell when the backup (export) is done. I’m not seeing, or I couldn’t find that kind of activity when I modified Task Manager/Details view so that it also shows the I/O activity.
The same issue applies when I copy from 1 thumb drive to another thumb drive.
http://winaero.com/blog/caution-firefox-can-wear-out-your-ssd-drive/
What about Process Hacker? Process Hacker is open source alternative of Process Explorer.
Excellent article, thanks.
(the Task Manager shortcut is Ctrl-Shift-Esc)
George, you are right of course. Corrected the shortcut in the article.
You can just use Perfmon, it’s more easy and already in Windows:
Click on the Start Button and key in “perfmon.exe /res” and hit Enter. This would launch the Resource Monitor
http://i.imgur.com/CyWImzh.png
Great article. Very useful comparison.
be careful with I/O counters in task manager!
they cover moreless all the IO activity not only disk one.
see definition on technet https://technet.microsoft.com/en-us/library/cc938567.aspx
Resource Monitor is useful for this as well. One way to get to it is the link at the bottom of the Performance tab in Task Manager.
What’s the difference between I/O Writes, Reads, Other, and I/O Writes bytes, Reads bytes, Other bytes?
This data writing issue is something, that devs really have to look forward. There is no any good reason for them to blow up customer’s SSD’s over the time.
I just today read about Firefox (session restore) writing lots of data to HD and confirmed it myself on my PC. I adjusted the Browser.sessionstore.interval setting to 60 seconds (default is 15 sec.).
However, I was shocked to find that Spotify was writing even more, A LOT more than Firefox, which was already bad. The amount of written bytes by Spotify was totally ridiculous! And I had ran the program only few days, compared to Firefox which had been ran for many more days. There’s definitely something VERY WRONG with Spotify, it writes so much more data to HD than it is required. Quick Spotify forum search yielded many topics/users complaining about this same thing. And it’s not a new thing, it has been going on for some time already. If you have SSD, don’t use Spotify on your computer.
It’s normal for any streaming service to write on disk, it’s just the caching to prevent skip.
Lot of paranoia since few days about the write on SSD, those SSD are made to be used not to stay unused in their computer case…
I’m not a spotify user but
just for streaming spotify would have tom make some use of caching anyway, ins’t it ?
Ideally this could happen in memory, but then ppl would also complain about lot of memory use.
Do you know why Spotify would write so much? Caching? Offline listening?
No, nothing like that. I have no off-line stuff, using free Spotify.
Cache is max 1 GB. Couple of days I listened to about 8 different albums. The written bytes were like at least 50 times larger than what those albums would take space. It was just ridiculous.
What I quickly read from searching the issue, the caching/off-line seems not to be the reason for the huge written data to HD.