ProcessMonitor 1.1 released by SysInternals

[mouser]

Thos of you who have heard about Filemon and Regmon but not the newer Process Monitor need to check this out.  Process Monitor is a great tool for watching what processes do in the background..

Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. It combines the features of two legacy Sysinternals utilities, Filemon and Regmon, and adds an extensive list of enhancements including rich and non-destructive filtering, comprehensive event properties such session IDs and user names, reliable process information, full thread stacks with integrated symbol support for each operation, simultaneous logging to a file, and much more. Its uniquely powerful features will make Process Monitor a core utility in your system troubleshooting and malware hunting toolkit.

http://www.microsoft.com/technet/sysinternals/utilities/processmonitor.mspx

[f0dder]

It's a pretty great tool indeed!

I had it lock up heavily on me (non-BSOD, but a windows that wouldn't shut down or start new apps) in combination with visual studio debugging. Can't remember what exactly did it, and I don't want to try and reproduce it , just a word of warning: be careful if you're running a debugger at the same time as ProcMon.

[urlwolf]

Same here. No VS debugging here.
It is a zombie process that not even windows process explorer can kill.
What did you do to kill it?

[Hirudin]

Sorry for the short post, but if it interests anyone, 1.12 is out.

[Curt]

Process Monitor is now at version 2.8. I have not been able to find what changes have been done, from 2.7.

Runs on:
   * Client: Windows XP SP2 and higher.
   * Server: Windows Server 2003 SP1 and higher.

Introduction

Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. It combines the features of two legacy Sysinternals utilities, Filemon and Regmon, and adds an extensive list of enhancements including rich and non-destructive filtering, comprehensive event properties such session IDs and user names, reliable process information, full thread stacks with integrated symbol support for each operation, simultaneous logging to a file, and much more. Its uniquely powerful features will make Process Monitor a core utility in your system troubleshooting and malware hunting toolkit.

Overview of Process Monitor Capabilities:

Process Monitor includes powerful monitoring and filtering capabilities, including:

   * More data captured for operation input and output parameters
   * Non-destructive filters allow you to set filters without losing data
   * Capture of thread stacks for each operation make it possible in many cases to identify the root cause of an operation
   * Reliable capture of process details, including image path, command line, user and session ID
   * Configurable and moveable columns for any event property
   * Filters can be set for any data field, including fields not configured as columns
   * Advanced logging architecture scales to tens of millions of captured events and gigabytes of log data
   * Process tree tool shows relationship of all processes referenced in a trace
   * Native log format preserves all data for loading in a different Process Monitor instance
   * Process tooltip for easy viewing of process image information
   * Detail tooltip allows convenient access to formatted data that doesn't fit in the column
   * Cancellable search
   * Boot time logging of all operations

The best way to become familiar with Process Monitor's features is to read through the help file and then visit each of its menu items and options on a live system.

http://technet.microsoft.com/sysinternals/bb896645(en-us).aspx
http://majorgeeks.com/Microsoft_Process_Monitor_d5553.html

[f0dder]

Curt: SysInternals has a RSS feed - quoting from Nov.03.2009:

Process Monitor v2.8: Displays new Windows 7 CreateFile options, includes file-delete operations in the Category filter’s Write subcategory, and displays names for more IOCTLs and result codes.

[mediaguycouk]

I used to use this program all the time to see which svchost.exe process was at 99.9% CPU and then bury down to see which service was causing it. If this is still possible I can't find a way of doing it.

I'll have to see if I can route out my old one.