There is a bunch of information on the web about PSR and one of the best is this video on CNET: http://cnettv.cnet.com/2001-1_53-50005144.html as you can see a demo of the tool working for an end-user perspective, it behaves differently when invoked by WER as described below. The key difference is that WER doesn’t collect screenshots.
From an error reporting perspective we plan on exposing this via the WER Services. The concept is that if you aren’t able to use standard mini-dumps or heap dumps to find the source of the problem, WER Services will allow the PSR tool to be run (with user consent)
Example of screen-shot shown to user:
When we enable an error Bucket to collect PSR data, here is the workflow:
Other links and blog posts:
Problem Step 1: (3/27/2009 7:53:51 PM) User right click on "user consent (editable text)" in "Problem Steps Recorder (PSR.exe) + Windows Error Reporting = Another tool to help find solutions to software defects - Windows Live Writer"
Problem Step 2: (3/27/2009 7:53:53 PM) User left click on "Hyperlink... (menu item)"
Problem Step 3: (3/27/2009 7:53:55 PM) User keyboard input in "Insert Hyperlink" [... Enter]