How to kill a process in Windows

So your computer’s acting extra slow today, with too many processes running and overloading the system. Now Chrome is using too much RAM and tabs are freezing. It’s probably best to just kill the processes and start fresh, but how do you actually do that? And what happens if you call up Task Manager and that freezes too?

There’s always a fix and a quick way to kill processes in Windows. This guide covers the easiest methods for killing Windows Processes, from simple Task Manager methods to enterprise-scale automation across multiple endpoints.

What you should know before killing a process in Windows

When a process is terminated in Windows, the operating system immediately halts its execution, releases all allocated memory, and closes associated handles (like files or network connections). Unlike pausing or suspending, which simply freeze the process in memory, termination removes it entirely from the system’s active process list.

A normal process termination occurs when you close an application gracefully. Its code executes cleanup routines, saves user data, and releases system resources. In contrast, a forced termination bypasses these steps and immediately halts the process without allowing internal cleanup, which can cause IT issues.

Windows documentation and Windows Internals describe that abruptly terminating a process may leave dependent threads or resources in an inconsistent state, especially in complex, multi‑threaded applications. That could lead to data loss or corrupted files, weird glitches after restarts, and other dependent programs freezing.

The processes you can’t kill

Certain Windows processes can’t be terminated easily due to security permissions, system protection, or dependency chains. For example, critical system processes like wininit.exe or csrss.exe are safeguarded by the OS because terminating them would cause a system crash (Blue Screen of Death).

Similarly, services tied to dependencies (like Windows Update or Print Spooler) can’t be ended unless their dependent processes are stopped first.

This also varies on different Windows versions:

• Windows 10 vs. 11: Both support Task Manager, taskkill, and PowerShell (Stop-Process). Windows 11 adds UI refinements and better integration with security tools.
  
• Pro Edition: Manual control via GUI and CLI; limited remote or policy-based termination.
  
• Enterprise Edition: Supports remote termination via Intune, Group Policy, and Windows Admin Center; ideal for automation and compliance.
  
• Server Edition: Focuses on headless management; uses PowerShell, WMI, or PsExec; GUI tools may be absent.

Easiest methods to kill a process in Windows

The three main types of process killing methods on Windows are great for different situations. If it’s just you on a single device, the easiest Task Manager method will probably be your go to, but other methods allow you more control or to automate the process across endpoints.

Task Manager: the easiest method

The key advantage of using Task Manager is speed and simplicity, ideal for diagnosing a frozen app or high CPU usage. However, Task Manager lacks batch control, remote capability, and granular scripting, which are vital in enterprise IT or automated environments.

Follow these steps:

1. Open Task Manager by pressing Ctrl + Shift + Esc

2. Navigate to the “Processes” tab

3. Find the target process you want to end > Right click > End task

This immediately signals Windows to terminate the process and free related memory. If termination fails, Windows might display one of these error messages:

• “Access is denied”: You lack administrator privileges.
• “The operation could not be completed”: Process is protected or locked by the system.
• “Unable to terminate process”: Dependency or service conflict.

Additionally, you can view process identifiers (PIDs) in Task Manager if you go to the “Details” tab, which can help you verify that the process was terminated.

In Windows, every running process is assigned a unique PID, which is a numeric tag that helps the system and administrators track and manage active processes. The PID changes every time a program restarts.

Pro tip if Task Manager gets stuck: Sometimes the frozen process can visually lock your screen and hide Task Manager. But there’s a quick fix if you have multiple monitors. Just press Alt + Tab until you highlight the Task Manager window, then press and hold the Windows key, then use your arrow keys to move the Window through different orientations until it moves to a new screen. And if that doesn’t work, check out our other methods for moving a Window that’s off screen.

Command Prompt: when Task Manager freezes

Command Prompt offers scriptable, automatable process termination that works even when Task Manager freezes or becomes unresponsive. Unlike Task Manager’s point-and-click interface, taskkill commands can be integrated into batch files, scheduled tasks, or remote administration scripts, making it invaluable for IT professionals managing multiple endpoints.

