Remote process killer

Remote process killer DEFAULT

5 Ways to Kill and View Processes on a Remote Computer

One of the first things any knowledgeable user would do if they suspect there is something slowing their computer down or a suspected malicious program might be running in the background, is press Ctrl+Shift+Escape to open the Windows Task Manager. From there you can view what’s running and detect if any programs are using too much CPU time or memory, or look suspect and shouldn’t be there. Although the Windows Task Manager is a valuable tool, there are better alternative Task management tools out there that you can use to replace it with.

Using the built in tool to manage tasks or a third party task manager on your local computer is great, but what about if you have more than one computer in your network to keep an eye on? Process Explorer, Process Hacker or System Explorer etc cannot show you what’s running on another computer so ordinarily if there is something that needs checking, you would have to go to that computer physically and view or kill any processes.

Thankfully there are ways to access other computers in your local network remotely, and you can also view and manipulate processes on another computer without leaving your own. Here we show you 5 ways to view and manage another computer’s tasks remotely.

1. Remote Process Explorer

Remote Process Explorer by Lizardsystems is a well known free application to view and manipulate the running processes on a remote computer. It is completely free for home and non commercial use. You do need a free registration code to use the free version though, visit the Registration page and enter your name, e-mail, city and country. Once you get the code in your inbox, enter it via Help > Enter Registration Code.

remote process explorer

Although it runs through Windows Management Instrumentation (WMI), Remote Process Explorer is quite comprehensive in what it displays and what you can do. Apart from viewing very detailed information of each remote process, you can kill, run and also change the priority of a remote process. You can even tick a box and have the related process log its memory and CPU usage via a graph in the main window

On first launch the program will ask to run the Wizard which will detect what computers are on the network, or you can go straight to the main interface and configure things yourself. Assuming you have run the Wizard and it’s detected the target computer, right click on it in the computers list to the left > Connect as > The following user, then enter the remote username and password and click OK.

remote process explorer connect as

The Processes and OSInfo tabs should now be populated with the information from the remote computer. Remote Process Explorer also has some administrative tools for remote management. You can shutdown, explore, open the Computer or Services Management consoles, open Event Viewer, open a Remote Desktop session or send a message etc.

Although Remote Process Explorer isn’t portable you can extract the setup installer with Universal Extractor and save the contents of the {app} folder to turn it into a portable version.

Download Remote Process Explorer

2. Desktop Central Free Windows Tools

ManageEngine make a number of commercial software applications for remote operations, corporate networking and enterprise solutions. They also have an application suite called Desktop Central which is designed for large networks but a free version has been made available that contains a number of individual components from the main suite.

desktop central free windows tools

There is a total of 12 tools in the Free suite, including Software Inventory to get a remote list of installed software, Wake on LAN, Remote Command Prompt, Remote Shutdown and Restart tool, Hard Disk Space detector, Laptop Battery Power Monitor and what we’re looking for here, Remote Task Manager.

Although basic, the Remote Task Manager is able to show you a list of processes running on the remote machine and allows you to kill a process in the list. Simply enter your remote user’s name and password into the boxes, then add the remote computer name or IP into both the Domain Name and Computer Name boxes, finally click the Get Process button.

desktop central remote task manager

The window will then populate itself with the list of processes on the remote machine, hovering over a process will select it, clicking “End Process” will allow you to terminate whatever process is highlighted. The icons above are to refresh the list and choose extra columns of information. Although you need to initially install Free Windows Tools to run the Remote Task manager, you can copy RemoteTaskManager.exe from the Program files folder and use it as a portable tool, then uninstall the suite again.

Download Desktop Central Free Windows Tools

3. Remote Process Viewer

Remote Process Viewer is a very simple program that gives you a list of all the processes currently running on a remote computer. A useful bonus is it’s also a standalone portable executable of around 600KB that doesn’t need installation although if you want to do more than just view what’s running on the target computer you will need to use something else a bit more powerful.

remote process viewer

Because it uses WMI to gather it’s information, you will need to make sure WMI is allowed through your firewall (see below). Then all you have to do is supply the name or IP address of the remote computer, or use the Browse button to find the computer on the network, than supply the username and password of the logged on remote user, finally click “Scan Now”.

After a few seconds the main window should be populated with Process name, it’s folder, ID, used memory, CPU time, priority and a few other related pieces of information. Clicking on a process will allow you to search for that particular process name via and the Google button. The popup isn’t useful and only points to a shareware network task manager trial.

Download Remote Process Viewer

4. Yet Another (Remote) Process Monitor

