Posted By: Charles | Sep 3rd @ 9:41 AM | 51,734 Views | 7 Comments
Windows Development Manager Melur Raghuraman and team have taken troubleshooting and diagnostics to a whole new level in Windows 7. For one thing, Windows 7 uses managed code "natively" as PowerShell has become the de facto language used for creating diagnostic algorithms that live inside of diagnostic packages. So, when something goes wrong eventually a PowerShell script runs and diagnosis happens.

You've probably already noticed the information flag that appears in your task bar notification area when Windows wants to tell you something important. Well, in order for Windows 7 to inform you of a problem and its solution it must first diagnose the issue and collect troubleshooting steps. Sometimes, and more so than ever before, Windows will simply fix the problem and let you know about it - this is a trend that will only become more common over time and with each iteration of Windows going forward. This troubleshooting fabric has both client and server (cloud) components.

How does this all work, exactly? What's the story?

Tune in. Lots to learn here. The new troubleshooting and diagnostics capabilities in Windows 7 marks a signficant step forward in the evolution of Windows supportability. Of course, you, the human user, can write your own diagnostic scripts - so you'll be more efficient  when you need to diganosis and then fix some computer problem.
Rating:
2
0

The regular WMV link is almost 600MB. The high version is almost 1GB. Can we have a "low" option? Not all of us are connecting with ultrafast connections.

Thanks, Charles. Can't play MP4s here at work since I don't have the codec, but it's nice to know that there is a smaller sized option.

 

Watching the video now...I think it's great that anyone can make their own diagnostic scripts. Once more Win 7 machines are out there, this will make my sidejob of cleaning up computers very efficient.

 

The live update is really cool too, as the causes of problems can change as time goes by.

ZippyV
ZippyV
Fired Up

Indeed, very interesting that we can create our own troubleshooting wizards. Now we just need a video with demonstration on how to do it.

 

 

EDIT: Looks like a development example is already in the video. Nice job, Charles.

 

More info on MSDN: http://msdn.microsoft.com/en-us/library/dd323778(VS.85).aspx

ZippyV
ZippyV
Fired Up

Do they have a blog?

Microsoft Communities