When an app stops repainting its window and ignores the close button, its message loop has usually stopped processing input. Clicking the X sends a polite close request that the app never reads. Ending the task skips that request, and Windows terminates the process directly. Most methods below work on both Windows 10 and Windows 11; the taskbar End task shortcut is limited to Windows 11.
End task
To end a task in Windows, press Ctrl+Shift+Esc, select the frozen app on the Processes tab, and click End task. You can also right-click its Windows 11 taskbar icon (once the End task toggle is on), run taskkill /IM app.exe /F in Command Prompt, or run Stop-Process -Name app -Force in PowerShell. Ending a task force-closes the process, so any unsaved work in that app is lost.
| Method | Where / command | Scope | Which processes end |
|---|---|---|---|
| Task Manager End task | Ctrl+Shift+Esc > Processes > End task | Local | The processes grouped under that app entry (varies by app) |
| End process tree | Details tab > right-click > End process tree | Local | Yes |
| Taskbar End task | Right-click taskbar icon > End task | Local, Windows 11 | The app behind that taskbar icon (exact processes vary by app) |
| taskkill | taskkill /IM app.exe /F | Local or remote (/S) | Child processes too with /T |
| Stop-Process | Stop-Process -Name app -Force | Local | Only the matched processes |
| CIM Terminate | Get-CimInstance Win32_Process | Invoke-CimMethod -MethodName Terminate | Remote | Only the matched processes |
How to End a Task in Task Manager
1. Open Task Manager and end the app
Press Ctrl+Shift+Esc. On the Processes tab, select the frozen app and click End task. The row usually disappears shortly afterward, though some processes take longer to tear down and can stay listed briefly while that finishes.
2. Use the Details tab for stubborn processes
One entry on the Processes tab can group several processes together. The Details tab lists each executable and its PID. Right-click the process and choose End task to kill only that PID. Choose End process tree to also kill everything it spawned. Use the tree option for launchers and browsers whose helper processes keep holding file locks.
Enable End Task on the Windows 11 Taskbar
Where the toggle lives depends on your Windows 11 version. On version 25H2 and later it’s under Settings > System > Advanced. On earlier versions that include the feature (22H2 through 24H2, kept up to date), it’s under Settings > System > For developers. If you don’t see it on either page, your build may be too old or a policy may be hiding it. To check your version, go to Settings > System > About.
- Open the correct page and turn End task to On. You don’t need Developer Mode. The End task toggle works on its own.
- Right-click the frozen app’s taskbar icon and choose End task.
Is the toggle greyed out or missing on a work PC? Your organization’s management policy is probably hiding it. Fall back to Task Manager or the commands below (BleepingComputer, PCWorld).
End a Task with taskkill and Stop-Process
3. taskkill locally
A normal Command Prompt can end processes running under your own account. Use an elevated (Run as administrator) prompt for services, system processes, and other users’ processes. The switches are documented on Microsoft Learn.
:: /IM targets an image name, /F forces termination, /T includes child processes
taskkill /IM notepad.exe /F /T
:: Kill one specific PID
taskkill /PID 4512 /F
:: /FI filters processes, here every app that isn't responding
taskkill /F /FI "STATUS eq NOT RESPONDING"
SUCCESS: The process "notepad.exe" with PID 4512 (child process of PID 3120) has been terminated.
Without /F, taskkill sends a close request instead. A hung app ignores that request, same as it ignores the X button.
4. taskkill on a remote PC
:: /S target host, /U account, /P password (omit /P to be prompted)
taskkill /S PC01 /U CORP\your-username /IM notepad.exe /F
The STATUS and WINDOWTITLE filters don’t work with /S. Filter by image name or PID instead.
5. Stop-Process in PowerShell
# -WhatIf shows what would be killed without killing anything
Get-Process -Name chrome | Stop-Process -WhatIf
# -Force stops the process without prompting for confirmation; it doesn't grant rights
# to processes owned by other accounts (permissions and elevation still apply)
Stop-Process -Name chrome -Force
Stop-Process -Id 4512 -Force -PassThru # -PassThru prints the stopped process
Stop-Process prints nothing on success unless you add -PassThru. To confirm the process is gone, run Get-Process -Id 4512. It should return an error.
6. Remote PowerShell termination
Each remote method has its own prerequisites. Check the one you plan to use:
- All remote methods: an account with rights to end the target process on the remote PC. Ending another user’s or a system process typically needs local administrator rights there; policy and the process’s protection level can still block it.
taskkill /S: the target must be reachable over the network and accept your credentials (/Uand/P), and Windows Firewall on the target must allow the remote management traffic taskkill uses.Invoke-Command: PowerShell remoting enabled on the target (Enable-PSRemoting), WinRM reachable through the firewall, and authentication that works between the two machines (Kerberos in a domain, or TrustedHosts/HTTPS in a workgroup).Get-CimInstance -ComputerName: per Microsoft Learn,-ComputerNamecreates a temporary session using the WS-Man protocol, so WinRM must be listening and allowed through the firewall. If WinRM isn’t available, create a DCOM-based session withNew-CimSessionOption -Protocol DcomandNew-CimSession, then pass it with-CimSession.
# Requires PowerShell remoting (Enable-PSRemoting on the target)
Invoke-Command -ComputerName PC01 -ScriptBlock { Stop-Process -Name notepad -Force }
# CIM over a temporary WS-Man (WinRM) session; the replacement for wmic process delete
Get-CimInstance -ClassName Win32_Process -Filter "Name='notepad.exe'" -ComputerName PC01 |
Invoke-CimMethod -MethodName Terminate
ReturnValue PSComputerName
----------- --------------
0 PC01
A ReturnValue of 0 means the Terminate call completed without error. It doesn’t guarantee the process has already disappeared from the process list, since cleanup can be delayed by a driver or kernel wait.
Skip wmic process delete. Microsoft deprecated WMIC in Windows 10 version 21H1, and its deprecated-features list (August 2026 update) says WMIC is removed and no longer available as a Feature on Demand on Windows 11 version 24H2 and later (Microsoft Learn: Deprecated features in the Windows client). Older machines may still have it, but CIM is the supported path. Action1 walks through other remote-kill options.
Why End Task Fails
“Access is denied”: The process usually runs as SYSTEM or as another user, or it’s a protected process. Reopen the console with Run as administrator and try again. Some protected processes still can’t be ended, even by an administrator.
The process comes back immediately: A Windows service owns it and restarts it. Stop the service with Stop-Service -Name ServiceName or sc stop ServiceName instead of killing the process. For svchost.exe, identify which service is inside first.
The process is still listed after a successful kill: Give it a few seconds and refresh first; the list may be stale or teardown may still be running. Also check whether a service restarted it under a new PID. If the same PID stays listed, a thread may be stuck waiting on a driver request, and Windows can’t finish tearing the process down until that request returns. In that case a reboot is often the practical fix.
Critical system processes: Don’t kill csrss.exe, wininit.exe, smss.exe or lsass.exe. Windows protects several of these, and the result of forcing one closed varies by process, Windows version, and session. It can crash Windows or sign you out of the session, so treat them as off-limits.
Wrapping Up
For a single frozen app, the taskbar End task entry is the quickest option once you’ve enabled it. For anything scripted or remote, use taskkill /S or the CIM Terminate method.
CIM termination commonly relies on a WinRM-based session, which isn’t always enabled on desktop machines by default. If a kill fails twice, check for a service or a driver wait before you reboot.