Windows 10: New WinDbg available in preview for Windows 10

Page 1 of 2 12 LastLast

  1. Posts : 31,394
    64-bit Windows 10 Pro build 18219
       28 Aug 2017 #1

    New WinDbg available in preview for Windows 10

    We are excited to announce a preview version of a brand new WinDbg. We've updated WinDbg to have more modern visuals, faster windows, a full-fledged scripting experience, built with the easily extensible debugger data model front and center. I'll start this by saying that WinDbg Preview is using the same underlying engine as WinDbg today, so all the commands, extensions, and workflows you're used to will still work just as they did before.

    Getting started

    I know a lot of you are going to want to dive right in and try it out, here are the things you should know before doing so.

    • Installation - You can install the WinDbg Preview from the store if you have Windows 10 Anniversary Update or newer at - WinDbg Preview uses some features from the Windows 10 Anniversary Update, so thatís required for now. The Windows Store lets us release bug fixes and updates to you faster than we've ever been able to before, so make sure to stayed tuned to our blog and MSDN to learn the latest about the preview.
    • Feedback - Familiarize yourself a bit with the Feedback Hub! We've still got a long way to go before we cover all WinDbg features, and we'll be using the Feedback Hub to help us prioritize what you want us to work on! The Windows Insider website has a great overview on how to give good feedback - Once you've read that, just hit the 'Feedback Hub' button on the home ribbon.
    • Questions - You're bound to have a lot of questions feel free to post them on this blog post, send feedback in the Feedback Hub, or tweet @aluhrs13 and I'll do my best to answer. We'll be posting an FAQ on our blog sometime in the upcoming weeks.
    • Documentation - We've got some early documentation up on MSDN that's preliminary and subject to change at, you can give us feedback or propose edits to that documentation by hitting "Comments" or "Edit" on any page. Also keep your eyes on our MSDN blog - - for more updates and tips.
    • Videos - We went to the Channel 9 studio and recorded a couple episodes of Defrag Tools to help explain some of the basics of WinDbg Preview.

    • Defrag Tools #182 - Tim, Chad, and I go over the basics of WinDbg Preview and some of the features
    • Defrag Tools #183 - Nick, Tim, and Chad use WinDbg Preview and go over a quick demo
    • Coming Soon - Defrag Tools #184 - Bill and Andrew walk through the scripting features in WinDbg Preview

    What's New

    There are a lot of major changes, some of them under the hood and some of them really obvious. Here are my favorites or the things that people have told me they like the best.

    Less intimidating

    One of the words people often use to describe WinDbg is "intimidating". When you first open it, you get a dull gray screen and very little indication of what to do next. Once you're going, outside of the stepping icons, it's difficult to tell what toolbar button or menu is what you want. With WinDbg Preview we've taken a few steps to make it a bit easier for beginners.

    • Ribbon - Ribbons are great when icons don't do a great job of describing an action, and when there are a lot of different contextual actions that are only relevant sometimes. Right now our ribbon is pretty barebones with the basics, but over time we'll be adding more ribbons for specific contexts while you're debugging.
    • Re-worked file menu - The new file menu makes it much more clear which options you have for starting and configuring your debugging session. The attach dialog is much cleaner and more organized now and there's even a new option to launch your Store App or background tasks without needing to set it up with PLMDebug.exe.
    • Familiar source windows - Source windows now are better in pretty much every way and should look more like to the source windows you're used to seeing in every other modern editor.

    Quality of life improvements

    WinDbg has gone a long time without any major quality of life improvements or modernizations. This has led a lot of people to doing registry hacks to get a prettier theme, or having a dozen icons pinned to their taskbar for each thing they debug often. We've taken some of these work-arounds and made them easy to access.

    • Dark theme - This one is pretty self-explanatory, a lot of people use dark themes in their editors, and then flip over to the glaring brightness of WinDbg. Now it can match!
    • Recent targets - Instead of having to have your KDNET key and IP on a sticky-note on your monitor, WinDbg Preview will now remember all your recent sessions and some of the settings that you had during that session. You can quickly access them again from the recent targets list in the file menu.
    • Various window improvements - Many windows have gone a while without updates or just have glaring bugs. Some of the notable things we've done differently are that the disassembly window keeps its highlighting in the right spot when scrolled, and the memory window has better highlighting and scrolling. Many windows are also asynchronous now and loading can be cancelled by running another command.

    Data model front and center

    Hopefully you've heard about the debugger data model by now. If you haven't check out some of my older blog posts at and our MSDN docs linked above. Up until now, the data model was only accessible through JavaScript and the dx command. With WinDbg Preview we're putting the data model under the vast majority of what you see, making it much more extensible.

    • Extensible locals and watch - The data model is now powering the locals and watch windows. NatVis and JavaScript extensions that extend the data model will be reflected in those windows. You can even put LINQ queries into the watch window!
    • Model windows - There's a new type of window called a model window. Model windows will show the results of any model query in a normal hierarchy view or a table. You'll see in the FAQ that WinDbg Preview doesn't have a modules window, you can use a model window to make your own with @$cursession.Modules! This also has the benefit that if you make a JavaScript extension that extends modules, it'll automatically update your window.
    • Built-in scripting environment - One of the biggest complaints with scripting and extending the debugger is having to go into an IDE to write and iterate on it with WinDbg Preview you can write and execute your JavaScript and NatVis directly from the debugger. The script window has error highlighting, IntelliSense, and easier execution of scripts.

    Restrictions and other things worth noting

    While we've got that big list of what's new and awesome, this is still a preview, so there's some things that you should be aware of.

    • At this point in the preview, we're only offering WinDbg Preview through the Windows Store. That means only devices running Windows 10 Anniversary Update can install it.
    • You might hit errors when trying to do something that requires elevation. You'll have to manually launch WinDbg Preview elevated.
    • The concept of a workspace is going to be changing a lot. A workspace in WinDbg Preview is vastly different from one in WinDbg. The MSDN documentation linked above has more information.

    That's where we are today. The core experiences are there and we'll be releasing improvements faster than our normal pace now in that we're shipping from the Windows Store. Please don't hesitate to send us feedback and feature requests in the Feedback Hub or in the comments below, we want your input as we move forward!

    -Andy Luhrs

    Source: New WinDbg available in preview! Debugging Tools for Windows
      My ComputersSystem Spec

  2. Posts : 35,450
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       28 Aug 2017 #1

    Thanks, Shawn! I thought you would grab it and give it a nice home! :)
      My ComputersSystem Spec

  3. Posts : 14,413
    Windows 10 Pro
       28 Aug 2017 #2

    f14tomcat said: View Post
    Not sure what this is, but sounds like Debugger tools that are new for 10.

    New WinDbg available in preview for Windows 10 - Windows 10 Forums
    That's an essential tool to our BSOD squad, helping to analyse system crashes and BSOD / GSOD.
      My ComputerSystem Spec

  4. Posts : 31,394
    64-bit Windows 10 Pro build 18219
    Thread Starter
       28 Aug 2017 #3

    f14tomcat said: View Post
    Thanks, Shawn! I thought you would grab it and give it a nice home! :)
      My ComputersSystem Spec

  5. Posts : 35,450
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       28 Aug 2017 #4

    Kari said: View Post
    That's an essential tool for our BSOD squad, helping to analyse system crashes and BSOD / GSOD.
    I got "Tweetered" by Gabe, and thought I'd take a look. It did sound like a BSOD tool, and other purposes.
      My ComputersSystem Spec

  6. Posts : 38,043
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       28 Aug 2017 #5

    What the hey. I went to get the app and it states it's currently not available? Anyone else get this?

    Click image for larger version. 

