[Bug] Cowork returns exit code 127 with "CoworkVM service not running" after update

Resolved 💬 4 comments Opened Apr 16, 2026 by igarreta Closed Jun 12, 2026

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 rsi@igarreta.com.ar

Environment Info

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

Errors

[]

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