Forumics logo Forumics
Issue 01

Back to issue

All Claude Code known issues

CLAIM C141 Supported 2026-11-16

GitHub issue #91763 in anthropics/claude-code, opened 2026-09-03 by sheelcheyne, records a report that after the Claude Desktop auto-updater stages a new MSIX version and force-relaunches the app, every subsequent launch fails with the dialog "Another program is currently using this file" (HRESULT 0x80070020, AppModel-Runtime events 215/208), because the old version's Desktop AppX container is kept alive by a detached git fsmonitor--daemon process that a Claude Code session spawned indirectly; terminating that process destroyed the old container the same second and the next launch succeeded with no reboot and no elevation; the reporter reproduced this three times in 24 hours across three consecutive updates (1.40609.1 to 1.44121.1 to 1.44121.2 to 1.44121.4); the report was filed against Claude Code 2.1.259 bundled with Claude Desktop 1.44121.4.0 on Windows 11.

Verbatim Excerpts from Cited Records
“After the Claude Desktop auto-updater stages a new MSIX version and force-relaunches the app, every subsequent launch fails with the dialog "Another program is currently using this file" (HRESULT 0x80070020, AppModel-Runtime events 215/208).”
— sheelcheyne · anthropics/claude-code (issue 91763 opening body, What's Wrong section) · 2026-09-03T10:18:15Z ·GitHub Issue ↗
“The old version's Desktop AppX container is kept alive by a detached `git fsmonitor--daemon` process that a Claude Code session (Desktop Code tab) spawned indirectly.”
— sheelcheyne · anthropics/claude-code (issue 91763 opening body, What's Wrong section) · 2026-09-03T10:18:15Z ·GitHub Issue ↗
“Terminating PID 32504 produced event 217 for `{36DD7527-…}` the same second, and the next launch of 1.44121.2.0 succeeded (event 201, process created).”
— sheelcheyne · anthropics/claude-code (issue 91763 opening body, Proof section) · 2026-09-03T10:18:15Z ·GitHub Issue ↗
“Reproduced three times in 24 hours (1.40609.1 → 1.44121.1 on 2026-09-02; 1.44121.1 → 1.44121.2 and 1.44121.2 → 1.44121.4 on 2026-09-03).”
— sheelcheyne · anthropics/claude-code (issue 91763 opening body, Steps to Reproduce section) · 2026-09-03T10:18:15Z ·GitHub Issue ↗
Counter-record: Issue closed 2026-11-15 by bpasero-ant as a duplicate of #73107, to keep the discussion in one place. 21 comments were read. dannykQuali (2026-09-03) confirmed the same mechanism with a different culprit, a detached Node process running a Claude usage-guard driver, and reported a second failure that survived clearing the container; KE9CFN (2026-09-06) confirmed with Android's ADB server as the sole surviving container member; mustalk (2026-09-07) confirmed with Git for Windows GnuPG agents (gpg-agent, keyboxd, scdaemon) from a signed commit; alexbereznikov (2026-09-09) confirmed with npx-spawned MCP servers and the bundled Claude Code CLI; DanCathers (2026-09-22) confirmed with three git fsmonitor--daemon processes on an update from 2.2553.1.0 to 2.2553.13.0; TaiwanTammy (2026-09-23), Disaer (2026-09-28, Monitor tail/grep watchers) and Fuzzied (2026-10-04, a hook-started Java daemon and restarted background servers) added further confirmations. m13v argued in several comments that breaking children out of the container job with CREATE_BREAKAWAY_FROM_JOB would trade the loud launch failure for a silent daemon leak and remove the container-membership signal used to find survivors. No fix release and no retraction of the original report appear in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #91763 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.