claude-code - 💡(How to fix) Fix Windows Store: Claude desktop fails to update due to CoworkVMService file lock and stuck WindowsApps\Deleted [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

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#46179Fetched 2026-04-11 06:27:03
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×5commented ×1

Error Message

  1. Update fails, app won't relaunch — "file in use" error

Root Cause

Two issues combine to block the update:

Fix Action

Workaround

Migrated to standalone install via winget install Anthropic.Claude which uses Squirrel auto-updater and installs to %LOCALAPPDATA%\Programs\ — avoids WindowsApps entirely. AppData (%APPDATA%\Claude\) is preserved across migration.

Code Example

Stop-Service CoworkVMService -Force
Set-Service CoworkVMService -StartupType Disabled
Stop-Process -Name cowork-svc -Force
Stop-Process -Name chrome-native-host -Force
# Then update/reinstall from Store, or better: switch to winget
RAW_BUFFERClick to expand / collapse

Environment

  • OS: Windows 11 Pro 10.0.26200
  • Claude Desktop: 1.1617.0.0 (Microsoft Store / MSIX package)
  • Package: Claude_1.1617.0.0_x64__pzs8sxrjxfjjc

Problem

Claude desktop installed from the Windows Store fails to update. The app closes for update (beforeQuitForUpdate handler fired, going down for update in main.log) but never restarts. Subsequent manual launch attempts fail with:

"Файл занят другой программой" (File is in use by another program) Path: C:\Program Files\WindowsApps\Claude_1.1617.0.0_x64__...

Root cause

Two issues combine to block the update:

1. CoworkVMService holds file locks on the package directory

The Windows service CoworkVMService runs cowork-svc.exe from inside the MSIX package folder (C:\Program Files\WindowsApps\Claude_1.1617.0.0_x64__pzs8sxrjxfjjc\app\resources\cowork-svc.exe). When the app closes for update, the service keeps running and auto-restarts if the process is killed (Stop-Process). This locks the package files, preventing the Store from replacing them.

Stop-Service CoworkVMService -Force is required before the package can update, but the update mechanism does not do this automatically.

2. WindowsApps\Deleted cleanup failures (secondary)

Old package versions from other apps get stuck in C:\Program Files\WindowsApps\Deleted\ with recurring Event ID 493 errors ("Cannot delete files from Deleted directory") every 6 minutes in Microsoft-Windows-AppXDeploymentServer/Operational. While not Claude-specific, this further jams the Store update pipeline.

Expected behavior

The auto-updater should stop CoworkVMService before attempting to replace the package files, or the service should gracefully exit when the main app signals beforeQuitForUpdate.

Workaround

Migrated to standalone install via winget install Anthropic.Claude which uses Squirrel auto-updater and installs to %LOCALAPPDATA%\Programs\ — avoids WindowsApps entirely. AppData (%APPDATA%\Claude\) is preserved across migration.

Steps to reproduce (Store version)

  1. Install Claude desktop from Microsoft Store
  2. Use the app normally (CoworkVMService starts automatically)
  3. Wait for an auto-update trigger
  4. App closes with "going down for update" but CoworkVMService keeps running
  5. Update fails, app won't relaunch — "file in use" error

Manual fix sequence (if still on Store)

Stop-Service CoworkVMService -Force
Set-Service CoworkVMService -StartupType Disabled
Stop-Process -Name cowork-svc -Force
Stop-Process -Name chrome-native-host -Force
# Then update/reinstall from Store, or better: switch to winget

extent analysis

TL;DR

Stop the CoworkVMService before updating the Claude desktop app to prevent file locks and allow the update to complete.

Guidance

  • Identify if CoworkVMService is running and stop it using Stop-Service CoworkVMService -Force to release file locks.
  • Consider disabling the CoworkVMService startup to prevent it from interfering with future updates.
  • If the issue persists, try stopping the cowork-svc and chrome-native-host processes using Stop-Process to ensure all related processes are terminated.
  • As a more reliable solution, migrate to the standalone install using winget install Anthropic.Claude to avoid WindowsApps-related issues.

Example

The manual fix sequence provided in the issue can be used to stop the interfering services and processes:

Stop-Service CoworkVMService -Force
Set-Service CoworkVMService -StartupType Disabled
Stop-Process -Name cowork-svc -Force
Stop-Process -Name chrome-native-host -Force

Notes

The CoworkVMService and its related processes can cause file locks, preventing the update from completing. Stopping these services and processes can resolve the issue, but migrating to the standalone install may be a more reliable solution.

Recommendation

Apply the workaround by migrating to the standalone install using winget install Anthropic.Claude, as it avoids the WindowsApps-related issues and uses a different auto-updater. This approach also preserves the AppData across migration.

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

The auto-updater should stop CoworkVMService before attempting to replace the package files, or the service should gracefully exit when the main app signals beforeQuitForUpdate.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING