claude-code - 💡(How to fix) Fix Windows: MSIX update fails — Desktop processes don't terminate, causing file lock [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45489Fetched 2026-04-09 08:04:14
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
0
Author
Timeline (top)
commented ×1labeled ×1

Error Message

When an update is available, Claude Desktop downloads it but cannot apply it. Windows MSIX shows the error "Ce fichier est utilisé par une autre application" (file in use by another application).

Root Cause

The root cause: Claude Desktop spawns 10-12 background processes (Helper, GPU, Renderer) that remain running after the user closes the main window. Windows MSIX cannot replace files of a running app, so it marks the update as "deferred registration" — but the deferred update never completes because the ghost processes never terminate.

Fix Action

Workaround

A scheduled task that kills windowless Claude processes nightly (Get-Process claude | Where-Object { $_.MainWindowHandle -eq 0 -and $_.Path -like "*WindowsApps*" } | Stop-Process -Force).

Code Example

"Marquage du package Claude_1.1348.0.0_x64__pzs8sxrjxfjjc pour l'inscription différée, 
car Claude_1.1062.0.0_x64__pzs8sxrjxfjjc est toujours en cours d'exécution."

"Les packages n'ont pas été mis à jour, car les applications concernées sont toujours 
en cours d'exécution. Applications en cours d'exécution: {Claude_pzs8sxrjxfjjc!Claude}"
RAW_BUFFERClick to expand / collapse

Environment

  • OS: Windows 11 Home 10.0.26200
  • Install method: Microsoft Store (MSIX package)
  • Current version: Claude_1.1062.0.0_x64__pzs8sxrjxfjjc
  • Pending update: Claude_1.1348.0.0_x64__pzs8sxrjxfjjc

Problem

When an update is available, Claude Desktop downloads it but cannot apply it. Windows MSIX shows the error "Ce fichier est utilisé par une autre application" (file in use by another application).

The root cause: Claude Desktop spawns 10-12 background processes (Helper, GPU, Renderer) that remain running after the user closes the main window. Windows MSIX cannot replace files of a running app, so it marks the update as "deferred registration" — but the deferred update never completes because the ghost processes never terminate.

Even killing processes via Task Manager doesn't fully work, as some child processes respawn or aren't visible.

Windows Event Log evidence

"Marquage du package Claude_1.1348.0.0_x64__pzs8sxrjxfjjc pour l'inscription différée, 
car Claude_1.1062.0.0_x64__pzs8sxrjxfjjc est toujours en cours d'exécution."

"Les packages n'ont pas été mis à jour, car les applications concernées sont toujours 
en cours d'exécution. Applications en cours d'exécution: {Claude_pzs8sxrjxfjjc!Claude}"

Process list at time of failed update

12 claude.exe processes running from C:\Program Files\WindowsApps\Claude_1.1062.0.0_x64__pzs8sxrjxfjjc\app\Claude.exe, most without a visible window (ghost processes).

Impact

User must fully reboot the PC to apply every update. This happens consistently on every update cycle.

Expected behavior

Claude Desktop should properly terminate all child processes when the user quits the app via the system tray. Alternatively, register an MSIX UpdateTask or RestartAppAfterUpdate capability to handle graceful shutdown during updates.

Workaround

A scheduled task that kills windowless Claude processes nightly (Get-Process claude | Where-Object { $_.MainWindowHandle -eq 0 -and $_.Path -like "*WindowsApps*" } | Stop-Process -Force).

extent analysis

TL;DR

Implement a proper shutdown mechanism for Claude Desktop to terminate all child processes when the user quits the app.

Guidance

  • Investigate and modify the application's shutdown logic to ensure all background processes (Helper, GPU, Renderer) are terminated when the main window is closed.
  • Consider registering an MSIX UpdateTask or RestartAppAfterUpdate capability to handle graceful shutdown during updates.
  • Review the scheduled task workaround that kills windowless Claude processes nightly to determine if it can be adapted as a temporary solution.
  • Verify that the update process completes successfully after implementing the shutdown mechanism or workaround.

Example

No code snippet is provided as the issue does not specify the programming language or framework used by Claude Desktop.

Notes

The provided workaround using a scheduled task may not be suitable for all users, and a more robust solution should be implemented to properly handle application shutdown and updates.

Recommendation

Apply the workaround using a scheduled task to kill windowless Claude processes nightly, as it provides a temporary solution to the update issue, while working on implementing a proper shutdown mechanism for Claude Desktop.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Claude Desktop should properly terminate all child processes when the user quits the app via the system tray. Alternatively, register an MSIX UpdateTask or RestartAppAfterUpdate capability to handle graceful shutdown during updates.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING