claude-code - 💡(How to fix) Fix [Bug] Cowork returns exit code 127 with "CoworkVM service not running" after update [1 comments, 1 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#49474Fetched 2026-04-17 08:40:09
View on GitHub
Comments
1
Participants
1
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×4commented ×1

Error Message

Subject: Cowork error 127 / VM service not running after update

  • Error message: "CoworkVM service not running. The service failed to start."
  • Tested with both OneDrive and local workspace folder — same error

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description Subject: Cowork error 127 / VM service not running after update

Hi,

I'm experiencing an issue with Claude Cowork that started after a recent update.

Symptoms:

  • Every Cowork prompt returns exit code 127
  • Error message: "CoworkVM service not running. The service failed to start."
  • Chat works normally

Environment:

  • Windows, MSIX installer
  • Claude Desktop: latest (reinstalled after issue appeared)
  • Claude Code: 2.1.111

Troubleshooting already performed:

  • Verified claude.exe is in PATH (C:\Users\RamonSantiagoIgarret.local\bin\claude.exe)
  • claude --version works correctly from both normal and admin terminal
  • CoworkVMService shows STATE: RUNNING, exit code 0
  • Full system restart
  • Reinstalled Claude Desktop
  • Tested with both OneDrive and local workspace folder — same error

The issue started after an automatic update. Prior to the update, Cowork was working normally.

Please advise.

Ramón Igarreta [email protected]

Environment Info

  • Platform: win32
  • Terminal: null
  • Version: 2.1.111
  • Feedback ID: 2ca4a81d-0374-4f68-9e7a-0aa80560fac8

Errors

[]

extent analysis

TL;DR

The issue with Cowork returning exit code 127 and the "CoworkVM service not running" error after an update may be resolved by investigating the service startup process and ensuring it's properly configured.

Guidance

  • Verify the CoworkVM service startup configuration to ensure it's set to start automatically after a system restart.
  • Check the system event logs for any errors related to the CoworkVM service startup process.
  • Consider manually starting the CoworkVM service to see if it resolves the issue temporarily.
  • Review the update changelog to see if there were any changes to the service startup process or dependencies.

Notes

The issue seems to be related to the CoworkVM service not starting properly after an update. However, the provided information does not give a clear indication of the root cause. Further investigation into the service startup process and system event logs may be necessary to resolve the issue.

Recommendation

Apply workaround: Manually start the CoworkVM service and monitor its behavior to see if it resolves the issue temporarily, while further investigating the root cause of the service not starting automatically after the update.

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

claude-code - 💡(How to fix) Fix [Bug] Cowork returns exit code 127 with "CoworkVM service not running" after update [1 comments, 1 participants]