4 ms·
Ah, good old days of using these to disable auto-run programs (with some of them viruses) on Windows XP and 7. And procexp! It's just the better task manager.
by joshxyz 5y ago
Ah, good old days of using these to disable auto-run programs (with some of them viruses) on Windows XP and 7.
And procexp! It's just the better task manager.
- T3OU-736 5y agoProcessHacker (https://processhacker.sourceforge.io/ https://processhacker.sourceforge.io/) is also a worthy competitor to the Process Explorer.
- krylon 5y agoI second that, because ProcessHacker was the only tool I found to let me set the I/O priority of a process.
- iggldiggl 5y agoThirded, because at some point, ProcessExplorer started recording the resource usage history of a process (CPU usage, memory, I/O) only the moment you explicitly opened that particular process's properties window for the first time. Because the last version of ProcessExplorer that didn't exhibit that behaviour no longer works on current Windows versions (certainly not 10, and I'm no longer sure whether 7 wasn't already problematic, too), ProcessHacker instead it is then.