Open joridiculous opened 1 year ago
Disclaimer: I'm not on the WinDbg team (or at Microsoft) anymore, but I did make this decision.
The "Debugging Tools for Windows" package that comes as part of the windows SDK includes a large number of build and debugging-related tools. Any of them that are really build tools (like pdbstr) actually belong as part of the SDK, and not as part of an interactive debugger package. Other components in the package are really redistributable components like dbghelp and dbgcore. The important ones have been shifted to NuGet packages. There are some remaining legacy debugging tools, like gflags and plmdebug. The intention was to build that functionality into WinDbg.
As for "why is it installed in a hidden folder with a stupid long name", that's because it's using AppX as an install/update technology.
like Kill, DumpChk (Main reason i downloaded it) Also why is it installed in a hidden folder with a stupid long name and not in "Program Files (x86)\Windows Kits\"