claude-code - 💡(How to fix) Fix Windows: 'Another program is currently using this file' when clicking Relaunch to update [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#45400Fetched 2026-04-09 08:06:17
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4commented ×1cross-referenced ×1

Error Message

On Windows 11, clicking "Relaunch" when a Claude Desktop update is available always fails with the error: "another program is currently using this file." This happens every time.

Root Cause

The CoworkVMService Windows service (cowork-svc.exe) remains running during the update process. It holds file locks on the MSIX package directory (C:\Program Files\WindowsApps\Claude_*). The service has StartupType = Automatic with auto-recovery, so it restarts immediately even if manually killed. Disabling it requires admin privileges that the updater doesn't have.

Fix Action

Workaround

Run the following in an admin PowerShell before clicking Relaunch:

Stop-Service CoworkVMService -Force
Set-Service CoworkVMService -StartupType Disabled
# Click Relaunch now
# After update, re-enable:
Set-Service CoworkVMService -StartupType Automatic
Start-Service CoworkVMService

Code Example

Stop-Service CoworkVMService -Force
Set-Service CoworkVMService -StartupType Disabled
# Click Relaunch now
# After update, re-enable:
Set-Service CoworkVMService -StartupType Automatic
Start-Service CoworkVMService
RAW_BUFFERClick to expand / collapse

Bug Description

On Windows 11, clicking "Relaunch" when a Claude Desktop update is available always fails with the error: "another program is currently using this file." This happens every time.

Root Cause

The CoworkVMService Windows service (cowork-svc.exe) remains running during the update process. It holds file locks on the MSIX package directory (C:\Program Files\WindowsApps\Claude_*). The service has StartupType = Automatic with auto-recovery, so it restarts immediately even if manually killed. Disabling it requires admin privileges that the updater doesn't have.

Expected Behavior

The updater should stop CoworkVMService before replacing package files, then restart it after the update completes.

Workaround

Run the following in an admin PowerShell before clicking Relaunch:

Stop-Service CoworkVMService -Force
Set-Service CoworkVMService -StartupType Disabled
# Click Relaunch now
# After update, re-enable:
Set-Service CoworkVMService -StartupType Automatic
Start-Service CoworkVMService

Environment

  • OS: Windows 11 Pro 10.0.22631
  • Claude Desktop version: 1.1062.0.0 (MSIX/Windows Store install)
  • Package: Claude_pzs8sxrjxfjjc
  • Service: CoworkVMServiceapp\resources\cowork-svc.exe

extent analysis

TL;DR

To fix the update issue, stop the CoworkVMService before clicking "Relaunch" and restart it after the update completes, as the service holds file locks on the MSIX package directory.

Guidance

  • Identify the CoworkVMService and its startup type to understand why it interferes with the update process.
  • Use the provided PowerShell commands to stop and disable the CoworkVMService before updating, and re-enable it after the update.
  • Ensure you run the PowerShell commands with admin privileges to successfully disable and re-enable the service.
  • Verify that the update completes successfully after stopping and disabling the CoworkVMService.

Example

Stop-Service CoworkVMService -Force
Set-Service CoworkVMService -StartupType Disabled
# Click Relaunch now
# After update, re-enable:
Set-Service CoworkVMService -StartupType Automatic
Start-Service CoworkVMService

Notes

This workaround requires admin privileges and manual intervention. A permanent fix would involve modifying the updater to handle the CoworkVMService properly.

Recommendation

Apply the provided workaround to stop and disable the CoworkVMService before updating, as it is a reliable and tested solution to the issue.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING