What's the way these days to load my custom extension (.dll) into the new WinDbgX when it starts up? It seems like it's now placed into a folder with the UWP apps where one can't easily write to.
You can set an environment variable to tell WinDBG where to look for extensions.
e.g.:
:: Works for all versions of WinDBG but especially useful for WinDBG preview
setx /M _NT_DEBUGGER_EXTENSION_PATH C:\t2\windbg\thirdparty_extensions\x64;C:\t2\windbg\thirdparty_extensions\x86;
1 Like