Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork VM connection timeout on Windows 11 Home ARM64 (Claude 1.2278.0.0) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47851•Fetched 2026-04-15 06:40:32
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
Broch140275Broch140275
Participants
Broch140275Broch140275github-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4closed ×1commented ×1unlabeled ×1

Error Message

Error Messages/Logs

Root Cause

Root cause (from logs): The new smol-bin included in 1.2278.0.0 contains an updated daemon binary (ed411765). When the VM boots, the old daemon (bf2c13d3) detects the update, applies it, and then the new daemon (ed411765) crashes immediately — producing zero console output and never establishing its vsock connection to the host.

Code Example

Bug Report: Cowork VM connection timeout on Windows 11 Home ARM64 (Claude 1.2278.0.0)

Device:

Lenovo 83HL, Snapdragon X / Qualcomm Oryon CPU (ARM64)
Windows 11 Home, Build 26200
Claude Desktop 1.2278.0.0
Problem:
Cowork workspace fails to start with "VM connection timeout after 60 seconds" after updating to Claude 1.2278.0.0.

Root cause (from logs):
The new smol-bin included in 1.2278.0.0 contains an updated daemon binary (ed411765). When the VM boots, the old daemon (bf2c13d3) detects the update, applies it, and then the new daemon (ed411765) crashes immediately — producing zero console output and never establishing its vsock connection to the host.

This results in a permanent 60-second timeout on every Cowork startup attempt.

Regression:
Cowork worked correctly in Claude 1.1.4498.0 (confirmed in logs from March 2026). The issue is specific to the new daemon binary shipped with 1.2278.0.0 on ARM64.

Relevant log files:

C:\ProgramData\Claude\Logs\cowork-service.log
C:\ProgramData\Claude\Logs\coworkd\user-S-1-5-21-3492074509-397282041-255339966-1001.log
C:\Users\jens\AppData\Roaming\Claude\logs\cowork_vm_node.log
Indsend via claude.ai/claude-code → Issues → eller direkte på GitHub: anthropics/claude-code

/debug



Debug-logging er nu aktiv. Log-filen er her:

C:\Users\jens\.claude\debug\30fb62ae-5a32-4304-ab59-f0a6e45fda5b.txt

Ingen log endnu — den oprettes når du reproducerer problemet.

Hvad vil du debug? Er det stadig Cowork VM-fejlen, eller er der noget med selve Claude Code-sessionen?

/Feedback


Unknown skill: Feedback


/feedback
Bug Report: Cowork VM connection timeout on Windows 11 Home ARM64 (Claude 1.2278.0.0)

Device:

Lenovo 83HL, Snapdragon X / Qualcomm Oryon CPU (ARM64)
Windows 11 Home, Build 26200
Claude Desktop 1.2278.0.0
Problem:
Cowork workspace fails to start with "VM connection timeout after 60 seconds" after updating to Claude 1.2278.0.0.

Root cause (from logs):
The new smol-bin included in 1.2278.0.0 contains an updated daemon binary (ed411765). When the VM boots, the old daemon (bf2c13d3) detects the update, applies it, and then the new daemon (ed411765) crashes immediately — producing zero console output and never establishing its vsock connection to the host.

This results in a permanent 60-second timeout on every Cowork startup attempt.

Regression:
Cowork worked correctly in Claude 1.1.4498.0 (confirmed in logs from March 2026). The issue is specific to the new daemon binary shipped with 1.2278.0.0 on ARM64.

Show more

Unknown skill: feedback
RAW_BUFFERClick to expand / collapse

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?

Cowork workspace fails to start with "VM connection timeout after 60 seconds" after updating to Claude 1.2278.0.0.

What Should Happen?

Can't start cowork after update

Error Messages/Logs

Bug Report: Cowork VM connection timeout on Windows 11 Home ARM64 (Claude 1.2278.0.0)

Device:

Lenovo 83HL, Snapdragon X / Qualcomm Oryon CPU (ARM64)
Windows 11 Home, Build 26200
Claude Desktop 1.2278.0.0
Problem:
Cowork workspace fails to start with "VM connection timeout after 60 seconds" after updating to Claude 1.2278.0.0.

Root cause (from logs):
The new smol-bin included in 1.2278.0.0 contains an updated daemon binary (ed411765). When the VM boots, the old daemon (bf2c13d3) detects the update, applies it, and then the new daemon (ed411765) crashes immediately — producing zero console output and never establishing its vsock connection to the host.

This results in a permanent 60-second timeout on every Cowork startup attempt.

