Hi Everyone!

My name is Andy Luhrs, and I'm one of the Program Managers on Debugging Tools for Windows. Our team has decided to start up a blog to get some more tips and tutorials out to people around updates and changes to our debugging tools (WinDbg, kernel debugging, AppVerifier, etc.) There's tons of blogs about debugging difficult or weird issues (Raymond's is my favorite), and the main goal of this isn't to cover that type of stuff. The plan is to have a few people across our team contribute, so expect to see a variety of perspectives. We're largely aiming to look at and highlight some of the under the hood type changes that doesn't fit in our normal MSDN documentation, and talk about features in the preview releases of the SDK that don't have full documentation written for them yet. We'll do our best to update our blog posts to point to official documentation when it's available.

So here's a few quick tips to get started:

  1. Stay up to date! We make a lot of changes behind the curtains that improve command performance, reliability, and output. It's definitely worth staying on the SDK preview versions of WinDbg when they're available.
  2. Try running 'dx Debugger' and click around the DML links and learn what's the in the namespaces there. We'll be going a bit more in-depth on what's possible with 'dx' and what some of the more interesting namespaces are in future posts. Or even better, try 'dx -r3 @$cursession.Devices.DeviceTree' while in a kernel session.
  3. If you're using something like a laptop or Surface, you might hate that it doesn't have a "Break" key. We added Alt+Delete as an alternative key combination to break-in.

We're aiming to make posts with every SDK preview release that has major changes, when we have a question that gets asked frequently, and when we have good tutorials or tips that we want to share out. Feel free to use comments to ask for elaboration or details, and we'll do our best to follow-up.


-Andy Luhrs


Comments (11)
  1. Oleg Gitsa says:

    0: kd> dx -r1 @$cursession.Devices.@”DeviceTree”
    @$cursession.Devices.@”DeviceTree” :
    Error 0x80004005 occurred.

    1. Andy Luhrs says:

      There was a typo in the original post, the actual command is “dx -r3 @$cursession.Devices.DeviceTree”, but that typo wouldn’t give you that error. What version of the debugger are you using?

      1. Oleg Gitsa says:

        0: kd> dx -r3 @$cursession.Devices.DeviceTree
        @$cursession.Devices.DeviceTree :
        Error 0x80004005 occurred.
        0: kd> version
        Windows 10 Kernel Version 10586 MP (2 procs) Free x64
        Built by: 10586.494.amd64fre.th2_release_sec.160630-1736
        Machine Name:
        Kernel base = 0xfffff800`b0e0b000 PsLoadedModuleList = 0xfffff800`b10e8cf0
        Debug session time: Fri Aug 12 12:33:52.474 2016 (UTC + 3:00)
        System Uptime: 0 days 0:24:01.273
        Remote KD: KdSrv:Server=@{},Trans=@{COM:Port=\\.\pipe\10-64-P-b10586-EN,Baud=19200,Pipe,Timeout=4000,Resets=2}

        Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
        Copyright (c) Microsoft Corporation. All rights reserved.

        command line: ‘windbg.exe -k com:pipe,port=\\.\pipe\10-64-P-b10586-EN -WF E:\Work\Debug\WinDBG\10-64-P-b10586-EN.wew -loga E:\Work\Debug\WinDBG\10-64-P-b10586-EN.log -c “g”‘ Debugger Process 0x44A4
        dbgeng: image 10.0.10240.16399, built Thu Jul 23 04:51:27 2015
        [path: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\dbgeng.dll]
        dbghelp: image 10.0.10240.16399, built Thu Jul 23 04:49:35 2015
        [path: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\dbghelp.dll]
        DIA version: 40116
        Extension DLL search Path:
        C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\WINXP;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winext;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winext\arcade;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\pri;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64;C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winext\arcade;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Skype\Phone\;C:\Windows\system32\config\systemprofile\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\WinDDK\8.0\Windows Performance Toolkit\;C:\Program Files (x86)\Windows Phone TShell\;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\
        Extension DLL chain:
        dbghelp: image 10.0.10240.16399, API 10.0.6, built Thu Jul 23 04:49:35 2015
        [path: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\dbghelp.dll]
        ext: image 10.0.10240.16399, API 1.0.0, built Thu Jul 23 04:50:27 2015
        [path: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winext\ext.dll]
        exts: image 10.0.10240.16399, API 1.0.0, built Thu Jul 23 04:49:59 2015
        [path: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\WINXP\exts.dll]
        kext: image 10.0.10240.16399, API 1.0.0, built Thu Jul 23 04:49:56 2015
        [path: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winext\kext.dll]
        kdexts: image 10.0.10240.16399, API 1.0.0, built Thu Jul 23 05:05:16 2015
        [path: C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\WINXP\kdexts.dll]

        1. Andy Luhrs says:

          You’re using a debugger that’s a bit over a year old. Installing the most recent SDK should fix your issue, you can find it at https://go.microsoft.com/fwlink/p/?LinkID=822845

          1. Oleg Gitsa says:

            Doesn’t help.
            0: kd> version

            Microsoft (R) Windows Debugger Version 10.0.14321.1024 X86
            0: kd> dx -r3 @$cursession.Devices.DeviceTree

            The error disappeared, but the command output is empty.

  2. e3bd87eb6d says:

    Hi, looking forward to your upcoming posts.

    One question I have is how developers will be able to obtain checked OS builds of current releases… any word on that?

  3. pfautsch says:

    Andy, I am seeing a problem with the new build 14901. The Miracast drivers are missing or the ability to use wifi to connect to TVs is missing. Do you have a work around for this??

    1. Andy Luhrs says:

      I’d recommend directing this feedback to the Feedback Hub or forums, this blog is focused on Debugging Tools for Windows: https://msdn.microsoft.com/en-us/library/windows/hardware/ff551063%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

  4. svenkat9 says:


    I just commented on your episode in Channel9’s Defrag Tools. It is not directly related to your team, but if you could give a brief overview to get started on LINQ & Natvis, it will be great!

    Hope this blog will be great like other great blogs out there! Good luck!

  5. Ben says:

    Welcome to the blogging world. I just watched you guys on Defrag Tools and found out about this blog.
    I use WinDbg almost daily in my work, so I’m sure you’re blog will be most useful to me.
    It was never easy following the scattered crumbs of information from the Debugger Tools team, so it’ll be great to have direct communication here.
    Looking forward to upcoming posts.

  6. Lee Cheng Yi says:

    Looking forward for most articles!!

Comments are closed.

Skip to main content