App Not Closing Even With Task Manager | Force Quit Fix

Guide / By

If an app won’t close in Task Manager, end its process tree, restart the shell process, then remove the relaunch trigger.

You click End task. The window vanishes. Then it pops right back up, or the process stays stuck at the top of Task Manager like it owns the place. That loop is annoying, and it can also block shutdown, chew CPU, or keep a file locked.

This guide walks you through fixes that work on Windows 10 and Windows 11, starting with the fastest moves and ending with deeper repairs. You’ll also learn why some apps survive End task and what to change so it stops happening.

Why An App Can Stay Alive After You End It

Task Manager can close a window, end a process, or end a whole family of processes. When the wrong piece gets killed, the rest can keep running, or a watcher process can bring it back.

Child processes keep running

Some apps split into multiple processes. One handles the window. Others handle updates, add-ons, media, or tabs. Ending the window process can leave the “helpers” running, and one of them may recreate the main process.

A background service relaunches the app

Installers, updaters, sync tools, and “startup boosters” often run as services or scheduled tasks. They can restart the main app the moment it exits, which makes it look like Task Manager failed.

The app is waiting on a stuck driver or device

Apps that talk to GPUs, audio devices, virtual cameras, VPNs, or USB tools can hang while waiting on a driver call. Windows may not be able to tear it down cleanly until the call returns.

The app is running with higher permissions

If the app is elevated (Run as administrator) and Task Manager isn’t, you may be trying to end a process you don’t fully control. On locked-down work PCs, policies can also block termination.

Fast Fixes That Usually Work In Under Five Minutes

Start here when you just need the app gone and you’d prefer not to reboot. These steps also help you confirm whether you’re fighting a single process or a whole process tree.

  1. Save what you can — If the app still responds, save files first. Force-closing can dump unsaved work.
  2. Use End task on the correct entry — In Task Manager, pick the app under the Processes tab, then click End task. If it returns, move to the Details tab next.
  3. End the process tree — Open the Details tab, right-click the app’s process, then choose End process tree. This closes the parent and its child processes.
  4. Restart the shell process — In Task Manager, find the shell process, right-click it, then choose Restart. This refreshes the desktop and clears stuck taskbar hooks.
  5. Log out and back in — Sign out from the Start menu, then sign in again. This is lighter than a reboot and clears many per-user background helpers.

If the shell restarts and the desktop stays blank, keep Task Manager open, click File, choose Run new task, type explorer.exe, then press Enter.

Quick lookup table for common stuck scenarios

What you see What to try Why it helps
Window closes, then reopens End process tree, then disable the app’s startup item Stops a helper process from relaunching it
Process stays “Not responding” Restart the shell process, then use taskkill /F /T Breaks shell hooks, then forces termination
App vanishes, but files stay locked Find child processes in Details and end them Releases the handle that is holding the file
End task is greyed out Run Task Manager as admin Gives permission to end elevated processes

App Not Closing Even With Task Manager On Windows

If you’ve already hit End task and nothing changes, treat it like a relaunch problem, not a “Task Manager is broken” problem. The goal is to find the trigger that keeps the app alive.

Start by watching the process list for a minute. If the app’s process disappears and returns, something restarted it. If it never disappears, you’re dealing with a hung process that needs a stronger kill method.

Check for a second copy hiding in the tray

Some apps keep a tray process alive after the window closes. Click the small arrow near the clock, right-click the app icon, then choose Exit or Quit if it exists.

Turn on the taskbar “End task” option

On many Windows 11 builds, you can enable an End task option on the app’s taskbar icon. Open Settings, go to System, open For developers, then switch on End Task. After that, right-click the app icon on the taskbar and use End task.

Stronger Ways To Kill A Stuck Process

When Task Manager can’t finish the job, the command line and a few built-in tools give you more control. These methods are also handy when the screen freezes or the mouse won’t cooperate.

Use taskkill to force-close the app

  1. Open an elevated terminal — Press Win + X, pick Windows Terminal (Admin) or Command Prompt (Admin).
  2. Find the process name — Run tasklist and look for the app’s .exe name.
  3. Kill by image name — Run taskkill /F /IM appname.exe /T to force-close it and its child processes.
  4. Kill by PID — If you prefer IDs, use taskkill /F /PID 1234 /T.

Use PowerShell for a cleaner stop

  1. List matching processes — Run Get-Process | Where-Object {$_.ProcessName -like "*name*"}.
  2. Stop the process — Run Stop-Process -Name appname -Force.
  3. Stop by ID — Run Stop-Process -Id 1234 -Force when names collide.

