4 ms·

Or at least in my experience using pskill from the Sysinternals Suite, even if you kill a process (at least on earlier versions of Windows), it would not do the

Or at least in my experience using pskill from the Sysinternals Suite, even if you kill a process (at least on earlier versions of Windows), it would not do the same as a SIGKILL (as in "tear down the process, don't wait for it whatsoever"), and would otherwise hang or be waiting for something else.

unnouinceput 4y ago
The trick is to run "taskkill" as user SYSTEM, using "run as". It will kill anything and everything, including generating a nice BSOD if you feel like (kill System process). Or if you're a GUI kind of guy and want a nice interface with plenty of options I recommend "Process Hacker" (https://processhacker.sourceforge.io/ https://processhacker.sourceforge.io/).
- piaste 4y ago
  I've used SuperF4 in the past for this: https://stefansundin.github.io/superf4/ https://stefansundin.github.io/superf4/ It seems to use the win32 TerminateProcess() function, I've never seen it fail although apparently according to the doc it does need to wait for pending I/O. ProcessHacker looks interesting, I used Sysinternals' Process Explorer for the longest time and this appears to be a fork of it?