[BUG] can't run cowork in Snapdragon X

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?

Device: ASUS Zenbook A14 UX3407QA, Snapdragon(R) X - X126100 - Qualcomm(R) Oryon(TM) CPU (2.96 GHz)
Readiness Check: SUPPORTED
Error: VM connection timeout after 60 seconds
Tried: reinstall workspace, reboot — no effect

What Should Happen?

After the Cowork workspace VM starts, the Linux guest kernel should successfully boot and establish an HVSock connection to the host, allowing Cowork to initialize within the 60-second timeout window.
The Cowork Readiness Check confirms this device meets all requirements (Windows 10.0 build 26200, arm64, Virtual Machine Platform services present, 820 GB disk space, 31.6 GB RAM) and returns "Result: SUPPORTED". Therefore, Cowork should launch and function normally on this device.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce

Install Claude Desktop (latest version) on ASUS Zenbook A14 UX3407QA running Windows 11 arm64 (Build 26200) with Snapdragon X processor
Run the official Cowork Readiness Check tool — result shows "SUPPORTED" with all items passing
Open Claude Desktop and navigate to Cowork
Wait for workspace to initialize
Observe: error message appears — "Failed to start Claude's workspace / VM connection timeout after 60 seconds"

Additional steps already attempted (issue persists after all of the following):

Clicked "Reinstall the workspace" within Claude Desktop
Fully uninstalled and reinstalled Claude Desktop
Rebooted the computer multiple times

Result: Cowork is completely unusable on this device. The timeout error appears every single attempt with 100% reproduction rate.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Version 1.1617.0 (8d6345)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_