[BUG] Cowork VM timeout after 60s on Windows 11 Pro ARM64 - stuck at add_plan9_shares

Resolved 💬 1 comment Opened Jun 8, 2026 by JossAubry Closed Jul 15, 2026

Preflight Checklist

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

What's Wrong?

When I use Claude Cowork, I have a VM timeout. I've done multiple action, upgraded to Win11 Pro, reinstalled the Desktop version, but still the issue.

OS: Windows 11 Pro, ARM64
Claude Desktop version: 1.11187.4.0
Hyper-V: fully enabled (all components)
Issue: VM starts and completes all steps (create_network, create_vm_config, vm_boot, add_plan9_shares) but times out after 60 seconds waiting for guest connection
Tested: full reinstall of Claude Desktop, VM bundle deletion, manual creation of Hyper-V switch and NAT rule, upgrade from Windows 11 Home to Pro

Log extract:
[VM:steps] add_plan9_shares completed (6ms)
[VM:start] Still waiting for guest connection... 10177ms elapsed
[VM:start] Still waiting for guest connection... 50860ms elapsed
[VM:start] Connection timeout, last completed step: add_plan9_shares
[VM:start] Startup failed: Error: VM connection timeout after 60 seconds

What Should Happen?

Claude cowork should be running the script, without any error; allow routines that have been configured.

Error Messages/Logs

Steps to Reproduce

Perform any prompt

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.11187.4.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