2 ms·

One of the most horrendous UX design picks in Windows 10, I immediately switched to ProcessHacker the moment I saw it.

• sitzkrieg 6y ago
  could have just double clicked it
• mycall 6y ago
  How does ProcessHacker compare to Process Explorer? From my quick look, they appear to have mostly the same features.
  • iggldiggl 6y ago
    At some point Process Explorer started recording the CPU/memory usage graphs for a process only the moment you opened the details window for that particular process for the first time. So even if Process Explorer had been running in background all the time, you could no longer inspect a process's CPU/memory usage history after the fact if you hadn't by chance already opened its details window before. As the last version (I might have even asked on the forum about it, but never got a definitive response whether this was intentional or a bug) of Process Explorer that didn't exhibit this annoying new behaviour stopped working after switching to Windows 10, I switched to ProcessHacker at that point. I've initially missed Process Explorer's miniature system information diagrams in the toolbar a little, but otherwise I've been happy with ProcessHacker.
• davepl 6y ago
  Oh yeah, that's a tour de force of UI design! Geebuk.