Also known as YAPM, this is quite a feature rich program and in addition to being able to view processes on the local or remote computer, it can also perform a number of other remote functions. These include killing existing or opening new processes, starting, stopping, creating or disabling services, viewing and closing remote network connections, and the ability to show, maximize/minimize or end currently opened tasks.

yet another remote process monitor

YAPM has two main modes of remote operation; Connecting via Windows Management Instrumentation (WMI) or using the YAPM server. Using WMI is a lot easier and requires nothing extra apart from making sure the connection to the remote machine works. It does have a drawback though of not allowing as many functions like tasks management, monitoring and network management.

The YAPM server allows for all the remote functions available in the program but YAPM itself needs to be run on the remote machine in server mode for it to work, something which you may not be able to do. Unless you need the extra functions of the YAPM server it’s recommended to start with WMI mode.

connect YAPM using WMI

To set up for WMI, launch the program and click the round Settings button > Change Connection type. Click “Remote via WMI”, enter the remote computer name or IP address, the username and the password, then click Disconnect and the same button again to connect to the remote machine. This will populate the relevant YAPM windows with processes and services where you can view, start, stop and gather information about each item. It also has a portable version.

Download Yet Another (Remote) Process Monitor

5. Remotely Viewing and Killing Tasks From Command Prompt

Windows has several built in command line utilities for performing various tasks, and two tools which are useful for this job are “Tasklist” and “Taskkill”. If you open an admin command prompt (Press Start, type cmd, press Ctrl+Shift+Enter) and type tasklist, it will give you a list of running processes on your computer. It can however, be used to get the task list from a remote computer with a few extra arguments, they are:

Tasklist /S remote system (name or IP address) /U username /P password

Remote tasklist in command prompt

Make sure to put anything in quotes that has a space in the name. This will give you a list of remote process names running on the target computer along with their Process IDentifier (PID) and memory usage. Killing a process in the list is achieved with the taskkill command that has a similar syntax to tasklist:

Taskkill /S remote system /U username /P password /IM Process

taskkill remote process

Simply add the process name (including .exe) or the PID number you wish to kill along with the “/IM” argument after the computer name, username and password. If it works a SUCCESS message will show. If the process doesn’t get killed, try and add /F to the end of the line to force the process to be terminated. Obviously some processes cannot be terminated such as those which are system critical or security software etc.

Requirements to Enable Remote Process Viewing and Control

Unless you have enabled your system to view processes remotely before, there are some requirements that must be met in order for tools like these to work in a local area network .

Note: If you have a Windows Home or Basic edition such as XP Home, Vista / 7 Basic or Home Premium, remote administration is disabled on those versions so it’s not possible to view or control processes on another computer. You can however, connect to those versions from a Professional, Enterprise or Ultimate version of Windows.

– You must be an Administrator or have Admin privileges to connect to the remote machine.

– Make sure the computer you are connecting to has a password on its user account, blank passwords will NOT work. Go to Control Panel > User Accounts > Create a password for the user if necessary.

– Make sure simple file sharing is disabled in Windows XP. Go to Control Panel > Folder Options > View tab > Scroll right to the bottom at Advanced Settings > Uncheck “Use simple file sharing”.

– Make sure a file and printer sharing exception is allowed in the firewall, go to Start > Run > and type:

netsh firewall set service type = FILEANDPRINT mode = enable

– With programs that use Windows Management Instrumentation (WMI) to gather the remote computer’s data, you need to make sure WMI is allowed through any active firewall. An RPC server error is common if WMI is being blocked by a firewall. For third party firewalls, TCP port 135 needs allowing. For Windows Firewall, type the following command into an admin Command Prompt for Vista, 7 and 8:

netsh advfirewall firewall set rule group=&quote;windows management instrumentation (wmi)&quote; new enable=yes

Or alternatively go to Windows Firewall in Control Panel, click “Allow a program or feature through Windows Firewall” and tick “Windows Management Instrumentation (WMI)”. Click OK.

enable wmi in windows firewall

For Windows XP Firewall use:

netsh firewall set service RemoteAdmin enable

If you still have issues of not being able to connect to the remote computer, you may need to temporarily disable any firewall or other security software and then try to connect.



Remote Process Explorer - short RPE - is a small tool for all the admins outside with the need to manage clients immediately within one or more domains. With RPE the admin is able to view all the running processes on a client and of course kill them. RPE shows also the services and their state and start type, you are able to directly get to the c$ share or open a remote commandshell (winrs) and connect to the client via RDP. But that's not all, RPE will show errors and warnings of the past 30 days out of the application eventlog and the system eventlog.
You need to know to which groups the actual logged on user on the remote client belongs to? No problem RPE will determine them for you!
And the best: It's free and open source!

