Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork VM timeout on Windows 11 Home Build 26200 — all prerequisites met [3 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#47971•Fetched 2026-04-15 06:37:06
View on GitHub
Comments
3
Participants
2
Timeline
7
Reactions
0
Author
michaelmikrut2michaelmikrut2
Participants
github-actions[bot]github-actions[bot]michaelmikrut2michaelmikrut2
Timeline (top)
labeled ×4commented ×3

Error Message

Error received:

Error Messages/Logs

Code Example

"Failed to start Claude's workspace
VM is already running
Restarting Claude or your computer sometimes resolves this. If it persists, you can reinstall the workspace."

"Failed to start Claude's workspace — VM connection timeout after 60 seconds"
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

System Info:

  • Windows 11 Home, Build 26200.8037
  • Claude Desktop: latest version
  • Active subscription (paying customer)

Error received: "Failed to start Claude's workspace — VM connection timeout after 60 seconds"

Also occasionally seeing: "VM is already running"

What I have already tried:

  • Clean uninstall and reinstall of Claude
  • Cleared all app data (%APPDATA%\Claude and %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc)
  • Manually stopping and restarting CoworkVMService via PowerShell
  • Running Claude as Administrator
  • WSL2 confirmed installed and up to date (version 2.6.3.0)
  • All Windows features enabled: Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, Windows Subsystem for Linux
  • All storage locations set to C: drive
  • Attempted to enable Windows Containers feature — not available on Home edition

System checks:

  • HypervisorPlatform: Enabled
  • Microsoft-Hyper-V-All: Enabled
  • Microsoft-Hyper-V: Enabled
  • Microsoft-Hyper-V-Tools-All: Enabled
  • Microsoft-Hyper-V-Management-PowerShell: Enabled
  • Microsoft-Hyper-V-Hypervisor: Enabled
  • Microsoft-Hyper-V-Services: Enabled
  • Microsoft-Hyper-V-Management-Clients: Enabled

Cowork has never worked on this machine since purchase. I purchased Claude specifically for the Cowork feature.

Related issues: #25136, #27652, #31516, #38112

What Should Happen?

Co Work Should be working properly

Error Messages/Logs

"Failed to start Claude's workspace
VM is already running
Restarting Claude or your computer sometimes resolves this. If it persists, you can reinstall the workspace."

"Failed to start Claude's workspace — VM connection timeout after 60 seconds"

Steps to Reproduce

  1. You are on Windows 11 Home Build 26200
  2. You go to CoWork with any request
  3. Did all the prerequisites above in what's wrong section and its still happening

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

claude-sonnet-4-6

Claude Code Version

Claude Sonnet 4.6

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

<img width="1223" height="561" alt="Image" src="https://github.com/user-attachments/assets/bc5540c2-9b15-4d7a-911c-2a1669e37a54" />

extent analysis

TL;DR

The issue can be potentially resolved by investigating and resolving the "VM connection timeout" and "VM is already running" errors, possibly related to the CoworkVMService or Hyper-V configuration.

Guidance

  • Investigate the status and configuration of the CoworkVMService to ensure it's properly running and not causing conflicts.
  • Check the Hyper-V settings and virtual machine configurations to see if there are any issues or misconfigurations that could be causing the timeout or "already running" errors.
  • Consider checking the system event logs for any errors related to Hyper-V, virtual machines, or the CoworkVMService that might provide more insight into the issue.
  • Since the issue persists after a clean reinstall and clearing app data, it might be worth exploring if there are any system-level or configuration issues that are not being addressed by these steps.

Notes

The provided information suggests that the issue is specific to the Windows 11 Home edition and the Claude Sonnet 4.6 version, and it's unclear if this is a regression or a new issue. The fact that Cowork has never worked on this machine since purchase indicates a potential underlying configuration or compatibility problem.

Recommendation

Apply workaround: Given the complexity of the issue and the lack of a clear solution, it might be best to try and apply workarounds or configuration changes to resolve the "VM connection timeout" and "VM is already running" errors, rather than immediately seeking an upgrade, as the latest version is already in use.

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…
#api#index setup#retrieval issue#search optimization#API routing

Still need to ship something?

×6

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

Back to top recommendations

TRENDING