[BUG] claude desktop can't communicate with VM

Resolved 💬 3 comments Opened Mar 18, 2026 by methink-cpu Closed Mar 21, 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?

Claude cowork keep saying timed out every command. can't use anymore.
.................
coworkd.log (ฝั่ง VM) → ทุกอย่างสำเร็จหมด: boot ได้, เชื่อมต่อ API ได้, reachability check passed, "connected, waiting for commands" ✅
cowork_vm_node.log (ฝั่ง Windows/Host) → Keep-alive ping timed out ตลอด ❌
แสดงว่า VM ทำงานได้ปกติ แต่ Claude Desktop app บน Windows สื่อสารกลับไปหา VM ไม่ได้ ผ่าน vsock (port 51234) ปัญหานี้เป็น bug ที่รู้กันในหมู่ผู้ใช้ Windows 10 กับ Cowork

What Should Happen?

run as usual

Error Messages/Logs

ontent
4.74 KB •66 lines
•
Formatting may be inconsistent from source
PS C:\WINDOWS\system32> Get-Content "$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\cowork_vm_node.log" -Tail 30
    at Socket.emit (node:events:508:28)
    at Socket._onTimeout (node:net:604:8)
    at listOnTimeout (node:internal/timers:605:17)
    at process.processTimers (node:internal/timers:541:7) {
  [stack]: [Getter/Setter],
  [message]: 'Request timed out'
}
2026-03-17 13:37:28 [warn] [Keepalive] Ping failed: Request timed out
2026-03-17 13:37:30 [warn] [Keepalive] Ping failed: Request timed out
2026-03-17 13:37:31 [info] [Process:2d5dca65-c8c5-4d0f-9611-fc14e7b342c3] Exited, code=0, signal=null, duration=86770ms, oom=false
2026-03-17 13:37:31 [info] [Process:2d5dca65-c8c5-4d0f-9611-fc14e7b342c3] Cleaned up, remaining active=0
2026-03-17 13:37:37 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:39 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:40 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:41 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:43 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:44 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:46 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:48 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:48 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:52 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:54 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:56 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:57 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:37:59 [warn] [Keepalive] Ping failed: Request timed out
2026-03-17 13:38:03 [warn] [Keepalive] Ping failed: Request timed out
2026-03-17 13:38:05 [warn] [Keepalive] Ping failed: Request timed out
2026-03-17 13:38:06 [warn] [Keepalive] Ping failed: Keep-alive ping timed out
2026-03-17 13:38:08 [warn] [Keepalive] Ping failed: Request timed out
2026-03-17 13:38:10 [warn] [Keepalive] Ping failed: Request timed out
2026-03-17 13:38:12 [warn] [Keepalive] Ping failed: Request timed out
2026-03-17 13:38:13 [warn] [Keepalive] Ping failed: Request timed out
2026-03-17 13:38:15 [warn] [Keepalive] Ping failed: Request timed out
PS C:\WINDOWS\system32> Get-Content "$env:LOCALAPPDATA\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\coworkd.log" -Tail 30
2026/03/17 06:25:04 [hyperv] mounting Plan9 share via vsock port 9999
2026/03/17 06:25:04 [hyperv] mounting with options: trans=fd,rfdno=6,wfdno=6,msize=1048576,noload,aname=home
2026/03/17 06:25:04 [hyperv] Plan9 share mounted at /mnt/.virtiofs-root/shared
2026/03/17 06:25:04 [hyperv] found session disk at /dev/sdc
2026/03/17 06:25:04 [coworkd] configuring static IP on tap0: 172.16.10.3/24 gateway=172.16.10.1 dns=172.16.10.1
2026/03/17 06:25:04 [coworkd] session disk already formatted as ext4
2026/03/17 06:25:04 [coworkd] running e2fsck on /dev/sdc
2026/03/17 06:25:04 [coworkd] e2fsck clean on /dev/sdc
2026/03/17 06:25:04 [coworkd] mounting session disk /dev/sdc at /sessions
2026/03/17 06:25:05 [coworkd] session disk mounted successfully at /sessions
2026/03/17 06:25:05 [coworkd] user recovery complete: recovered=0 skipped=1 failed=0
2026/03/17 06:25:05 [proxy] generating ephemeral CA certificate (private key in memory only)
2026/03/17 06:25:05 [proxy] ephemeral CA generated (expires: 2027-03-17T06:25:05Z)
2026/03/17 06:25:06 [coworkd] MTU on tap0 is 1400, already at or below target 1400
2026/03/17 06:25:06 [coworkd] static IP configured successfully
2026/03/17 06:25:06 [tapvsock] TAP device configured (tap=tap0, ip=172.16.10.3/24, gw=172.16.10.1)
2026/03/17 06:25:06 [tapvsock] connecting to host network via vsock port 1024
2026/03/17 06:25:06 [tapvsock] connected to host network, bridge running
2026/03/17 06:25:11 [proxy] CA certificate installed to system trust store
2026/03/17 06:25:11 [proxy] MITM proxy started on /var/run/mitm-proxy.sock
2026/03/17 06:25:11 [rpc] connecting to host CID=2 port=51234
2026/03/17 06:25:11 [rpc] connected successfully
2026/03/17 06:25:11 [coworkd] waiting for IPv4 route
2026/03/17 06:25:11 [coworkd] IPv4 route is available
2026/03/17 06:25:11 [rpc] ready event sent
2026/03/17 06:25:11 [coworkd] checking reachability https://api.anthropic.com/ (timeout=30s)
2026/03/17 06:25:12 [coworkd] reachability check passed (status=404)
2026/03/17 06:25:12 [coworkd] connected, waiting for commands
2026/03/17 06:25:16 [coworkd] installed 44 host CA certificates
2026/03/17 06:25:17 [coworkd] SDK binary v2.1.76 already installed, skipping
PS C:\WINDOWS\system32>

Steps to Reproduce

no idea

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude 1.1.7053 (cc1949) 2026-03-16T22:55:50.000Z

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

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