[German]Short note for developers who want to use the debugger WinDbg as an app in the current preview under Windows 10. With WinDbg USB debugging is currently not possible, because of a Microsoft fail.
Most blog readers will probably have using Windows debugger WinDbg. But developers are dependent on this tool – and to evaluate a BlueScreen the tool is also indispensable.
Some background
Microsoft started to revise the Windows debugger WinDbg in 2017. On August 28, 2017 Microsoft published the blog article New WinDbg available in preview!, , which deals with the availability of the updated debugger.
The tool supports now a ribbon and has also received a few other optimizations. And the debugger is now available for download as an app in the Microsoft Store for Windows 10. The aim is to deliver the debugger preview in updated form more quickly.
I blogged about tat within my German blog post Bullshit-Bingo: Windows Debugger WinDbg im Windows Store. There blog post contains some critical remarks about the pitfalls of that new debugger app. My conclusion: "So I'm dealing with bugs in the app that I don't have in Win32 WinDbg'.
Microsoft failed again
Users who wanted to use WinDbg for USB debugging runs in serious issue. I stumbled last night upon the following tweet.
Install WinDbg Preview and set up USB debug
>Fail because USB debug driver has a weird signature
Opt for classic WinDbg
>Fail because the SDK installed by Visual Studio interferes with itAt the moment USB debugging under RS4 with VS installed appears to be impossible.
— Lucan (@tfwboredom) 28. Mai 2018
The developer installed WinDbg Preview and wanted to start debugging via USB. But I couldn't get started because it didn't work. In this case, it wasn't even a preview of Windows 10 that should be debugged. Rather, the developer tried to debug in the Redstone 4 branch, i.e. Windows 10 version 1803 (April update). So he wanted to use the fallback solution: grab the classic debugger from the Windows SDK. But the installed SDK interferes with the preview of the WinDbg debugger, which the user explained in another tweet.
Why does WinDbg ship with a driver that doesn't seem to work on retail Windows installs? pic.twitter.com/oM0hFlBMeB
— Lucan (@tfwboredom) 28. Mai 2018
Microsoft has provided a driver for WinDbg whose digital signature is not accepted/recognized. Ergo, USB debugging is not possible – somehow strange and another Microsoft fail.
Similar articles:
Windows Debugger Preview with Time Travel Debug-Feature
Blue screen stop code 0x00000116 (nvlddmkm.sys)
