Andrew Richards

As a user, look at the .exr -1, .ecxr and k output.

!analyze does the same (via APIs) thing internally to decide what type of analysis to run.

You can jump to the "!analyze -v" output, if you want, and skip the other commands -- it's easier to understand the "!analyze -v" output if you have some context to base it on.

@eschwabe:!analyze considers the last exception record (it does it through the API : IDebugControl3::GetLastEventInformation) - you won't see it running the command.

If you ever find a case where !analyze doesn't seem to be considering it, email us and we'll look into it.

All of the new !black* commands are great to leverage for any hang related analysis.
The blackbox secondary streams are added by the hang bugcheck codes (E2, 1C8, etc.).
!analyze reads the data to aid decisions.

@Peter:Yes, the plan is to do more tools that aren't debugging based.

Debugging is lots of small topics - and that's what drove the show's creation.

Such an awesome team and workspace to tape in -- looking forward to taping many new episodes in 2018.

@j1n1:WinDbg doesn't have intrinsic CLR support... it's only by extensions (SOS, etc.).

Visual Studio does have intrinsic CLR support -- but doesn't currently support TTD.

BTW, USB-A is the rectangle connector. USB-B is the D connector in regular, mini (old cameras) and micro (phones) sizes, and USB-C is the new rectangular one with the rounded corners.

USB 2 requires a client and server, and thus uses A+B connectors.

USB 3 is bidirectional, allowing C at both ends. Most data cables are A to C though. Because C is both, that is why it can drive HDMI, etc.

@wellisolutions: It's the 2nd edition.

@Matt:When you device is Workplace managed, the tab shows up, to indicate if the fike is personal or corporate owned. 

@Templaar:Yes -- definitely are still alive :) We've got a few shoots in edit now.

RS2 end-game kept me (Andrew) too busy to find time for it, Chad's been flying the world a lot to talk to Partners, and //build/ closed the Channel 9 studios (they do 300+ pre-shoots) for weekly shows.

Keep the show ideas coming - to defragtools@microsoft.com -- after 170+, we're running out of tools that haven't been covered -- and that we can find an expert for.

If you'd like to see re-visits (second deep-dive) of certain tools -- we can do that for sure.

And I'm always up for just showing random debugging tips.

@Peter: Yes, just clone it over and it'll work.

@LeoJBG: I'd just copy bash.ico into c:\windows -- and skip trying to get anything more complex to work.