Please be so kind to leave a review about RPE after downloading, this is my only source to improve RPE and to implement your requirements to it!


  • Shows all running processes on remote client
  • Kill process on remote client
  • Shows services, service status, service start type on remote client
  • Start and stop services on remote client
  • View, Copy-Paste System and Application Event Log entries (past 30 days)
  • Directly open connection to client via RDP
  • Open a remote command shell to remote client
  • Show C$ of remote client within your explorer
  • Shows some extra info like free space on c, uptime, os version and so on
  • Get groups currently logged on user on remote client belongs to (AD)
  • Able to use with parameters for automation within scripts
  • Shows (regular) installed software on the remote host
  • Acts now faster with background jobs
  • Shows the windows native Services.msc and Eventviewer Consoles using the menu

Project Samples

Main WindowNew Features


System, Systems Administration


Creative Commons Attribution ShareAlike License V3.0

Other Useful Business Software

Get secure and private access to the internet Icon

We help companies keep their networks and Internet connections secure. Our VPN service adds an extra layer of protection to secure your communications. We do this by applying strong encryption to all incoming and outgoing traffic so that no third parties can access your confidential information. Protect your organization against security breaches. Secure remote team access. Simplify business network security. Access region-specific online content from anywhere in the world

Learn More

Rate This Project

Login To Rate This Project

User Ratings

5.0out of 5 stars





ease1 of 52 of 53 of 54 of 55 of 55 / 5

features1 of 52 of 53 of 54 of 55 of 55 / 5

design1 of 52 of 53 of 54 of 55 of 50 / 5

support1 of 52 of 53 of 54 of 55 of 50 / 5

User Reviews

  • Excellent and useful too. Developers - could you please make the Domain field changeable? It's currently greyed out for some reasons.

  • RPE / ReProEx works perfectly! a Must Have!

    1user found this review helpful.

Read more reviews >

Additional Project Details



Intended Audience

System Administrators

User Interface

Win32 (MS Windows)

Programming Language




Similar Business Software
  • Atera


    Atera is a cloud based all-in-one remote monitoring & management (RMM) platform for MSPs & IT pros. Atera includes everything you need to solve your clients toughest IT problems in one, centralized location. Atera's fixed cost pricing model helps IT businesses of all sizes grow with no extra...

    See Software

  • N‑able RMM

    N‑able RMM

    N‑able RMM® is a cloud-based IT solution that makes it easy for MSPs to deliver valuable technology services within hours, not weeks or months. Clear graphical dashboards place alerts front and center so you can focus on what needs you most. Built-in remote access and security features help you...

    See Software

  • NinjaRMM


    If you're looking to support your clients and manage IT more efficiently, turn to NinjaRMM. The world's first security centric remote monitoring and management (RMM) platform, NinjaRMM enables IT professionals to monitor and manage the entire IT stack with full automation all within a single...

    See Software

Report inappropriate content

  1. Rampart trail
  2. Margot shoulder bag
  3. Buzzfeed clothing style
  4. 600rpm motor

7 Ways to Manage Windows Processes Remotely

Manage Windows Processes RemotelyA while back we talked about ways you can manage Windows services remotely. Today, we’ll show you seven ways you can “manage” Windows processes remotely in general. By manage we mean start, query, and kill a remote Windows process. Keep in mind pretty much all of these tools and techniques here assume you have appropriate permissions on the remote computer.

Starting processes remotely

1. PsExec, PowerShell, and WMI

We’ve alreadytouched on ways you can start processes remotely using tools like PsExec, but with a little bit of scripting effort, you can also use tools like PowerShell’s Invoke-Command cmdlet or even a WMI query.

Query processes remotely

Without interactively connecting to a remote Windows computer you can easily query its current list of processes with a variety of tools.

2. tasklist

Since Windows XP there is a built-in command line utility named “tasklist“. By running the command “tasklist /s hostname” where “hostname” is the remote computer you want to query, it will return a list of processes on the remote machine and some basic details about each process (PID, session number, memory usage, etc.).

The tasklist command also allows you to specify different credentials on the command line if you need to authenticate to the remote computer with a different username and password. Just remember if you specify the password on the command line it will be visible to other administrators on the local computer who look at the local computer’s process list details.


In a command prompt run “tasklist /?” for more information about its usage.

3. PsList