The trade-off is less visual feedback and the fact that you need administrator privileges when dealing with system processes. You’ll also need to know either the process name or PID beforehand, whereas Task Manager shows you everything at a glance.

Follow these steps:

1. Open Command Prompt as Administrator

2. Run this command to display all active processes and their PIDs: tasklist

3. Alternatively, you can also search for a specific process with: tasklist | findstr “processname”

For example, <tasklist | findstr “notepad”> will find all instances of Notepad

4. Terminate the process either by task name with <taskkill /IM processname.exe /F> or by PID with <taskkill /PID {number} /F>

Look for the message, “SUCCESS: The process … has been terminated” to know that it worked. If you see “ERROR: Access is denied”, you need administrator privileges, while if you see “ERROR: The process … not found”, check the process name or PID again.

PowerShell: for enterprise-scale scripting and automation

PowerShell elevates process termination beyond simple commands into a full automation and scripting powerhouse. Unlike Command Prompt’s taskkill, which operates on basic text-based inputs, PowerShell works with objects, meaning you can filter processes by CPU usage, memory consumption, or runtime, then terminate them programmatically.

For example, IT administrators using Atera can use AI Copilot to generate scripts for specific process killing using natural language, such as “kill all Chrome processes using more than 500MB of RAM” or “terminate any process that’s been running for more than 24 hours.” They can then deploy the PowerShell script remotely using Atera’s RMM platform to all endpoints simultaneously.

Here’s an example of how to kill processes with PowerShell:

1. Open PowerShell as Administrator

2. You can view all processes with the <Get-Process> command, but you can also improve filtering through more complex commands. For example, <Get-Process | Select-Object Name, Id, CPU, PM | Sort-Object CPU -Descending> will show process names, PIDs, CPU time, and memory sorted by CPU usage.

3. Terminate the process by name or PID using these commands:

• By name: <Stop-Process -Name “processname” -Force>. Note: you can omit the .exe extension as PowerShell doesn’t need it, and the -Force flag bypasses confirmation prompts and ensures termination, which is useful for automation.
• By PID: <Stop-Process -Id {number} -Force>

Note: PowerShell won’t tell you if it completed successfully, so if you don’t get any message then it’s usually a good sign. However, it might still give you an error message if something went wrong, like “Stop-Process : Cannot stop process … Access is denied”.

The beauty of PowerShell is that, if you want, you can add error handling to scripts to force the program to show you if it completed successfully or not (obviously this takes slightly more scripting knowledge).

Here are some examples of PowerShell commands you can paste to be more specific with what you terminate:

• Kill all processes using more than 500MB of memory: Get-Process | Where-Object {$_.WorkingSet -gt 500MB} | Stop-Process -Force
• Kill all processes from a specific company: Get-Process | Where-Object {$_.Company -eq “CompanyName”} | Stop-Process -Force
• Kill all processes running longer than 24 hours: Get-Process | Where-Object | Stop-Process -Force
• Kill specific processes on remote computers: Invoke-Command -ComputerName “PC01” -ScriptBlock { Stop-Process -Name “notepad” -Force }

» Still not working? Try restarting the computer remotely

From manual fixes to automated enterprise management

Knowing how to kill a Windows process is a fundamental IT skill, but the method you choose matters, and the key is matching the tool to the situation. Task Manager is great for isolated troubleshooting, Command Prompt for simple scripts and batch files, and PowerShell when you need conditional logic or enterprise-scale automation.

For IT teams managing multiple endpoints, manual process termination quickly becomes unsustainable if something starts acting weird. Atera transforms reactive troubleshooting into proactive management through autonomous IT and automation. AI Copilot helps technicians generate custom PowerShell scripts with vibe coding principles (no coding expertise required) that can be deployed and monitored from the RMM platform.

» Sound good? You can try Atera for free