{"id":184,"date":"2009-02-01T17:13:00","date_gmt":"2009-02-01T17:13:00","guid":{"rendered":"http:\/\/windowsvj.com\/wpblog\/?p=184"},"modified":"2009-02-01T17:13:00","modified_gmt":"2009-02-01T17:13:00","slug":"windows-7-tool-problem-steps-recorder","status":"publish","type":"post","link":"http:\/\/windowsvj.com\/wpblog\/2009\/02\/windows-7-tool-problem-steps-recorder\/","title":{"rendered":"Windows 7 Tool: Problem Steps Recorder"},"content":{"rendered":"<p><!-- google_ad_section_start(weight=ignore) -->   <!-- google_ad_section_end -->   <\/p>\n<p><a href=\"http:\/\/blog.taragana.com\/wp-content\/uploads\/2009\/01\/windows-7.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-medium wp-image-3995\" title=\"windows-7\" src=\"http:\/\/blog.taragana.com\/wp-content\/uploads\/2009\/01\/windows-7-300x300.jpg\" alt=\"\" width=\"300\" height=\"300\"><\/a>One of the most troublesome issues of troubleshooting is to find out exactly how it happened and for what. Obviously, some processes are non-recoverable. For them you can not repeat the process and risk another hardware just because a troubleshooter wasn&#8217;t able to understand where did it err. So what do you do depict the error ditto to original. Here is a wonderful tool for Windows 7. A feature new to Windows 7, called <strong>Problem Steps Recorder<\/strong> looks to be the missing tool for documenting where it all goes wrong.<\/p>\n<p><span id=\"more-3994\"><\/span><\/p>\n<p>The tool is just an advanced version of the screen capture software but with other in- depth functionalities. Think of it as an automated <strong>Print Screen<\/strong> plus a little monkey in the background documenting all the mouse clicks, key strokes and gathers some technical reading material, who then ties up everything in a neat box and saves the results. The neat little box you get is a zipped MHTML report page which can be sent off directly to the help desk.<\/p>\n<p>Try it. Prevention is always better than cure. But when its about Windows, you know that cure is the only way to go. So let&#8217;s strengthen it.<\/p>\n<h2><font size=\"3\">How To Get Started<\/font><\/h2>\n<ul>\n<li>Go to Start Menu -> <strong>Run<\/strong>.<\/li>\n<li>type and select <strong>psr.exe<\/strong> and ENTER.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>One of the most troublesome issues of troubleshooting is to find out exactly how it happened and for what. Obviously, some processes are non-recoverable. For them you can not repeat the process and risk another hardware just because a troubleshooter wasn&#8217;t able to understand where did it err. So what [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[],"class_list":["post-184","post","type-post","status-publish","format-standard","hentry","category-windows-7"],"_links":{"self":[{"href":"http:\/\/windowsvj.com\/wpblog\/wp-json\/wp\/v2\/posts\/184","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/windowsvj.com\/wpblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/windowsvj.com\/wpblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/windowsvj.com\/wpblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/windowsvj.com\/wpblog\/wp-json\/wp\/v2\/comments?post=184"}],"version-history":[{"count":0,"href":"http:\/\/windowsvj.com\/wpblog\/wp-json\/wp\/v2\/posts\/184\/revisions"}],"wp:attachment":[{"href":"http:\/\/windowsvj.com\/wpblog\/wp-json\/wp\/v2\/media?parent=184"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/windowsvj.com\/wpblog\/wp-json\/wp\/v2\/categories?post=184"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/windowsvj.com\/wpblog\/wp-json\/wp\/v2\/tags?post=184"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}