claude-code - 💡(How to fix) Fix [BUG] Cowork VM connection timeout on Windows ARM64 Snapdragon — Linux guest never responds after add_plan9_shares [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#46729Fetched 2026-04-12 13:34:34
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1unlabeled ×1

Error Message

2026-04-11 08:20:42 [info] [VM:steps] vm_boot completed (403ms) 2026-04-11 08:20:42 [info] [VM:steps] add_plan9_shares completed (5ms) 2026-04-11 08:20:53 [info] [VM:start] Still waiting for guest connection... 10192ms elapsed, 21 polls 2026-04-11 08:21:03 [info] [VM:start] Still waiting for guest connection... 20362ms elapsed, 41 polls 2026-04-11 08:21:13 [info] [VM:start] Still waiting for guest connection... 30564ms elapsed, 61 polls 2026-04-11 08:21:23 [info] [VM:start] Still waiting for guest connection... 40750ms elapsed, 81 polls 2026-04-11 08:21:33 [info] [VM:start] Still waiting for guest connection... 50960ms elapsed, 101 polls 2026-04-11 08:21:43 [error] [VM:start] Connection timeout, last completed step: add_plan9_shares 2026-04-11 08:21:43 [error] [VM:start] Startup failed: Error: VM connection timeout after 60 seconds

Code Example

2026-04-11 08:20:42 [info] [VM:steps] vm_boot completed (403ms)
2026-04-11 08:20:42 [info] [VM:steps] add_plan9_shares completed (5ms)
2026-04-11 08:20:53 [info] [VM:start] Still waiting for guest connection... 10192ms elapsed, 21 polls
2026-04-11 08:21:03 [info] [VM:start] Still waiting for guest connection... 20362ms elapsed, 41 polls
2026-04-11 08:21:13 [info] [VM:start] Still waiting for guest connection... 30564ms elapsed, 61 polls
2026-04-11 08:21:23 [info] [VM:start] Still waiting for guest connection... 40750ms elapsed, 81 polls
2026-04-11 08:21:33 [info] [VM:start] Still waiting for guest connection... 50960ms elapsed, 101 polls
2026-04-11 08:21:43 [error] [VM:start] Connection timeout, last completed step: add_plan9_shares
2026-04-11 08:21:43 [error] [VM:start] 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?

Cowork fails to start on Windows ARM64 (Snapdragon). The VM boots successfully but the Linux guest OS never establishes a connection. Claude waits 60 seconds then times out. This happens on every attempt with a fresh bundle.

What Should Happen?

The Linux guest should initialize and respond to the host connection after vm_boot, allowing Cowork to start normally.

Error Messages/Logs

2026-04-11 08:20:42 [info] [VM:steps] vm_boot completed (403ms)
2026-04-11 08:20:42 [info] [VM:steps] add_plan9_shares completed (5ms)
2026-04-11 08:20:53 [info] [VM:start] Still waiting for guest connection... 10192ms elapsed, 21 polls
2026-04-11 08:21:03 [info] [VM:start] Still waiting for guest connection... 20362ms elapsed, 41 polls
2026-04-11 08:21:13 [info] [VM:start] Still waiting for guest connection... 30564ms elapsed, 61 polls
2026-04-11 08:21:23 [info] [VM:start] Still waiting for guest connection... 40750ms elapsed, 81 polls
2026-04-11 08:21:33 [info] [VM:start] Still waiting for guest connection... 50960ms elapsed, 101 polls
2026-04-11 08:21:43 [error] [VM:start] Connection timeout, last completed step: add_plan9_shares
2026-04-11 08:21:43 [error] [VM:start] Startup failed: Error: VM connection timeout after 60 seconds

Steps to Reproduce

  1. Install Claude Desktop v1.1617.0.0 (ARM64) on Windows 11 ARM64 (Snapdragon)
  2. Sign in with a paid plan
  3. Click the Cowork tab
  4. Observe: "Failed to start Claude's workspace — VM connection timeout after 60 seconds"

Confirmed environment:

  • VirtualMachinePlatform: Enabled
  • CoworkVMService: Running
  • Claude installed as ARM64 (confirmed via Get-AppxPackage)
  • VM bundle complete (rootfs.vhdx ~9GB present)
  • Microsoft-Hyper-V-All: unavailable on ARM64 (expected)
  • VirtualizationFirmwareEnabled: False (expected on Snapdragon)
  • Fresh bundle re-download does not fix the issue
  • Issue persists across multiple reboots

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

Claude Desktop v1.1617.0.0 ARM64 (This is Claude Desktop Cowork, not Claude Code CLI)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

The VM boots and completes all steps up to add_plan9_shares, but the Linux kernel inside the VM never responds. No coworkd logs are generated inside the VM, suggesting the guest OS never reaches initialization.

Asus Zenbook A14

Related issues: #40198, #30566, #30864

extent analysis

TL;DR

Investigate the compatibility of the Linux guest OS with Windows ARM64 (Snapdragon) and consider updating the VM configuration or the Linux kernel to resolve the connection timeout issue.

Guidance

  • Verify that the Linux guest OS is compatible with the Windows ARM64 (Snapdragon) architecture and check for any known issues or limitations.
  • Check the VM configuration to ensure that it is properly set up to communicate with the host machine, including the network settings and any required ports or protocols.
  • Consider updating the Linux kernel or the VM configuration to a version that is known to work with Windows ARM64 (Snapdragon), if available.
  • Review the related issues (#40198, #30566, #30864) to see if they provide any insight or solutions to the problem.

Notes

The issue seems to be related to the compatibility of the Linux guest OS with the Windows ARM64 (Snapdragon) architecture, and resolving this may require updates to the VM configuration or the Linux kernel.

Recommendation

Apply a workaround by investigating alternative VM configurations or Linux kernels that are known to work with Windows ARM64 (Snapdragon), as updating to a fixed version is not explicitly mentioned in the issue.

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