Before worrying about setting your environment variables, e.g.
, get the Windbg session working.
This will set your symbol search path to the Microsoft msdl symbol server. Next, reload your symbols:
lkd> .reload /f
This will force the debugger to immediately reload all symbols. This should fix the issue. If it does not, try
lkd> !sym noisy
This will turn on your symbol prompts. Try again running
, looking for clues in the output.
Once your symbols are fixed, you can fix your environment variables. First, ensure that you have created a symbols cache, e.g.
. Add it to
via the command:
lkd> .symfix +C:Symbols
Ensure that symbols still work (do a
), then have a look at your
lkd> .sympath Symbol search path is: symsrv*symsrv.dll*C:Symbols*http://msdl.microsoft.com/download/symbols Expanded Symbol search path is: symsrv*symsrv.dll*c:windowssymbols*http://msdl.microsoft.com/download/symbols ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred symsrv*symsrv.dll*C:WindowsSymbols*http://msdl.microsoft.com/download/symbols
Now set your
using the output above.
- Right click on My Computer
- Environment Variables
- New (User variables)
- Variable name =
Close Windbg and open a new session. Ensure that symbols are fixed. If not, examine your
and ensure it does not differ from the settings that worked in your previous session.