Security tools

Process Explorer

Inspect running processes, open handles, and loaded DLLs with Microsoft Process Explorer. Learn a careful workflow for locked files and unfamiliar processes.

Purpose
Process inspection
Vendor
Microsoft Sysinternals
License model
free
Platforms
Windows 11
Testing status
Editorially researched

Documentation research is not a measure of detection or cleanup effectiveness.

Process Explorer is a Microsoft Sysinternals utility for examining running programs and the resources they use. Its most useful starting point is a concrete troubleshooting question: which program holds this file open, or which DLL has this process loaded?

It also belongs in an investigation toolkit, but seeing an unfamiliar process is not a malware diagnosis. A process inspector gives you observations to interpret. It does not replace antivirus protection or provide a complete infection-removal procedure.

Current release and supported scope

The official download page, checked on 6 October 2026, lists version 17.14, published on 10 September 2026. Its current client requirement is Windows 11 or higher; the server requirement is Windows Server 2019 or higher. This article covers Windows 11 rather than claiming that the newest release supports every older Windows version.

Microsoft documents running the executable directly. Obtain the package through that official page and follow its included help for the current interface. Avoid search advertisements, repackaged installers, and instructions that ask you to disable protection merely to open a diagnostic utility.

On a work or school computer, start through the supported administrator workflow. Additional privileges are a reason to understand the task first, rather than an automatic cure for a missing detail. A managed restriction can be intentional.

Processes, handles, and DLLs

Microsoft describes an upper pane with active processes and their owning accounts. The lower pane can show a selected process’s handles, or its loaded DLLs and memory-mapped files. Search connects particular handles or DLLs with the processes using them.

ObservationWhat it helps establishWhat remains uncertain
Active process and accountWhich running instance is being inspectedWhether its behavior is authorized
Open handle matching a pathA program has a reference to that resourceWhether closing the handle is safe
Loaded DLLA dependency loaded in that processWhether the dependency is malicious
Search result for a locked fileA candidate application to close normallyWhether another process will reopen it

Keep the selected process and resource in the same record. Similar names or multiple instances can otherwise lead to changing the wrong program. Capture the time of the observation as well: a running instance can disappear while you investigate, and a later instance may have different state.

A careful locked-file workflow

Suppose an ordinary document cannot be renamed because another program is using it. Save work first and check the applications that normally use that document. Search the relevant filename or path in Process Explorer, inspect the matching result, and establish which application owns it.

Close that application through its normal interface, then retry the operation. This gives it an opportunity to save data and release resources properly. If the problem involves a shared file, an update, or a background service, coordinate with the responsible user or administrator before interrupting it.

Do not force-close an arbitrary handle just because the name matches. A handle represents a resource relationship inside a program; removing it unexpectedly can produce failures that are harder to interpret than the original lock. Likewise, killing a process may lose unsaved work or interrupt an installation. If a normal close is unavailable, record the condition and use the application’s supported recovery procedure.

Finding the owner solves an ownership question. It does not establish that the file itself is safe, or that a lock was caused by malware.

Investigating an unfamiliar process

If high CPU use prompted the investigation, start with the CPU decision path. It distinguishes known workloads, browser tasks and system behavior before deeper process inspection.

Start with the symptom and the application’s expected role. A browser, updater, printer component, and security service can all create background activity. Name similarity alone is weak evidence: record the actual instance, associated resource, and origin you can establish.

If you inspect the executable’s signature through its properties, use Microsoft’s Authenticode explanation to interpret identity and integrity separately from wanted behavior. A valid publisher signature is useful context, while a missing signature is not a sufficient malware verdict.

If you identify an unwanted ordinary application, Microsoft’s supported app removal guidance is a better next step than deleting its loaded DLLs. For security concerns, use infection diagnosis and the Windows scan guide to build a fuller case.

Choose a companion for the next question

Use Autoruns to investigate why a program starts again after sign-in. Use TCPView for its current network endpoints. Use Process Monitor when the question is what file or Registry operations occurred during a particular action. These views complement each other; none supplies an automatic all-clear.

Stop when you have answered the troubleshooting question or reached a change you cannot justify. A useful handoff names the symptom, time, process, resource, and attempted normal close. This profile is researched documentation, not a hands-on product test. We have not measured detection, remediation, or performance. See the methodology for the research criteria.

Reasons to consider it

  • Connects open handles and loaded DLLs to active processes
  • Helps investigate locked files and application dependencies

Limitations to understand

  • A process list does not provide a malware verdict
  • Forced termination or handle closure can interrupt work

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy

No affiliate links are included in this build. Read our disclosure.