Description

Microsoft tech troubleshooter extraordinaire Gov Maharaj and I help walk you through troubleshooting solutions to your tech support problems. If you have a problem you want to send us, you can use the Problem Step Recorder in Windows 7 (see the show for details on how) and send us the zip file to DefragShow@microsoft.com. We will also be checking comments for problems, but the email address will let us contact you if needed.

On tonight's episode:

00:40 David Young fixes his Homegroup problem. 02:10 When to re-registering DLL's.02:54 Troubleshooting Windows 7 Shutdown delays. 06:30 How to collect data to send us for problem solving.11:50 Troubleshooting an MSI installation, turning on verbose logging for troubleshooting.17:30 About the Program Compatibility Assistant. 18:50 Troubleshooting a Windows Update failure. 22:18 Using the Debugging Tools for Windows.

If you recall from the show, I did in fact state to not randomly start changing the state of the services. However, what I did say was to look at if there was anything in the event to indicate a service was taking a long time to shutdown, or if it were crashing during the shutdown.

The performance tools for windows are a great set of tools to use to troubleshoot these issues, and that was something I was going to go into at a later date.

There are countless number of reasons why a system may be slow to shutdown, and I can't possibly enumerate them all.

Thanks for your feedback, but I still stand by the recommendations stated, as well as understanding that there are other tools available to do more indepth analysis.

@MagicAndre1981: I've never run into anyone that set their Clear Page File At Shutdown flag without knowing what it does or what it impacts. Then again, I don't have to deal with people that tattoo their face, put hot sauce in the wrong hole, or perform other inexplicable acts upon themselves.

Linux and OSX have a different OS model. If you compare a clean Win7 box to an OSX box shutting down times should be very comparable. It also depends on whether or not you are on a domain, the hardware, etc.

i too love where this show is going! great job so far. i'd love to see more detail in debugging issues with error codes returned from application logs. seeing someone else's thought process and workflow helps a lot! thank you!

As you can imagine, an actual debug session may be a little too long and/or dry to go over on the show. However, if you (and by you, I mean anyone) send some watson bucket IDs of crashes you have seen, I can pick a couple to go over.

You can get the watson bucket ID by going into the event viewer, find the "Application Error" event, then look at the "Windows Error Reporting" event right above it. There should be a non-zero bucket ID (assuming that you submitted the issue). Try and pick something that happened in the past 30-60 days.

I like this show a lot. It's both interesting and helpful. One request though; I can't always read what is on your display so when you type a path to a log or point out a file name could you also verbalize it?