Use Resource Monitor to see what it’s waiting on

Open Resource Monitor from Task Manager’s Performance tab (or search for it). Under CPU, expand Associated Handles, type part of a file name, and see which process is holding it. If the stuck app is waiting on a handle, ending the correct process can free everything faster than guessing.

Use Wait Chain To Find What’s Blocking Exit

Some freezes come from one thread waiting on another process, a printer driver, or a network share. When the option shows up, wait chain view points at the blocker.

  1. Open the Details tab — Right-click the stuck process and choose Wait chain if it appears.
  2. Review the waiting list — If another process is listed, that process may be the one holding things up.
  3. End the blocker first — End the listed process, then end the original app again.
  4. Disconnect the dependency — Unplug a stalled USB device or pause a flaky network drive, then retry the close.

Fix The Background Trigger That Keeps Bringing It Back

At this point, you can usually close the app. The next win is stopping the loop so you don’t keep dealing with app not closing even with task manager week after week.

Disable startup items linked to the app

  1. Open the Startup list — In Task Manager, open the Startup apps tab.
  2. Disable the app and its updater — Look for the app name, update helper, launcher, or “tray” entry and disable them.
  3. Reboot once — After a reboot, test closing the app again.

Check Task Scheduler for relaunch tasks

Search for Task Scheduler, open it, then check Task Scheduler Library. Look for tasks that mention the app, its updater, or “assistant” services. Disable the task, then test closing the app. If the loop stops, you found the trigger.

Stop and set a service to Manual

  1. Open Services — Press Win + R, type services.msc, press Enter.
  2. Find related services — Sort by name and look for the app vendor, updater, or “agent” service.
  3. Stop the service — Right-click, choose Stop.
  4. Set Startup type — Set it to Manual, then test closing the app again.

Turn off “run in background” settings

Some apps have a setting like “keep running when closed” or “start with Windows.” Open the app settings, switch those off, then close the app and confirm it stays closed. Also check Windows Settings for background permissions for Store apps.

Look for overlays and plug-ins that hook the app

Screen recorders, FPS overlays, audio enhancers, and browser extensions can keep processes alive. Disable overlays one at a time, then test. If a single tool is the culprit, update it or remove its app hook.

If you see unknown processes relaunching the app, run a Microsoft Defender scan, then remove the add-on that installed it.

Deep Fixes When The Problem Keeps Returning

If the app still refuses to die, the root cause is often a damaged profile, a broken install, or a driver layer that keeps the process stuck in a waiting state. These steps take longer, but they tend to end the cycle.

Try a clean boot to isolate conflicts

  1. Open System Configuration — Press Win + R, type msconfig, press Enter.
  2. Hide Microsoft services — On the Services tab, tick Hide all Microsoft services.
  3. Disable remaining services — Click Disable all, then apply.
  4. Disable startup apps — Open Task Manager from the Startup tab, disable third-party startup items.
  5. Restart and test — If the app closes normally now, re-enable items in batches to find the conflict.

Reinstall the app the clean way

  1. Uninstall from Settings — Settings → Apps → Installed apps, remove the app.
  2. Remove leftover folders — Check %AppData%, %LocalAppData%, and the app’s install folder for leftovers, then delete only folders tied to the app.
  3. Reinstall from the vendor — Download the latest installer from the official site, then install fresh.

Update drivers tied to the app’s workload

Video editors, games, meeting apps, and anything using hardware acceleration can get stuck on GPU or audio drivers. Update graphics and audio drivers from your PC maker, then test closing the app again.

Create a new Windows user profile

If a single account keeps showing the bug, a new profile is a clean test. Create a new local user, sign in, install the app, and see if it closes normally. If it does, your old profile may have a startup hook or corrupted setting that keeps the process alive.

Use Safe Mode for a stubborn uninstall

Safe Mode loads fewer drivers and startup items, which can make a stuck process easier to remove. Boot into Safe Mode, uninstall the app, reboot normally, then reinstall. This often clears “relaunch agents” that resist removal.

Once the loop is gone, keep an eye on updates. If the issue returns after an update, roll back that app version, then report the bug to the vendor with the app name, Windows version, and steps that reproduce it.

If you landed here because app not closing even with task manager is blocking shutdown, try the process tree method first, then use taskkill with /T. That pairing fixes most cases without a full reinstall.