Once again, if you’ve followed our articles for awhile, you know we’re big fans of the SysInternals PsTools suite. The PsList utility is another part of the PsTools suite. PsList is very similar to tasklist, but it gives you much more detailed information on threads (counts, states, context switches, etc.), CPU usage (user time, kernel time, etc.), and memory usage (private byes, working set, virtual memory, page faults, etc.).

PsList can also target a specific PID or process name (or name pattern). And one of my favorite features of PsList is the -t option to show you the process tree structure.

Much like the tasklist command, PsList also allows you to specify different credentials on the command line if you need to authenticate to the remote computer with a different username and password. Again, remember if you specify the password on the command line it will be visible to other administrators on the local computer who look at the local computer’s process list details.


After downloading PsList, in a command prompt run “pslist -?” for more information about its usage.

4. Scripting

And of course, if you want to go the scripting route, you can use things like PowerShell’s Get-Process cmdlet or again, even WMIqueries to get details about remote Windows processes.

Killing processes remotely

Just like how you don’t need an interactive login to a remote Windows computer to get running process details, you don’t need an interactive login to terminate Windows processes on a remote computer either.

You obviously want to be very careful with these remote kill commands as you can pretty easily knock out an important service or process on the remote machine. Proceed with caution.

5. taskkill

The taskkill command is very similar to the tasklist command. You can specify a process name to kill by running a command like “taskkill /s hostname /IM notepad.exe” or one ore more PIDs with “taskkill /s hostname /PID 1234 /PID 5678”, where hostname is the name of the remote computer. The taskkill command also has a /t option to terminate an entire process tree (i.e. kill the process and any child processes it spawned).

Just like the tasklist command, taskkill also allows you to specify different credentials on the command line if you need to authenticate to the remote computer with a different username and password. Again, remember if you specify the password on the command line it will be visible to other administrators on the local computer who look at the local computer’s process list details.

In a command prompt run “taskkill /?” for more information about its usage.

6. PsKill

Just like how tasklist has the sister command taskkill, PsList has a sister command in PsKill. PsKill is also part of the SysInternals PsTools suite. PsKill is nearly identical to taskkill in that it will let you specify a process name or PID to kill, it has a -t option to terminate an entire process tree, and it allows you to specify different credentials on the command line. And just to drive it home… once again, remember if you specify the password on the command line it will be visible to other administrators on the local computer who look at the local computer’s process list details.

After downloading PsKill, in a command prompt run “pskill -?” for more information about its usage.

7. Scripting

Unfortunately PowerShell’s Stop-Process cmdlet doesn’t take a “-ComputerName” argument for remote execution, however you can workaround this by combining Stop-Process with Invoke-Command to remotely execute the cmdlet like:

Invoke-Command -ComputerName hostname {Stop-Process -name "notepad"}

And of course, good ol’ WMI provides a way for you to terminate a remote Windows process as well.

So as you can see, there are many tools and techniques – most built-in to Windows – that allow you to manage Windows processes remotely. Have fun with your processes!

How To Kill A Tree Without Anyone Knowing - How To Kill A Tree - Journey To Sustainability

vista.jpgWindows provides several methods to view processes remotely on another computer. Terminal Server is one way or you can use the command line utility pslist from Microsoft Sysinternals site. While both options are good alternatives, Windows XP and Vista provides a built in utility for viewing and killing process on remote Computers using Tasklist and Taskkill commands.

Both tasklist.exe and taskkill,exe can be found in %SYSTEMROOT%\System32 (typically C:\Windows\System32) directory.

To view processes on a remote Computer in your home, you will need to know the username and password on the Computer you want to view the processes. Once you have the user account information, the syntax for using tasklist follows:


(To view all tasklist options, type tasklist /? at the command prompt)

To execute, click on Start \ Run… and in the run window type cmd to open a command prompt. Then type the tasklist command, substituting SYSTEM for the remote computer you want to view processes, USERNAME and PASSWORD with an account/password on the remote Computer.

(NOTE:if you are in a Domain environment and have Administrator rights to the remote Computer, you will may not need to specify a Username and Password)


Now if there was a process that needed to be killed, you can use the taskill command. As with tasklist, you will also need the Username and Passoword on the remote Computer. The syntax for using taskkill is


(To view all taskkill options, type tasklll /? at the command prompt)

Where SYSTEM, USERNAME, PASSWORD is the same as above for the tasklist command, and IM is the process image name you want to kill. In the above screen shot we will kill firefox.exe by typing the following at the command prompt:

taskkill.exe /S wtn1 /U joe /P ddd1234 /IM firefox.exe
SUCCESS: The process "firefox.exe" with PID 196 has been terminated

