[BUG] Cowork falha ao iniciar workspace no Windows ARM64 — "VM connection timeout after 60 seconds

Open 💬 0 comments Opened Jun 17, 2026 by danilomoreira094-max

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 fails to start the workspace on Windows 11 ARM64 (Snapdragon), showing the error:

"Failed to start Claude's workspace — VM connection timeout after 60 seconds. Restarting Claude or your computer sometimes resolves this. If it persists, you can reinstall the workspace."

What Should Happen?

The Cowork workspace should start and connect normally, as it does on x86/x64 hardware.

Error Messages/Logs

Error message shown:
"Failed to start Claude's workspace — VM connection timeout after 60 seconds. Restarting Claude or your computer sometimes resolves this. If it persists, you can reinstall the workspace."

Logs: No log files were found in %APPDATA%\Claude\logs or %LOCALAPPDATA%\Claude\logs after the failure (recursive search for "*.log" returned no results), suggesting the failure occurs before logging starts in this version, or the log path differs from what's documented in similar bug reports.

Steps to Reproduce

  1. Open Claude Desktop on Windows 11 ARM64
  2. Go to the Cowork tab
  3. Start (or attempt to start) any Cowork task
  4. Wait for the VM connection attempt
  5. After approximately 60 seconds, the timeout error is shown

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

N/A — not using Claude Code CLI, this bug is in Cowork (Claude Desktop) version 1.13576.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

This bug is in Cowork (Claude Desktop), not the Claude Code CLI — the "Claude Code Version" and "Terminal/Shell" fields above don't perfectly apply to this scenario.

Claude Desktop version: 1.13576.0.0

Troubleshooting steps already taken (without success):

  1. Full reinstall of Claude Desktop
  2. Restarted the computer multiple times
  3. Reinstalled the workspace via the in-app option
  4. Confirmed VirtualMachinePlatform is Enabled (via DISM)
  5. HypervisorPlatform was Disabled, manually enabled via DISM /Online /Enable-Feature /FeatureName:HypervisorPlatform /All + restart — error persisted
  6. Confirmed Microsoft-Hyper-V-All is not available as a feature on this architecture/edition
  7. Confirmed WSL2 is installed and updated (wsl --status, wsl --update)
  8. No log files found in %APPDATA%\Claude or %LOCALAPPDATA%\Claude after the failure

Related reports (same ARM64 architecture):

  • #54011 (Cowork sandbox unusable on Windows ARM64 — guest VM never reaches userspace)
  • #48370 (same error message, log shows failure at add_plan9_shares)
  • #42784 (timeout persists after full reinstall)

Question: Is Cowork on Windows ARM64 (Snapdragon) officially supported at this time?

View original on GitHub ↗