Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork VM connection timeout on Windows 11 Home — worked previously, broke after update to v1.1617.0.0 [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#46487•Fetched 2026-04-11 06:19:00
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
CleanColorsCleanColors
Participants
CleanColorsCleanColorsgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1

Error Message

Error message 2026-04-10 19:04:25 [error] [VM:start] Connection timeout, last completed step: add_plan9_shares 2026-04-10 19:04:25 [info] Dispatching startup error: VM connection timeout after 60 seconds

Error Messages/Logs

Fix Action

Fix / Workaround

2026-04-10 19:03:35 [info] [VM:start] Still waiting for guest connection... 10280ms elapsed 2026-04-10 19:04:25 [error] [VM:start] Connection timeout, last completed step: add_plan9_shares 2026-04-10 19:04:25 [info] Dispatching startup error: VM connection timeout after 60 seconds 2026-04-10 19:04:25 [info] [VM:start] Skipping auto-reinstall (already attempted once)

Code Example

VM Connection timeout on windows personal.
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?

Environment

  • OS: Windows 11 Home
  • Claude Desktop version: 1.1617.0.0
  • Installed via: Microsoft Store (MSIX)

Description Cowork was working correctly on this machine (Windows 11 Home) and stopped working approximately 2 days ago, coinciding with an auto-update to v1.1617.0.0. No other changes were made to the system.

The VM boots partially but never establishes a guest connection. Claude in Chrome also crashes on complex tasks.

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

Log evidence Last completed step before timeout: add_plan9_shares

2026-04-10 19:03:35 [info] [VM:start] Still waiting for guest connection... 10280ms elapsed 2026-04-10 19:04:25 [error] [VM:start] Connection timeout, last completed step: add_plan9_shares 2026-04-10 19:04:25 [info] Dispatching startup error: VM connection timeout after 60 seconds 2026-04-10 19:04:25 [info] [VM:start] Skipping auto-reinstall (already attempted once)

Steps to reproduce

  1. Run Claude Desktop v1.1617.0.0 on Windows 11 Home
  2. Open Cowork tab
  3. Result: VM times out after 60 seconds at add_plan9_shares step

What I tried

  • Multiple app restarts
  • Multiple full system restarts
  • In-app workspace reinstall
  • Full uninstall and reinstall of Claude Desktop

Nothing resolves the issue.

Expected behavior Cowork starts successfully, as it did before the update.

Additional context

  • vmcompute service: Running
  • vmms service: Not found (not available on Windows Home)
  • Hyper-V: Not available on Windows Home edition
  • Related issues: #42784, #44007

What Should Happen?

Claude shouldn't crash.

Error Messages/Logs

VM Connection timeout on windows personal.

Steps to Reproduce

  1. Open Cowork (which was always working)
  2. Write a task.
  3. VM connection timed out.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

anything before 1.1617.0.0

Claude Code Version

1.1617.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

No response

extent analysis

TL;DR

The most likely fix is to revert to a previous version of Claude Desktop, as the issue is reported to be a regression introduced in version 1.1617.0.0.

Guidance

  • Verify that the issue is indeed a regression by checking the version history and confirming that the problem did not exist in previous versions.
  • Attempt to reinstall a previous version of Claude Desktop that was known to be working, to confirm whether the issue is specific to version 1.1617.0.0.
  • Check the system's event logs for any errors or warnings related to the vmcompute service, as it is running and may be related to the timeout issue.
  • Consider reporting this issue to the developers, as it may be a bug that needs to be fixed in a future update.

Notes

The fact that the issue occurred after an auto-update and that the vmms service is not available on Windows Home edition may be relevant to the root cause of the problem. However, without further information or debugging, it is difficult to determine the exact cause.

Recommendation

Apply workaround: Revert to a previous version of Claude Desktop, as the issue is reported to be a regression introduced in version 1.1617.0.0. This is because the issue is confirmed to have worked in previous versions, and reverting to a previous version may provide a temporary solution until the issue is fixed in a future 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…
#api#tensor shape#autograd error#model save/load#optimization

Still need to ship something?

×6

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

Back to top recommendations

TRENDING