claude-code - 💡(How to fix) Fix [BUG] Cowork VM connection timeout — Windows 11 Home ARM64 [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#47737Fetched 2026-04-15 06:43:40
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
1
Timeline (top)
labeled ×4commented ×1cross-referenced ×1subscribed ×1

Error Message

[VM:steps] vm_boot completed (136ms) [VM:steps] add_plan9_shares completed (15ms) [VM:start] Still waiting for guest connection... 10261ms elapsed [VM:start] Still waiting for guest connection... 51185ms elapsed [VM:error] Connection timeout, last completed step: add_plan9_shares [VM:error] Startup failed: Error: VM connection timeout after 60 seconds

Code Example

[VM:steps] vm_boot completed (136ms)
[VM:steps] add_plan9_shares completed (15ms)
[VM:start] Still waiting for guest connection... 10261ms elapsed
[VM:start] Still waiting for guest connection... 51185ms elapsed
[VM:error] Connection timeout, last completed step: add_plan9_shares
[VM:error] Startup failed: Error: 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?

Description: Cowork fails to start with "VM connection timeout after 60 seconds" on every attempt. All standard troubleshooting has been completed without resolution. System info:

Windows 11 Home, ARM64 Claude Desktop v1.2278.0.0 (arm64)

Troubleshooting already completed:

Restarted app and computer multiple times Reinstalled workspace via in-app option Installed WSL2 (Default Version: 2, Ubuntu) Manually restarted CoworkVMService via PowerShell Ran wsl --shutdown to clear stuck VM

Log findings (cowork_vm_node.log): VM boots successfully (vm_boot completed in 136ms, add_plan9_shares completed), but guest agent never responds. Host times out after 60 seconds waiting for guest connection: [VM:steps] vm_boot completed (136ms) [VM:steps] add_plan9_shares completed (15ms) [VM:start] Still waiting for guest connection... 10261ms elapsed [VM:start] Still waiting for guest connection... 51185ms elapsed [VM:error] Connection timeout, last completed step: add_plan9_shares [VM:error] Startup failed: Error: VM connection timeout after 60 seconds This appears to be the known ARM64 + Windows Home compatibility issue referenced in GitHub issues #42784, #44007, and #46516. Please advise on a fix or timeline for ARM64 support.

What Should Happen?

Cowork workspace should start successfully and connect to the VM guest agent, allowing task execution in the desktop environment.

Error Messages/Logs

[VM:steps] vm_boot completed (136ms)
[VM:steps] add_plan9_shares completed (15ms)
[VM:start] Still waiting for guest connection... 10261ms elapsed
[VM:start] Still waiting for guest connection... 51185ms elapsed
[VM:error] Connection timeout, last completed step: add_plan9_shares
[VM:error] Startup failed: Error: VM connection timeout after 60 seconds

Steps to Reproduce

  1. Open Claude Desktop on Windows 11 Home ARM64
  2. Click on the Cowork tab
  3. Observe error: "Failed to start Claude's workspace — VM connection timeout after 60 seconds"
  4. Error persists regardless of how many times the workspace is reopened

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

1.2278.0.0

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

This is a Claude Desktop Cowork issue, not Claude Code CLI.

Device: Windows 11 Home ARM64 Troubleshooting completed:

  • Restarted app and computer multiple times
  • Reinstalled workspace via in-app option
  • Installed WSL2 (Default Version: 2, Ubuntu)
  • Manually restarted CoworkVMService via PowerShell
  • Ran wsl --shutdown to clear stuck VM

VM boots successfully but guest agent never responds. Related issues: #42784, #44007, #46516.

extent analysis

TL;DR

The issue is likely due to a known compatibility problem with ARM64 and Windows Home, and a fix or workaround may involve waiting for an update or using a different environment.

Guidance

  • The error messages indicate a connection timeout after 60 seconds, suggesting an issue with the guest agent responding.
  • The fact that the VM boots successfully but the guest agent never responds implies a potential problem with the communication between the host and guest.
  • Checking the related issues (#42784, #44007, #46516) may provide more information on the known compatibility issue and potential workarounds.
  • Consider using a different environment, such as a non-ARM64 Windows version or a different operating system, to see if the issue persists.

Notes

The issue appears to be a known problem, and the user has already completed standard troubleshooting steps without resolution. The fact that the VM boots successfully but the guest agent never responds suggests a complex issue that may require a fix from the developers.

Recommendation

Apply workaround: Wait for an update or use a different environment, as the issue is likely due to a known compatibility problem with ARM64 and Windows Home.

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 VM connection timeout — Windows 11 Home ARM64 [1 comments, 2 participants]