Questions[kill-process](server)

I have a server with Windows Server 2008 R2 and a service process (our custom service) running on it under SYSTEM account. A service has presumably hanged and I wanted to stop it. I tried stopping via Management Console "Services" snap-in, but it didn't help, service process still running, despite in the Management Console it is already marked as not running. Is there a way to kill it from the command line? Note that service runs under the SYSTEM account. I have full administrative privileges on the server.

I have tried pskill from console with elevated privileges (just as pskill PID), but it didn't do the job: it has reported that process killed, but I still see it in the Task Manager.

Taskkill also doesn't help:

C:\>taskkill /f /im myservice.exe
ERROR: The process "myservice.exe" with PID 1268 could not be terminated.
Reason: There is no running instance of the task.

But the process still visible in the Task Manager.

Update: Powerhell Stop-Process -Name myservice -Force also didn't work.

Any ideas how to really kill the process (except rebooting the server)?

I wrote a powershell script to start my flask server, run my tests then stop my server. It starts the server and runs my tests. However, when it kills the $server process, it leaves the actual server process running and I can see the window for this process still open. How can I kill the server after the tests finish running?

$db_id = [guid]::NewGuid().ToString()
$env:AUTHZ_DB_FILE = 'Authorization ' + $db_id
$server = Start-Process py -ArgumentList '-m', 'authz.test.server' -PassThru 

Write-Output $server.Id

py -m authz.test.tests $args

Stop-Process -Id $server.Id

I have a PHP script I wrote that I am running, and it has ran all the way through before, but for some reason, it keeps stopping with a message of 'Killed' ...

It is my box, no one else is logged in

The script does not have the word 'Killed' in it anywhere

What is killing my script and why?

I am looking for a well tested bash script (or alternative solution) to do so, in order to avoid max_connection to be exhausted. I know that it is fighting the symptoms, but really need such script as a short term solution.

I have a script running python script.py in a new screen but sometimes the script gets killed:

18
21
Restarting processes... done
2
Killed

How can I protect the script from being killed even when I close the console? Shall I use & or nohup?