This is what the dialog box looks like the first time you use it: Detailed Instructions and Tipsįirst, open up the Options | Configure Symbols. It here for the benefit of others and give some detailed insights into how to know whether it is truly working or not. I finally made it work, and came to understand why it was not working, so I thought I would explain I did not see the screenshot, just the link. Path, and other articles on the web were also outdated or did not give the windbg.dll path at all. His screenshot was correct, but the link he gave for information had an old windbg.dll However, I was not having much success getting it to work. The book uses Sysinternals Process Explorer application heavily and discusses how to enable debugging symbols downloads via the Microsoft symbol server to enable resolution of raw address offsets in executables to symbolic names, for instance, in the Threads tab of a process’s Properties dialogue box or in stack traces. I am following along in Windows Internals, Part 1, Edition 7 by Mark Russinovich, et. NOTE: The Dbghelp.dll path is different from the paths I have seen in older articles, The Debugging Tools for Windows installed after the WDK too. This is my setup, and works for me, with the Windows Driver Kit (WDK) installed as well as the Software Development Kit (SDK) with You can call it whatever you want, and put it My C: drive is short on space, and the the local symbols cache can get very big, many gigabytes.

In the picture above, I show the path to the local symbols cache (between the asterisks in the Symbols path) on the D: drive.

Windows process monitor windows 10