Unable to Terminate Process Access Denied? Fix It

Updated 7 November 2026 · Standard formula, shown below

If Windows says “Unable to terminate process: Access is denied,” it usually means the process is running with higher privileges than your current user account, or it is protected by the operating system. The fix is to close it with an elevated (Administrator) Command Prompt, use Task Manager’s “End Task” after taking ownership, or use a dedicated tool like Process Explorer. Below is a full breakdown of why this happens and every reliable way to resolve it.

Why Windows Blocks Process Termination

Windows enforces security tokens on every process. A process started by an administrator, by the SYSTEM account, or by another user cannot be killed by a standard user—even if that user is in the Administrators group but has not elevated their own token. This is the same mechanism that prevents a normal app from closing antivirus software or core system services. The error message “Access is denied” is Windows’ way of saying your token lacks the SeDebugPrivilege or the target process’s security descriptor does not grant you the PROCESS_TERMINATE right.

Another common cause is that the process is a protected process (like parts of Windows Defender or certain drivers) or it is stuck in a kernel-mode state that cannot be interrupted from user mode. In those cases, even an administrator cannot kill it directly; you must stop the parent service or reboot.

Fix 1: Use an Elevated Command Prompt

The simplest fix is to run the kill command as administrator. This gives your token the necessary privileges.

Click Start, type cmd, right-click “Command Prompt,” and choose “Run as administrator.”
Type tasklist | findstr "processname" to confirm the exact process name (e.g., notepad.exe).
Type taskkill /F /IM processname.exe and press Enter.
If that fails with “Access denied,” try taskkill /F /PID <PID> using the process ID from the tasklist output.
If you still get the error, the process may be running as SYSTEM. Use psexec -s taskkill /F /IM processname.exe (from Sysinternals) to run the command as SYSTEM.

This works for most third-party apps and even some system services. If the process is a service, you can also try net stop <servicename> in the same elevated prompt.

Fix 2: End Task in Task Manager with Elevated Privileges

Task Manager itself must be running as administrator to kill elevated processes. If you opened Task Manager normally, it cannot end a process that is elevated.

Press Ctrl+Shift+Esc to open Task Manager.
If you see “Fewer details,” click “More details.”
Click “Details” tab, right-click the process, and choose “End task.”
If you get an error, close Task Manager, right-click its shortcut, and select “Run as administrator.” Then try again.

For processes that still refuse to die, right-click the process in the “Details” tab, choose “Analyze wait chain,” and kill the parent process first. Often the child process is owned by a service that will restart it immediately.

Fix 3: Take Ownership and Change Permissions

Some processes are protected by file-level permissions on their executable. If the process is a service or a scheduled task, you can take ownership of the executable file and then stop the service.

Open an elevated Command Prompt.
Type takeown /f "C:\Path\to\process.exe" and press Enter.
Type icacls "C:\Path\to\process.exe" /grant administrators:F and press Enter.
Then use sc stop <servicename> or taskkill /F /IM processname.exe again.

This is rarely needed for ordinary apps, but it is the standard fix for malware that has locked its own file or for stubborn system components.

Fix 4: Use Process Explorer (Sysinternals)

Process Explorer, a free Microsoft tool, can kill processes that Task Manager cannot, because it can run with a SYSTEM token and shows the exact security context of each process.

Download Process Explorer from Microsoft’s Sysinternals site.
Run it as administrator (right-click → “Run as administrator”).
Find the process in the list, right-click it, and choose “Kill Process.”
If it still fails, right-click the process and choose “Kill Process Tree” to kill all child processes first.
You can also right-click the process and select “Properties” → “Security” to see which user owns it.

Process Explorer is especially useful when you need to kill a process that is running as SYSTEM or when you need to see the command line and parent process to understand why it is protected.

What to Do When Nothing Works

If all of the above fail, the process is likely a protected system process, a driver, or part of Windows itself. In that case, do not try to force it with third-party “force kill” tools—that can cause a blue screen or corrupt system files. Instead, try these safe alternatives:

Reboot the computer – Many stuck processes are cleared on restart.
Disable the related service – Open services.msc, find the service that owns the process, right-click → “Properties,” set “Startup type” to “Disabled,” then reboot.
Use Safe Mode – Boot into Safe Mode (Shift + Restart → Troubleshoot → Advanced options → Startup Settings → Restart → press 4). In Safe Mode, most non-essential processes are not running, so you can delete or disable the offending file.
Check for malware – Some malware hides as a system process and blocks termination. Run a full antivirus scan with Windows Defender or a reputable third-party scanner.

If the process is a legitimate Windows component (like csrss.exe, wininit.exe, or lsass.exe), do not attempt to kill it—doing so will crash your system.

Common Misconceptions

Many users believe that “Access is denied” means they need to log in as the built-in Administrator account. That is rarely true—the built-in Administrator account still needs to be elevated, and it cannot kill protected processes either. Another misconception is that ending a process in Task Manager always works; in reality, Task Manager cannot kill processes that are running with a higher integrity level. Finally, some think that restarting the process will solve the problem, but if the parent service restarts it automatically, it will come back with the same protection.

Frequently Asked Questions

Q: Why does “taskkill /F” say access denied even when I run as administrator?
Because the target process is running as SYSTEM or is a protected process. You need to run the command as SYSTEM (using psexec) or use Process Explorer with a SYSTEM token.

Q: Can I kill a process that is stuck and not responding?
Yes, if it is a normal user process. Use Task Manager’s “End task” or taskkill /F in an elevated prompt. If it is a system process, a reboot is safer.

Q: What is the difference between “End task” and “End process tree”?
“End task” kills only the selected process. “End process tree” kills the process and all its child processes. Use the tree option when the child processes are preventing the parent from closing.

Q: Is it safe to use third-party force-kill tools?
Generally no. They use low-level APIs that can crash your system or leave it in an unstable state. Stick to Microsoft’s tools (Task Manager, Process Explorer, taskkill) and reboot if those fail.

Q: Why does the process come back immediately after I kill it?
Because it is a service or a scheduled task that is configured to restart automatically. Disable the service or scheduled task first, then kill the process.

Q: What if the process is a virus?
Do not try to kill it manually. Run a full antivirus scan in Safe Mode. If the malware blocks the scan, use Windows Defender Offline or a bootable rescue disk.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.