Regression:
Cowork worked correctly in Claude 1.1.4498.0 (confirmed in logs from March 2026). The issue is specific to the new daemon binary shipped with 1.2278.0.0 on ARM64.

Relevant log files:

C:\ProgramData\Claude\Logs\cowork-service.log
C:\ProgramData\Claude\Logs\coworkd\user-S-1-5-21-3492074509-397282041-255339966-1001.log
C:\Users\jens\AppData\Roaming\Claude\logs\cowork_vm_node.log
Indsend via claude.ai/claude-code → Issues → eller direkte på GitHub: anthropics/claude-code

/debug



Debug-logging er nu aktiv. Log-filen er her:

C:\Users\jens\.claude\debug\30fb62ae-5a32-4304-ab59-f0a6e45fda5b.txt

Ingen log endnu — den oprettes når du reproducerer problemet.

Hvad vil du debug? Er det stadig Cowork VM-fejlen, eller er der noget med selve Claude Code-sessionen?

/Feedback


Unknown skill: Feedback


/feedback
Bug Report: Cowork VM connection timeout on Windows 11 Home ARM64 (Claude 1.2278.0.0)

Device:

Lenovo 83HL, Snapdragon X / Qualcomm Oryon CPU (ARM64)
Windows 11 Home, Build 26200
Claude Desktop 1.2278.0.0
Problem:
Cowork workspace fails to start with "VM connection timeout after 60 seconds" after updating to Claude 1.2278.0.0.

Root cause (from logs):
The new smol-bin included in 1.2278.0.0 contains an updated daemon binary (ed411765). When the VM boots, the old daemon (bf2c13d3) detects the update, applies it, and then the new daemon (ed411765) crashes immediately — producing zero console output and never establishing its vsock connection to the host.

This results in a permanent 60-second timeout on every Cowork startup attempt.

Regression:
Cowork worked correctly in Claude 1.1.4498.0 (confirmed in logs from March 2026). The issue is specific to the new daemon binary shipped with 1.2278.0.0 on ARM64.

Show more

Unknown skill: feedback

Steps to Reproduce

Bug Report: Cowork VM connection timeout on Windows 11 Home ARM64 (Claude 1.2278.0.0)

Device:

Lenovo 83HL, Snapdragon X / Qualcomm Oryon CPU (ARM64) Windows 11 Home, Build 26200 Claude Desktop 1.2278.0.0 Problem: Cowork workspace fails to start with "VM connection timeout after 60 seconds" after updating to Claude 1.2278.0.0.

Root cause (from logs): The new smol-bin included in 1.2278.0.0 contains an updated daemon binary (ed411765). When the VM boots, the old daemon (bf2c13d3) detects the update, applies it, and then the new daemon (ed411765) crashes immediately — producing zero console output and never establishing its vsock connection to the host.

This results in a permanent 60-second timeout on every Cowork startup attempt.

Regression: Cowork worked correctly in Claude 1.1.4498.0 (confirmed in logs from March 2026). The issue is specific to the new daemon binary shipped with 1.2278.0.0 on ARM64.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

version before Claude Desktop 1.2278.0.0

Claude Code Version

Claude Desktop 1.2278.0.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

extent analysis

TL;DR

The most likely fix is to revert to the previous version of Claude Desktop, specifically version 1.1.4498.0, which is known to work correctly.

Guidance

  • The issue is caused by the new daemon binary (ed411765) crashing immediately after update, resulting in a permanent 60-second timeout on every Cowork startup attempt.
  • To verify the issue, check the log files, specifically cowork-service.log, coworkd\user-S-1-5-21-3492074509-397282041-255339966-1001.log, and cowork_vm_node.log, for any error messages related to the daemon binary.
  • Consider downgrading to the previous version of Claude Desktop, version 1.1.4498.0, which is confirmed to work correctly.
  • If downgrading is not feasible, try to gather more information about the crash by enabling debug logging and checking the debug log file 30fb62ae-5a32-4304-ab59-f0a6e45fda5b.txt for any clues.

Example

No code snippet is provided as the issue is related to a specific version of Claude Desktop and its daemon binary.

Notes

The issue is specific to the new daemon binary shipped with Claude Desktop 1.2278.0.0 on ARM64, and reverting to the previous version may be the most straightforward solution.

Recommendation

Apply workaround: Downgrade to version 1.1.4498.0, as it is confirmed to work correctly and the issue is specific to the new daemon binary in version 1.2278.0.0.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#retriever error#indexing error#inference speed#output truncation

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Cowork VM connection timeout on Windows 11 Home ARM64 (Claude 1.2278.0.0) [1 comments, 2 participants]