‚Č° Menu

How to kill process on remote computer?

In Windows, we can kill processes running on a remote computer using the taskkill command. We can specify process id/image file name/user name to identify the processes that need to be killed. Below you can find the syntax for each of the cases with examples.

Kill remote process using process id.

The syntax for this case is as below

Taskkill /S remoteServer /u userName /PID processId


c:\>taskkill /S /u administrator /PID 5088
Type the password for administrator:******

SUCCESS: The process with PID 5088 has been terminated.

We can as well specify FQDN name of the computer for /S option. We can add /P switch to the above command, to specify the password in the command itself. This will allow the command to be executed from a batch file, without any user interaction.

Kill remote process using image name

We can use filter option (/FI) to specify the image name. The syntax is as given below.

taskkill /s remoteServer  /u userName /FI "IMAGENAME eq filename"

For example, if I need to kill all command window processes, I would run the below command.

taskkill /s /u administrator /FI "IMAGENAME eq CMD.EXE"

If you need to kill outlook process, the command would be:

taskkill /s /u administrator /FI "IMAGENAME eq OUTLOOK.EXE"

Kill processes executed by a particular user

The command is similar to the previous case with one change. Instead of ‘imagename‘, now we use ‘username‘ in the filter argument.

taskkill /s remoteServer  /u userName /FI "USERNAME eq userLoginId"

Viewing the list of processes on remote computer

We can get the remote processes list using tasklist command.
To get list of all the processes, the command is :

tasklist /s remoteServer /u userName

To list the processes running a particular image file:

TASKlist /S remoteServer /u userName /FI "IMAGENAME eq filename"

Example: To get the list of processes running cmd.exe on the remote computer, the command is:

c:\>Tasklist /S /u administrator /FI "IMAGENAME eq CMD.EXE"
Type the password for administrator:******

Image Name                     PID Session Name        Session#    Mem Usage
========================= ======== ================ =========== ============
cmd.exe                       4272                            3      2,336 K
cmd.exe                       4448                            3      2,276 K
cmd.exe                       5008                            1      2,392 K
cmd.exe                       4228                            0      2,032 K
cmd.exe                       2344                            0      2,024 K
cmd.exe                       5552                            0      2,028 K
cmd.exe                       2936                            0      2,024 K
cmd.exe                       3776                            1      6,248 K
6 comments… add one
  • Ricardo Calles

    You are the real mvp.

  • Charles

    Everything seems to be working but even when typing the correct password it keeps saying that the username or password is correct.

    C:\>taskkill /s /u Reception /FI "IMAGENAME eq App1.exe"

    the correct name is Reception, ive tried it without the capitol R and ive also tried it the way specified below but i still keep getting the same error.

    C:\>taskkill /s /u\Reception /FI "IMAGENAME eq App1.exe"

    Any guess why its saying the username or password is incorrect?

    • InChargeOfMe

      Charles, have you tried it without the username option?

    • Todd

      I don’t know if this will work but you can try the following:

      /u .\reception

      That should specify the local user on the remote machine. I hope it helps!

  • Fred

    Same issue as Charles for me. When typing the correct password it keeps saying that the username or password is correct.

    tasklist /s SMA-ATTC /u Sylvie

    Without username option the response is “ERROR: The RPC server is unavailable”

    • Gav

      I has the same issue at first until I used the domain admin account, I know you’ve probably checked already but just make sure that account has admin rights. Also try opening cmd as administrator too.

Leave a Comment