A Windows 11 desktop displays Task Manager and Process Explorer side by side on a monitor.
Task Manager is fine for a quick look. When a PC stutters while the CPU graph sits at 12%, though, you need a tool that shows more. MakeUseOf writer Afam Onyimadu argues that Microsoft's free Process Explorer, part of the Sysinternals suite, is that tool. His account is useful, but a few parts need tightening before you copy his workflow.

A Windows 11 desktop displays Task Manager and Process Explorer side by side on a monitor. What Process Explorer is, and what's current​

Microsoft's documentation currently lists Process Explorer v17.21, published November 5, 2026, at a 3.7 MB download. The Sysinternals "What's New" feed shows that v17.2 arrived on October 15. That release added process efficiency mode support, persistent process activity history, live kernel memory dump creation, a process memory map explorer, a Devices page in System Information and NPU monitoring. The same feed notes that Process Explorer now has a macOS port. That is a curiosity for Windows readers, not something you need.

Version numbers drift between third-party download sites. Several mirrors show older builds such as 17.14, so get the tool from Microsoft's Sysinternals page. Microsoft lists Windows 11 and higher as the client requirement.

The core design is simple. The top window lists the currently active processes and their owning accounts. The bottom window shows either the handles a selected process has open, or the DLLs and memory-mapped files it has loaded. A search function finds which processes have particular handles open or DLLs loaded. That is why it is the classic answer to "what is locking this file?"

Getting started​

Microsoft's install instruction is short: simply run Process Explorer (procexp.exe). There is no installer. The workflow below follows Onyimadu's account, with the Microsoft-documented parts marked.

  1. Download Process Explorer from Microsoft's Sysinternals page, extract the ZIP and run procexp.exe. This portable route is the one the author describes. Sysinternals Suite is also available from the Microsoft Store, and Microsoft says graphical tools such as Process Explorer are added to the Start menu.
  2. Launch it elevated when you want to inspect system-level processes. Microsoft's own troubleshooting steps for thread inspection begin with running Process Explorer as an administrator. That doesn't prove elevation is required for every use. It does mean you shouldn't be surprised if some details are hidden without it.
  3. Add columns. Microsoft says you can right-click a column and choose Select Columns to pick what's displayed. Onyimadu added I/O Read Bytes and Private Bytes during his own investigation.
  4. If you want it to replace Task Manager, he says to use Options, then Replace Task Manager. That makes Ctrl+Shift+Esc open Process Explorer, and unchecking the option reverses it. Microsoft's Defrag Tools episode lists this option under the Options menu, but I haven't verified the exact behavior on the current build. Try it on a non-critical machine first.

The author's three anecdotes​

Onyimadu reports three cases from his own PCs:

  • A browser process reading from disk nonstop. Closing the tab fixed the slowdown.
  • Periodic spikes from Windows Defender scanning a large backup folder. He scheduled scans for night rather than disabling Defender.
  • A thread in Windows Explorer pinned at 100% CPU. He ended the process to avoid a restart.

These are his experiences, and nothing independent confirms them. They are plausible, and they show the kind of pattern-spotting the tool supports. They should not be read as general findings.

One caution on the first case. I/O Read Bytes is a cumulative count, not a live latency measure. A large number shows that a process has read a lot, not that the disk is the bottleneck right now. The better habit is to watch whether the figures change during the stutter and whether they line up with it. Treat the column as a lead, not a verdict.

Going deeper: threads and stacks​

For stubborn cases, Microsoft documents a more advanced route. Right-click a process, choose Properties, open the Threads tab, then select a thread and click Stack to see the functions it is running. Microsoft's guide says you can get better stack results by configuring symbols. That means installing Debugging Tools for Windows, pointing the Dbghelp.dll path at that install, and using Microsoft's symbol server.

This is not a beginner step. It is how you move from "this process is busy" to "this is the code path it is busy in." Microsoft also notes that the stack display doesn't update automatically. You have to refresh it, and the minimum refresh interval is one second. For finer-grained timing, Microsoft points to Windows Performance Recorder and Windows Performance Analyzer.

The VirusTotal claim needs a correction​

The MakeUseOf piece says a file is "considered safe" if no security vendors flag it. That is too strong.

VirusTotal's own documentation carries a warning: a missing report, a pending analysis, or zero detections is not a guarantee that an item is safe. Read a clean score as one signal. A new or targeted malware sample can sit undetected, and a lone detection on an obscure file can be a false positive.

Hashes versus uploads matters too. VirusTotal's documentation notes that hash lookups do not upload files. Microsoft's Sigcheck page draws the same line: it can query VirusTotal by file hash, and it offers a separate option to upload files not previously scanned. I didn't find Microsoft's Process Explorer page documenting the right-click "Check VirusTotal.com" step, so confirm that menu in your build. Expect a prompt to accept VirusTotal's terms of service.

The author's path advice is sound as a first filter. A process named svchost.exe running from a Downloads folder deserves suspicion. Treat that as a reason to investigate, not as proof of malware. Check the digital signature and the parent process as well.

A cautious troubleshooting routine​

  1. Reproduce or catch the slowdown with Process Explorer already open.
  2. Sort by the relevant columns and look for the process whose numbers change when the lag hits.
  3. Use the lower pane in handle or DLL mode on that process to see what it has open or loaded.
  4. Open the Threads tab only if you need to know which thread is responsible.
  5. Check unfamiliar processes by path, signature and a VirusTotal lookup, and weigh the results together.
  6. Close a misbehaving app normally if you can. Ending a system process, including the "stuck Explorer" fix from the story, can cause problems. Save your work first, and don't kill things you can't identify.

Verdict​

Process Explorer is a worthwhile install for anyone who has stared at an innocent-looking Task Manager during a stutter. Microsoft's documentation backs its core strengths: the process view, handles and DLLs, configurable columns, and thread stacks. It also backs the recent additions in v17.2.

The article's claims that every lag has a trigger the tool reveals, and that Task Manager becomes useless afterwards, are enthusiasm rather than documented fact. Task Manager still wins for a quick glance. Process Explorer wins when you need to know which process, handle, DLL or thread is involved. It collects evidence, and you still have to interpret it.

 

References

  1. I set up a free system monitor that actually tells me why my PC is slow MakeUseOf 2026-11-18T16:31:18+00:00
  2. Process Explorer - Sysinternals | Microsoft Learn learn.microsoft.com
  3. Troubleshoot issues using Process Explorer - Windows Server | Microsoft Learn learn.microsoft.com