Capture the action that produces the problem
Process Monitor records Windows activity so you can examine what happened around a failed launch, a missing setting or an unexpected file operation. The Microsoft Sysinternals utility follows file-system, Registry and process or thread events, with details such as paths, operations and results. It is most useful when you can describe and repeat the action you want to investigate.
The current verified release is 4.12, published on October 15, 2026. Microsoft's requirements list Windows 11 or later and Windows Server 2019 or later. The Windows utility is available free under Microsoft licence terms. Its archive is extracted before running the appropriate executable, and system activity capture requires elevated permissions. The separately linked Linux project should not be confused with this Windows package.
Keep the recording short and relevant
Prepare the application and note the steps that expose the problem. Start capture, perform those steps once, then stop recording promptly. A brief interval around a known symptom is usually easier to inspect than hours of unrelated activity. If old filters are present, review them before recording so a previous investigation does not hide the process you now need.
The trace can grow rapidly on a busy system. When using a backing file on disk, account for available space and the capture duration. Do not leave an unrestricted recording running indefinitely simply because the main window is minimized. Stopping capture preserves a clear endpoint and lets you analyze the collected events without continuously adding new noise.
Filter by evidence, then inspect nearby events
Use process identity, path or operation to reduce the visible set. Process Monitor's ordinary filtering is nondestructive, allowing the view to change without discarding captured information. That does not mean every saving or capture option preserves everything: deliberately dropping filtered events or exporting only a subset changes what remains available for later analysis. Choose those options with the purpose of the trace in mind.
A result such as ACCESS DENIED or NAME NOT FOUND is a clue, not an automatic repair instruction. Software can probe optional locations or encounter an expected refusal before continuing normally. Read the operation, requested path and surrounding events, and relate them to the time of the visible failure. Creating arbitrary files or granting broad permissions in response to every failed row can introduce new problems.
Connect events to the right process
The process tree helps identify relationships between processes referenced by the recording, including children created during the reproduced action. This matters when an application launches a helper and the interesting event belongs to that helper rather than its main window. For a view of what is currently running and which objects it holds, Process Explorer complements the time-based trace with a different kind of inspection.
Save the native PML log when you need to reopen the collected details in Process Monitor. A shortened export for another reader may be useful, but is not identical to retaining the full native record. Traces can reveal user names, paths and command lines, so review the intended scope before sharing them. The program supplies diagnostic evidence, not an automatic diagnosis or a guarantee that every application action was captured.