[BUG] Claude for Desktop not exiting
Resolved 💬 22 comments Opened Dec 25, 2025 by stanciuadrian Closed Feb 28, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When I try to Exit Claude desktop, either via the main menu (File -> Exit) or taskbar icon (right click -> Exit), the main window disappears but the process is still running in the background.
If I try to start Claude desktop again (after clicking Exit once), the main window will show for 1-2s then disappear.
Unless the process is terminated via Task Manager, one cannot use the application again.
What Should Happen?
The 6-7 Claude processes should terminate and release the occupied RAM.
Error Messages/Logs
Steps to Reproduce
- Start Claude for Desktop
- (main menu) File -> Exit or (taskbar icon) right click -> Exit
- Examine the taskbar icon; Claude icon still there
- Start Claude for Desktop again
- The main window shows for 1-2s then disappears.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
Claude 1.0.2339 (1782e2) 2025-12-16T19:35:52.000Z
Platform
Other
Operating System
Windows
Terminal/Shell
Other
Additional Information
_No response_
22 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Before clicking Exit, task manager shows 7 Claude processes: main spawning 6 others (crashpad + gpu-process + utility + 3x renderer)
After clicking Exit, only 1x renderer terminates.
+1
Same here
After I close the app, any attempts to reopen it result in a brief launching window before the window disappears. The tray icon is not present either. When I toggle settings to have the tray icon on after closing, I still cannot relaunch the app without first closing with task manager. If I click the tray icon to launch a new chat, the new chat appears to submit but again fails to launch.
+1. Guessing the quit button was written by AI :)
+1
+1
Been noticing that for weeks. Affects both Windows and Mac OS.
IT IS a regression, obviously.
Sorry if that sounds rude, but...
A process that refuses to terminate properly isn't some obscure edge case in an advanced feature - it's a fundamental application lifecycle bug. We're talking Software Development 101 here. Being able to close an application is literally the most basic function that exists. This should be a P0 critical issue, not something left unfixed for weeks.
Claude has no match in its own realm, but a bug like this surviving for weeks is actually insane. We're talking Windows AND Mac OS here. Of course claude.ai remains normally usable, but a company such as anthropic can't underestimate the impact of this problem. I mean, what if you are a first time user who just downloaded the app ? You'll never get to understand how Claude can integrate into your workflow or change the way you work, because all you'll see is a desktop app unable to properly terminate. Any user from basic to advanced will run away as he sees that. Do you guys need help ? 💃 😃
Same here, I'm forced to kill Claude tasks
+1 to this issue, it's been happening for a few weeks now.
+1
+1
+1
+0
Has apparently been fixed, at least on Mac OS :)
Will be checking windows later and editing.
no longer reproduces on Windows (on my machine™️):
Claude 1.0.2768 (21341c) 2026-01-05T18:21:10.000ZFixed also for me on Windows 11
Found the cause: This bug only occurs when "Show Claude in menu bar" is disabled.
Environment: Claude Version 1.1.351 (648bf5), Windows 11
The fix: Enable the "Menu bar" setting under Desktop app → General. With this on, quitting from the system tray properly terminates all processes. With it off, zombie processes persist.
---
What's happening:
When the tray setting is enabled, Claude lives in the system tray (the small icons near the clock). To fully quit, you right-click the tray icon and select Exit — standard behavior for tray apps.
When the tray setting is disabled, Claude doesn't appear in the tray, but it still seems to require being quit from there. Since there's no tray icon to access, there's no way to properly exit — hence the orphaned processes that can only be killed via Task Manager.
---
Side note on terminology: The setting says "menu bar" (Mac terminology), but on Windows this controls the system tray / notification area. The original issue mentions "taskbar icon" which could mean either the main taskbar button or the tray icon — worth clarifying.
---
Additional observations:
+1 here
I just created a desktop shortcut for
taskkill /f /im claude.exeas it's way quicker than even exiting from the context menu.+1 on mac
i will often not even try to open claude and use other LLMs because i know it won't launch
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
I'm absolutely furious about this bug that is still present today.
Windows Claude Desktop stay in the tray icon forever even if Exit from context menu has been invoked.
It consumes a large amount of CPU, and the only way is to kill the application from task manager.
Why ? Why ? Why ?
This is a basic dumb quality control, guys!
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.