You can filter anything from Architecture, Authentication ID, Category, Command Line, Company, Completion time, Date & Time to Version.Īnother example where filtering is important is when we want to find out if a particular EXE contains an MSI that is extracted and executed during the installation. By filtering operations, you can easily detect your issues on your system/application. Cool right?įiltering operations is one of the most important and powerful aspects of Procmon. This will ensure that only the Explorer.exe will appear in the capture, and with the registry operations filter, you will now see only what Explorer.exe operations are happening in the registry. Go to Include and click on the “Add” button.In this window, we can configure to display the entities as follows: In the main Process Monitor window, we see a list of all system operations along with their exact time, process name, ID, and the result of every operation: It is particularly helpful when you need to track which application or process accesses a file or a registry key. You can use Process Monitor to track system and application activity and troubleshoot some product issues.

A long list of improvements are also added, including process monitoring, monitoring of files loaded into system memory, improved filters, process activity details, and more. Process Monitor is a Windows system monitoring tool that shows files, accessed registry keys, and active processes. We will discuss its prerequisites and share how you can get started with it.

We mentioned Process Monitor in our MSI Packaging Training free e-book but this time around, we want to explore it further. Process Monitor is probably one of the most used tools by IT Pros to debug applications and check installations. Getting started with Procmon: The Beginner’s Guide to Monitoring Windows Systems

Process monitor windows server