


You can filter out unwanted processes by right-clicking on a 'process name' and choosing Exclude: Now you have to minimize the output of the trace by only showing the processes you want to see. Disable registry, network and process trace by pressing these buttons: In most trouble shooting scenarios, file tracing is enough. When started, MPM will automatically start showing all processes currently running, with registry, file, network and process activity. On first run, you will have to confirm to a license agreement. The tool does not have to be installed, just run it from the new location.

Just copy the contents of the archive file to a new folder on the PC or server where you want to trace the problem, for example to C:\Program Files (x86)\Microsoft Process Monitor. Please note that MPM is not an Exact tool and not supported as such. Microsoft Process Monitor (MPM) can be used to trace problems related to file or registry access, or to show which process may be the last to execute before an error occurred.
