If you using the backingfile option and wish to export your results, the application has to stop, totally close the file and then restart in order to perform the next step of exporting.

You can’t necessarily pipe this to a one-liner. One important thing to also notice is the batch script examples show using the procmon.exe with successive switches.

So, I set out to write a PowerShell script to help me automate testing. Batch files, uhm, yea I’m not going down that road. On the Windows Sysinternals forum there are some examples posted of how to use Process Monitor in batch files. It was a bit of a pain to do it all manually and, frankly, I didn’t want to do each of the applications I was testing one at a time. While doing some initial testing, I wanted to be able to run through a set of few applications all at one time. One of the recommended tools that can help provide some of that data is Process Monitor. Are changes made to the registry? Are temporary files written to a directory? Does the user need special permissions to specific folders? These are only a few of the things you need to know. Testing software for preparing installation/deployment packages or for locking down the local desktop can be quite a chore!Ī critical step in collecting data for those changes is understanding what is taking place on the system when that application runs.

Using procmon