Comments

@gelatus:

You can submit them here (in general we look at comments of the "current" show to prep for the future show).

Next show will come after MIX.

@martinmine:

Look in the system logs.

@itsnotabug:

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.

@martinmine:

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.

@MagicAndre1981:

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.

@Charles: Also note that there are some early b/g routers and 1st gen N routers that were slightly out of spec. If anyone actually remembers the microsoft branded router, that would be an example of a slightly out of spec router.

@CKurt:

For 1 and 2 I will need to do more research...

For 3, when you open event viewer, look in the application log (under windows logs), and find the "Application Error" and right above it, the "Windows Error Reporting" and share the watson bucket ID.

@Bydia:

1) Disk2VHD isn't a backup solution per se... you can't go back from the VHD to the physical drive.

2) considering 1) are you trying to restore the VHD to the drive, and it is no longer booting?

3) discounting 1 and 2, are you saying that the VHD you took won't boot properly in the VPC environment?

Thanks...

Wanted to get this out there for this show... we have an email address for the show: defragshow@microsoft.com. It would be great for some of the more detailed questions to come here because we may need to have a deeper discussion about the issues you may be having... thanks!

@tom : Can you do a tracert to http://media.ch9.ms/">http://media.ch9.ms ? I am curious what paths you are taking, and where the latency may be. Thanks