[BUG] Cowork VM boots successfully on Windows side but Linux guest hangs silently after first session - Snapdragon X ARM64

Resolved 💬 3 comments Opened Apr 11, 2026 by Matt73D Closed Apr 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?

Cowork connected and worked successfully once. Every subsequent attempt has the VM container starting successfully on the Windows side (HCS returns success, console pipe connects) but the Linux guest produces no output and coworkd log does not update. Results in 60 second timeout.

What Should Happen?

Cowork should launch.

Error Messages/Logs

Hyper-V guest OS boot hangs silently on Snapdragon X after first session, possibly related to rootfs state or Hyper-V virtualization compatibility on this platform.

Steps to Reproduce

Launch cowork

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.1617.0.0 arm64

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Title: Cowork VM boots successfully on Windows side but Linux guest hangs silently after first session - Snapdragon X ARM64
Environment:

Device: Snapdragon X X126100 (Qualcomm Oryon CPU)
OS: Windows 11 Pro ARM64
Claude version: 1.1617.0.0 arm64

Behavior:
Cowork connected and worked successfully once. Every subsequent attempt has the VM container starting successfully on the Windows side (HCS returns success, console pipe connects) but the Linux guest produces no output and coworkd log does not update. Results in 60 second timeout.
Confirmed working:

HNS network cowork-vm-nat created, forwarding enabled
CoworkVMService starts and runs
HcsCreateComputeSystem and HcsStartComputeSystem both return hr=0x0
Console pipe connects successfully
vmlinuz is valid ARM64 kernel (magic bytes 4D 5A 40 FA)
rootfs.vhdx is intact (9.1 GB, decompressed from 2.2 GB zst)
coworkd log shows successful connection on April 10 but nothing from April 11 attempts

Suspected cause: Hyper-V guest OS boot hangs silently on Snapdragon X after first session, possibly related to rootfs state or Hyper-V virtualization compatibility on this platform.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