Security tools

Process Monitor

Trace Windows file, Registry, and process activity with Microsoft Process Monitor. Plan a bounded capture, interpret results in context, and protect sensitive logs.

Purpose
System activity tracing
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 Monitor, often called Procmon, records Windows activity for troubleshooting and investigation. It is useful when a reproducible action fails and you need to connect that action with file, Registry, or process operations. A short capture of a known problem can be more informative than a long unexplained event list.

This is a tracing utility, not an antivirus scanner. Its live display describes observed activity rather than continuous threat blocking. Capturing operations does not quarantine a file or certify that the machine is clean.

Current requirements and capabilities

Microsoft’s current product page, checked on 6 October 2026, lists Process Monitor 4.11, published on 10 September 2026. Its client requirement is Windows 11 or higher; Windows Server 2019 or higher is listed separately. This profile covers the Windows utility, not the separately linked Linux project.

The documented features include file-system, Registry, and process/thread activity; event properties; filtering; process details; a process tree; native saved logs; and advanced boot logging and stack inspection. Obtain the package through Microsoft and use the included help for current controls.

Keep the investigation limited to normal actions you can reproduce safely. Do not execute a suspicious download to generate an interesting trace. On a managed device, log collection and administrative access should follow the organization’s support process.

Plan a capture before starting

Write down the symptom, the application, and the one action that reproduces it. For example, a known application’s save operation may fail at a particular destination. That is a better investigation scope than collecting everything until an unusual line appears.

Capture decisionPractical starting pointWhy it matters
QuestionOne application action and expected resultDefines which events are relevant
TimingBrief baseline, then one reproductionSeparates background activity from the symptom
Process scopeConfirm the actual running instanceAvoids unrelated programs with similar names
End conditionStop after the result appearsLimits volume and private information
Retained evidenceNative trace plus a short reproduction notePreserves context for later review

Begin recording shortly before the action, perform it once, note the time and visible result, then stop capture. Repeating it several times without marking boundaries can make cause and consequence difficult to separate. A failure that does not reproduce is still useful to record; do not imply the trace contains the missing event.

Choose a local storage location with enough space and controlled access. Captures can grow quickly. Do not leave recording enabled indefinitely or turn on boot logging as a first response to an ordinary application problem.

Filter without confusing the evidence

The product page describes non-destructive display filtering. Narrowing the view can help isolate the process, path, or time interval you need. A visible subset is not necessarily the full capture.

Microsoft’s historical Defrag Tools training episode also discusses a Drop Filtered Events option. That 2012 training is context for the distinction, not proof that every current control is unchanged. Check the present help and selected settings: dropping events during capture and hiding them afterward have different consequences for what can be recovered later.

Keep the original trace when a filtered view might omit related activity. Describe any capture restrictions in a handoff so the next reader does not interpret an absent event as proof that it never happened. Native logs preserve richer investigation context than a screenshot of a few rows.

Interpret a sequence, not a lone failure

A failed lookup can be part of a program searching several locations before succeeding. A denied operation may reflect permissions or a supported protection policy. These are possibilities to investigate, rather than automatic explanations for every failure.

Match an event to the symptom, inspect neighboring operations, and consider whether the application later succeeded through another path. Separate an observed result from your explanation of it. A file write or Registry change can belong to normal software; the operation alone does not establish malicious intent.

Do not weaken folder permissions, disable protection, or delete Registry keys solely to remove an error from the trace. Establish the application’s expected behavior and use its supported repair route. Microsoft’s Windows Security settings guidance provides a separate way to check protection providers if security status is the actual concern.

Save useful context and choose the next step

Treat logs as potentially sensitive. Paths, usernames, process arguments, and recorded operations may reveal details about documents and installed software. Inspect what you plan to share and use an appropriate support channel; this profile does not ask you to upload a trace.

Process Explorer helps with a resource currently held open, Autoruns with configured startup, and TCPView with current endpoints. If the investigation points toward malware, move to diagnosis and supported scanning rather than interpreting Procmon as a cleaner.

This article received a documentation and editorial pass on 6 October 2026. We have not collected a test trace, run malware, or measured Process Monitor performance. See the methodology for the research criteria.

Reasons to consider it

  • Detailed event traces connect operations to processes and paths
  • Native logs support later investigation

Limitations to understand

  • Unbounded captures can become large and difficult to interpret
  • Logs may contain private paths and command lines

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.