Name:	3 WinDbg.png 
Views:	4 
Size:	121.8 KB 
ID:	150826
      My ComputersSystem Spec

  7. Posts : 14,413
    Windows 10 Pro
       28 Aug 2017 #6

    HippsieGypsie said: View Post
    What the hey. I went to get the app and it states it's currently not available? Anyone else get this?
      My ComputerSystem Spec

  8. Posts : 38,043
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       28 Aug 2017 #7

    Thanks, Kari. I should read my Twitter more often, although I have its notifications shut off. It was driving me crazy....Well, crazier.
      My ComputersSystem Spec

  9. Posts : 35,450
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       28 Aug 2017 #8

    Am I reading this wrong?

    Click image for larger version. 

Name:	2017-08-28_16h34_31.png 
Views:	2 
Size:	29.9 KB 
ID:	150828
      My ComputersSystem Spec

  10. Posts : 38,043
    Dual boot Windows 10 FCU Pro x 64 & current Insider 10 Pro
       28 Aug 2017 #9

    f14tomcat said: View Post
    Am I reading this wrong?
    I got that and noticed it too. Does that mean 32 bit systems only? And what's with the keyboard and mouse? I click on "More info" and it opens my "About" page in Settings app.

    Click image for larger version. 

Name:	2 WinDbg.png 
Views:	3 
Size:	159.7 KB 
ID:	150833
      My ComputersSystem Spec

Page 1 of 2 12 LastLast

Related Threads
winDbg report after BSOD in BSOD Crashes and Debugging
REPORT: Probably caused by : ntkrnlmp.exe ( nt!FsRtlNotifyFilterReportChange+122 ) Background: ... ran chkdsk ... verified all drivers up to date ... ran memtest86+-5.01 ... AVG indicates virus free ... reinstalled win 10 ... PC is ancient...
WinDbg error in BSOD Crashes and Debugging
For some reason, I can't debug using WinDbg. This error pops up whenever I debug my minidump files. I can confirm that the files are not corrupted, as I posted them here in this forum and the problem got troubleshooted. I have attached my...
Solved WinDbg error. in Software and Apps
Hi, I'm quite active on the BSOD subforum of Sevenforums and recently I've been having a small issue with WinDbg and I tried to fix it but it didn't work. It has something to do with symbols and its path has somehow gotten a bit messy. 59847 ...
Solved Need Help with setting up Windbg in BSOD Crashes and Debugging
I seem to be suffering from a severe lack of knowledge and experience in this area. I am trying to read dump file created by Windows 10 but keep seeing errors about ntoskrnl.exe and symbol errors. I have gone through the tutorial by Golden. I...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:20.
Find Us