Products · Product
WinDbg
Raised as a usability problem by 10 people on Hacker News over 14 years (2013–2026), in 11 threads.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
Every issue, all time, most people first
Features are hard to find due to poor discoverabilityUnreviewed
20132026- Awful GUI with no discoverability, so features are hard to find2026-05-03
- Poor UI/UX and weak discoverability make features hard to find2020-12-03
- Modern interface is cluttered and hard to find things in, unlike old WinDbg2020-06-20
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 12 complaints
- Awful GUI with no discoverability, so features are hard to find2026-05-03
- Debugger has an unintuitive command syntax that is hard to learn2025-05-05
- Freezes every other command and reconnecting to kd after a freeze is frustrating2022-07-13
- Huge learning and usability cliff; needs a cheat sheet even after a decade2022-06-04
- Has to repeatedly type long commands and finds them tedious2021-09-25
- Commenter found the debugger hard to use and never groked it2021-05-20
- The Store version's UI was unusable on a large project2020-12-13
- Poor UI/UX and weak discoverability make features hard to find2020-12-03
- Modern interface is cluttered and hard to find things in, unlike old WinDbg2020-06-20
- Ribbon interface and full-screen File menu feel like Office and are disliked by developers2020-06-20
- Steep learning curve makes the debugger hard to get into2014-07-27
- Steep learning curve and a primitive, hard-to-use interface2013-09-18