CoworkVMService stopped with no in-app recovery (Windows, Claude 1.2581.0.0)

Resolved 💬 3 comments Opened Apr 15, 2026 by figgsoftware Closed Jun 21, 2026

Environment

  • OS: Windows 11 Pro 10.0.26200
  • Claude app: 1.2581.0.0 (x64, WindowsApps package Claude_1.2581.0.0_x64__pzs8sxrjxfjjc)
  • Service binary: cowork-svc.exe

Symptom
Cowork could not start its workspace VM. No actionable error in-app, and
Cowork's own recovery did not resolve it.

Diagnosis

  • Windows service CoworkVMService (display name "Claude") was STOPPED.
  • Start type AUTO_START, account LocalSystem, dependency staterepository running.
  • Exit codes WIN32_EXIT_CODE 0 / SERVICE_EXIT_CODE 0 — clean stop, not a crash.
  • Service binary present and intact.
  • No SCM failure/recovery actions configured on the service.

Workaround
net start CoworkVMService — started on first try.

Expected

  1. Cowork should detect the stopped service and restart it, or surface a

clear actionable error ("Claude background service is not running — restart").

  1. Service should have recovery actions configured (e.g. sc failure ... restart/5000/...)

so Windows auto-restarts it.

Repro
Unclear — the clean exit suggests something issued a stop (possibly an
update/uninstall leftover or prior manual stop) rather than a crash.

View original on GitHub ↗

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