Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Windows: App unusable after update — file lock + spawn EBUSY (v1.3561.0.0)[BUG]

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…

Error Message

never launched again — "File is in use by another program" error

Error Messages/Logs

never launched again — "File is in use by another program" error

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Clicked "Update" in Claude Desktop on Windows 11. App closed and never launched again — "File is in use by another program" error at C:\Program Files\WindowsApps\Claude_1.3561.0.0_x64__pzs8sxrjxfjjc.

CoworkVMService locks package files. Set-Service and sc.exe return "Access Denied" even with admin rights. Had to disable service via registry (HKLM Start=4).

After full reinstall (Remove-AppxPackage + reinstall), sending messages fails with "spawn EBUSY". 9+ claude.exe processes pile up every send attempt.

Spent 2+ hours middle of the night fixing this. Script crashed due to forced reboot. App still doesn't work. Paid Max subscription.

Version: 1.3561.0.0 OS: Windows 11 Install: MSIX / Microsoft Store

What Should Happen?

The paid app have to start working

Error Messages/Logs

Steps to Reproduce

Clicked "Update" in Claude Desktop on Windows 11. App closed and never launched again — "File is in use by another program" error at C:\Program Files\WindowsApps\Claude_1.3561.0.0_x64__pzs8sxrjxfjjc.

CoworkVMService locks package files. Set-Service and sc.exe return "Access Denied" even with admin rights. Had to disable service via registry (HKLM Start=4).

After full reinstall (Remove-AppxPackage + reinstall), sending messages fails with "spawn EBUSY". 9+ claude.exe processes pile up every send attempt.

Spent 2+ hours middle of the night fixing this. Script crashed due to forced reboot. App still doesn't work. Paid Max subscription.

Version: 1.3561.0.0 OS: Windows 11 Install: MSIX / Microsoft Store

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

N/A — Desktop App issue, not CLI

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

extent analysis

TL;DR

The issue can be potentially resolved by disabling the CoworkVMService and removing any leftover claude.exe processes to prevent file locking and "spawn EBUSY" errors.

Guidance

  • Disable the CoworkVMService via registry (HKLM Start=4) to prevent it from locking package files, as this has been identified as a contributing factor to the issue.
  • Manually terminate any leftover claude.exe processes to prevent them from piling up and causing "spawn EBUSY" errors during send attempts.
  • Consider performing a clean uninstall and reinstall of the Claude Desktop app to ensure all associated files and services are properly removed and reconfigured.
  • Verify that the issue persists after these steps to determine if further troubleshooting is needed.

Example

No specific code snippet is applicable in this case, as the issue appears to be related to service configuration and file locking rather than code-level errors.

Notes

The provided information suggests that the issue is specific to the Windows 11 environment and the MSIX/Microsoft Store installation method. The fact that it worked in a previous version implies a potential regression, but without knowing the last working version, it's challenging to pinpoint the exact cause.

Recommendation

Apply the workaround by disabling the CoworkVMService and removing leftover processes, as this directly addresses the identified symptoms and may provide a temporary solution until a more permanent fix is available.

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…
#api#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

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

Back to top recommendations

TRENDING