@aallidina: Rename them and then put the symsrv.dll from the debugger folder there. That might make it work. If it doesn't, get a DBGHELP trace and email it to me (defragtools@microsoft,com)
md c:\Mymd c:\My\DbgHelp
setx DBGHELP_DBGOUT 1setx DBGHELP_LOG C:\My\DbgHelp\DbgHelpLog.txt
@aallidina: Well that's annoying. What location is symsrv.dll being loaded from (looking in the Process Monitor log).
The versions in system32 isn't the full version. You need to use the version that comes with the debugger (same story goes for dbghelp.dll).
@voidp: Good idea. Added to the show notes.
OneDrive link for the PDE debugger extension: http://sdrv.ms/11C7S9c
@BrianCatlin: I was going to mention it but decided not to. You need to know what the schema is to use the tool effectively. Personally, I think writing the XML directly is as easy as using the tools.
@S3curityPlu5: Is your Developer License up-to-date?
@Kenan: We both have the Lenovo X1 Carbon Touch i5/4Gb RAM (a business model). You can also get an i7/8Gb model.
For consumers, the Lenovo Yoga is the equivalent model.
@s3curityConsult: Weird, if you run procdump -ma -i c:\dumps after the VS install, it should be set as the AeDebug Debugger. (Equally, if you run WinDbg -I it should be the debugger).
What values do you have in these locations?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebugHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug
@Peter: I think the only place they are sold is the MS Company store on the Redmond campus. I don't think they are at the Retail Stores or Online...
@loverboy: No idea - they might have deleted it themselves. We wouldn't have culled that.
@loverboy: What do you mean? Did they get stripped in a post?
(Yes, codemachine has a great debugger extension)