You can also kill a process using the PID (Process ID) of the process. In the above example the PID for firefox.exe is 196:

taskkill.exe /S wtn1 /U joe /P ddd1234 /PID 196

If the process does not terminate, you can use /F to forcefully terminate the process.

taskkill.exe /S wtn1 /U joe /P ddd1234 /PID 196 /F


Process killer remote

PsKill v1.16

  • 2 minutes to read

By Mark Russinovich

Published: June 29, 2016

DownloadDownload PsTools(2.7 MB)


Windows NT/2000 does not come with a command-line 'kill' utility. You can get one in the Windows NT or Win2K Resource Kit, but the kit's utility can only terminate processes on the local computer. PsKill is a kill utility that not only does what the Resource Kit's version does, but can also kill processes on remote systems. You don't even have to install a client on the target computer to use PsKill to terminate a remote process.


Just copy PsKill onto your executable path, and type pskill with command-line options defined below.

Using PsKill

See the September 2004 issue of Windows IT Pro Magazine for Mark's article that covers advanced usage of PsKill.

Running PsKill with a process ID directs it to kill the process of that ID on the local computer. If you specify a process name PsKill will kill all processes that have that name.

Usage: pskill [- ] [-t] [\\computer [-u username] [-p password]] <process name | process id>

-Displays the supported options.
-tKill the process and its descendants.
\\computerSpecifies the computer on which the process you want to terminate is executing. The remote computer must be accessible via the NT network neighborhood.
-u usernameIf you want to kill a process on a remote system and the account you are executing in does not have administrative privileges on the remote system then you must login as an administrator using this command-line option. If you do not include the password with the -p option then PsKill will prompt you for the password without echoing your input to the display.
-p passwordThis option lets you specify the login password on the command line so that you can use PsList from batch files. If you specify an account name and omit the -p option PsList prompts you interactively for a password.
process idSpecifies the process ID of the process you want to kill.
process nameSpecifies the process name of the process or processes you want to kill.

PsKill Microsoft KB Article

This Microsoft KB article references PsKill:

810596: PSVR2002: "There Is No Information to Display in This View" Error Message When You Try to Access a Project View

DownloadDownload PsTools(2.7 MB)


PsKill is part of a growing kit of Sysinternals command-line tools that aid in the administration of local and remote systems named PsTools.

Runs on:

  • Client: Windows Vista and higher.
  • Server: Windows Server 2008 and higher.
Interrogation/confession of a Monster Child Killer named Brittany Gosney Part 1

"Complete remote management solution for your network in a single easy to use tool..."

Remote Task Manager® (RTM) is a systems control interface that can be run from any remote Windows NT/2000/XP and Windows Server 2003 computer. This enables a Systems Administrator to control most aspects of a remote environment. The simple-to-use, tabbed interface separates applications, services, devices, processes, events, shared resources and performance monitor, making each of these very easy to control. A Systems Administrator can start or stop services or devices, add new services or devices, manage the run level and adjust the security (permissions, auditing and owner). The Process Function and the Task Manager allows remote termination and adjusting of priority. An Event Viewer lets the Administrator view all events as though they were being run on the host computer. The Performance Monitor displays a dynamic overview of the computer's performance (CPU and memory usage). RTM even supports remote installs, enabling a Systems Administrator to set up a service on remote machines without ever having to physically go to them. RTM adds the ability to lock/shutdown/reboot and to create processes on remote computers.

  • Monitor all running tasks, processes, services and events on remote computers.

  • Watch features of running tasks (the handle of the main window, process ID, etc.).

  • Watch features of running processes (process ID, CPU time, privileges used, memory, priority).

  • See which process is associated with a selected task.

  • See which process is associated with a selected service.

  • End a selected task correctly.

  • Terminate a selected process at any time.

  • Change priority of a selected process.

  • Control which CPUs the process will be allowed to execute on.

  • Stop, start, restart, pause and continue any selected service or device.

  • Change startup parameters of a service or a device (name, account, startup type, dependencies, etc.).

  • Change service's repair parameters on Windows 2000/XP.

  • Watch dependent services.

  • Adjust service's and device's security (permissions, auditing and owner).

  • Manage shared resources on remote computers.

  • Clear event logs.

  • Archive event logs.

  • Monitor a dynamic overview of the computer's performance (CPU and memory usage).

  • Shut down and reboot remote computers.

  • Create processes on remote computers.

  • Lock computers remotely.

  • And much more...

  • Sours:

    You will also be interested:

    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

    793 794 795 796 797