[BUG] Failed to start Claude's workspace VM connection timeout after 60 seconds

[Andy9786]

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?

I am getting this error in Claude Cowork ( I am using a Windows 11 Snapgragon ARM64 Asus Vivo laptop )-

"Failed to start Claude's workspace
VM connection timeout after 60 seconds"

I have checked the logs in the cowork_vm_node.log file in the Packages folder and can see the below -

2026-04-14 23:06:31 [info] [VM:start] Still waiting for guest connection... 10259ms elapsed, 21 polls
2026-04-14 23:06:41 [info] [VM:start] Still waiting for guest connection... 20531ms elapsed, 41 polls
2026-04-14 23:06:51 [info] [VM:start] Still waiting for guest connection... 30799ms elapsed, 61 polls
2026-04-14 23:07:02 [info] [VM:start] Still waiting for guest connection... 41066ms elapsed, 81 polls
2026-04-14 23:07:12 [info] [VM:start] Still waiting for guest connection... 51321ms elapsed, 101 polls
2026-04-14 23:07:21 [error] [VM:start] Connection timeout, last completed step: add_plan9_shares
2026-04-14 23:07:21 [info] Dispatching startup error: VM connection timeout after 60 seconds
2026-04-14 23:07:21 [error] [VM:start] Startup failed: Error: VM connection timeout after 60 seconds

I have uninstalled Claude a couple of times and reinstalled plus tried to reinstall the workspace but nothing has changed this error message.

Please can you advise on a solution,

Thanks

Andy.

What Should Happen?

I should not be getting the eror message

Error Messages/Logs

In Cowork -
"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 in the cowork_vm_node.log file in the Packages folder -

2026-04-14 23:06:31 [info] [VM:start] Still waiting for guest connection... 10259ms elapsed, 21 polls
2026-04-14 23:06:41 [info] [VM:start] Still waiting for guest connection... 20531ms elapsed, 41 polls
2026-04-14 23:06:51 [info] [VM:start] Still waiting for guest connection... 30799ms elapsed, 61 polls
2026-04-14 23:07:02 [info] [VM:start] Still waiting for guest connection... 41066ms elapsed, 81 polls
2026-04-14 23:07:12 [info] [VM:start] Still waiting for guest connection... 51321ms elapsed, 101 polls
2026-04-14 23:07:21 [error] [VM:start] Connection timeout, last completed step: add_plan9_shares
2026-04-14 23:07:21 [info] Dispatching startup error: VM connection timeout after 60 seconds
2026-04-14 23:07:21 [error] [VM:start] Startup failed: Error: VM connection timeout after 60 seconds

Steps to Reproduce

I get the error message in Cowork on my laptop after 60 seconds automatically without doing anything.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

Claude 1.2581.0 (f10398) 2026-04-14T17:16:40.000Z

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

[github-actions]

Found 3 possible duplicate issues:

1. Cowork: VM connection timeout on Windows ARM64 (Snapdragon X Plus) #45480
2. [BUG] Cowork VM connection timeout on Windows ARM64 Snapdragon — Linux guest never responds after add_plan9_shares #46729
3. [BUG] Cowork VM connection timeout — Windows 11 Home ARM64 #47737

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #45480.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.