Author: Noumegnos
Subject: PsKill not killing
Posted: 05 September 2014 at 2:36am
So I've been on a frustrating journey.
I'm trying to use PsKill to shut down processes that have frozen to unresponsiveness, that still take up memory and clog my computer. Lately, this seems to happen more and more often, and today has been hitting me left and right. There seems to be something severely wrong (or just beyond me).
But the reason for this post is not my computer trouble, but the fact that I cannot get PsKill to do anything about these frozen processes. In the command line, I've put windows/system32> pskill -t (process), nothing fancy or complex, I just need it to work. I've re-read the instructions several times, and I get the impression it works since the little message of "Pskill version etc" pops up, but then nothing. Don't even get a line back to type on. I've tried with all conceivable firewalls and auto-sandboxing turned off, with no difference. The only thing that gives me a difference is using PID instead of the application's name, but I only get a message saying it's terminated (it's not).
I searched this forum for similar issues, but I only found people trying more advanced commands and failing to make them work. There was someone who mentioned a service related to pstools, but I can't find such a thing.
Also, I tried pskill on an application that ran normally, and it terminated without issue.
Anyway, I hope this is at least of interest to someone. It's disheartening enough that my efforts to find a solution to the actual issue of programs slowly choking my computer leads me simply to a more powerful tool for shutting them down, but that this, too, failed, is depressing. I hate system restores.
Thanks!
Subject: PsKill not killing
Posted: 05 September 2014 at 2:36am
So I've been on a frustrating journey.
I'm trying to use PsKill to shut down processes that have frozen to unresponsiveness, that still take up memory and clog my computer. Lately, this seems to happen more and more often, and today has been hitting me left and right. There seems to be something severely wrong (or just beyond me).
But the reason for this post is not my computer trouble, but the fact that I cannot get PsKill to do anything about these frozen processes. In the command line, I've put windows/system32> pskill -t (process), nothing fancy or complex, I just need it to work. I've re-read the instructions several times, and I get the impression it works since the little message of "Pskill version etc" pops up, but then nothing. Don't even get a line back to type on. I've tried with all conceivable firewalls and auto-sandboxing turned off, with no difference. The only thing that gives me a difference is using PID instead of the application's name, but I only get a message saying it's terminated (it's not).
I searched this forum for similar issues, but I only found people trying more advanced commands and failing to make them work. There was someone who mentioned a service related to pstools, but I can't find such a thing.
Also, I tried pskill on an application that ran normally, and it terminated without issue.
Anyway, I hope this is at least of interest to someone. It's disheartening enough that my efforts to find a solution to the actual issue of programs slowly choking my computer leads me simply to a more powerful tool for shutting them down, but that this, too, failed, is depressing. I hate system restores.
Thanks!