Comments on: Using the Problem Steps Recorder Tool in Windows 7

By: Damian

Damian — Thu, 11 Feb 2010 03:05:27 +0000

I hear what you guys are saying. I’m an Engineer at an Accounting Firm, and I find it’s impossible to get my users to send me screen shots or the like.

One thing you should consider is combining the power of the PSR with VBScript or PowerShell. I have a script built that starts the PSR in record mode, captures the output to a local ZIP file, and then when the user closes the PSR, it automatically emails the result to the Help Desk. This is a great way to eliminate “I dont remember what the error was” from the list of user excuses, eliminates the need for “print screens” to capture the error, and is accurate data when passing an incident up the support chain.

By: Easily Record Troubleshooting Steps In Windows 7 | PCMech

Easily Record Troubleshooting Steps In Windows 7 | PCMech — Wed, 02 Dec 2009 07:32:33 +0000

[...] by hand or trying to walk someone through it over the phone, Windows 7 has a nifty tool called the Problem Steps Recorder you can use. Click Start, type PSR.EXE and press ENTER. This starts the Problem Steps [...]

By: vignesh

vignesh — Tue, 17 Nov 2009 06:30:36 +0000

PSR concept is really a new tech for all users. My friend wants to install application software in his systems. On that time it is been so useful to guide him. PSR is really an good gift for all.

By: ashish

ashish — Wed, 07 Oct 2009 19:30:18 +0000

it’s a great tool, I must say….great job !!!

By: marsha

marsha — Mon, 20 Jul 2009 05:03:10 +0000

Isn’t this the same recorder we used to have in Windows 3.1?

What’s new about this tool?

By: Mitch

Mitch — Mon, 02 Feb 2009 19:12:32 +0000

@Brett What do you suggest? A bug free OS? Impossible. Software is made by humans and therefore has problems. It would be impossible to create an operating system which has can never crash and naive to assume it should be. Beyond that simple assumption, it is also for third party applications, which are not created by microsoft. It is better to try and help the developers to fix the bug (by providing detailed explanations) than to just whine about errors. (And if you think windows is alone in bug reporting, check out the avalible options for linux and os x (gdb, ltrace)

By: Andy

Andy — Thu, 29 Jan 2009 10:21:46 +0000

This is amazing. Problems are not always the fault of the O/S… it is quite often “user-error” (and/or bad UI design). This will be an invaluable tool for developers that have to use “customers” as their “testers”. It is a simple application to run, so the customers can easily use it to produce documents containing a step they might have missed–or something else they might have done incorrectly while trying to use an app. Pretty cool.

By: Tony

Tony — Mon, 19 Jan 2009 08:56:25 +0000

This tool looks like it will be invaluable. So long as you can get users to run it, rather than just complaining and saying ‘I don’t know anything about computers, can you come and look at it’ only to find they were clicking the wrong button.

Maybe Microsoft could include it as a more automatic feature. Like their stack trace reports they send themselves, a ‘black box recorder’ style app for enterprise would be good. Ie. It could be running always, keeping the last few minutes actions, then if a crash occurs, allows you to send it to a support system. Or if it is not a crash, but just a problem, an icon could be clicked in the bar at the bottom and the report created from that.

Actively getting someone to use it will be an issue.

By: Ramesh Srinivasan

Ramesh Srinivasan — Fri, 16 Jan 2009 04:03:58 +0000

Hi Brett, Using PSR one can record problem steps in third-party apps as well. I’ve been waiting for such a tool for a long time.

By: Brett

Brett — Thu, 15 Jan 2009 17:08:46 +0000

If Windows didn’t have so many problems we wouldn’t need a problem step recorder. I think it is sad that in the latest OS from M$ they are expecting that you be troubleshooting problems they built in a recorder so that you can keep track of the problems. What happens if the problem step recorder has a problem. If there something that records the steps to reproduce the problems with the problem step recorder?