[BUG] VM connection timeout after 60 seconds

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?

EBUSY: resource busy or locked, open 'smol-bin.vhdx'
The VM startup failed because the .vhdx disk image was locked by a previous process. This caused the "VM service not running" error repeatedly.

What Should Happen?

the VM boots successfully but takes >60s to be reachable, causing a false failure. The VM was working fine, just slow.

Error Messages/Logs

Error: VM connection timeout after 60 seconds                                                                           Last completed step: add_plan9_shares
  App version: Claude 1.1.7464.0 (Windows)                                                                                OS: Windows 10 Enterprise 10.0.19045                                                                                                                                                                                                            Timeline:                                                                                                               - 12:29:07 - VM booted, add_plan9_shares completed                                                                      - 12:30:09 - Timeout fired (60s)
  - 12:30:59 - Network status: CONNECTED  ← VM was actually alive
  - 12:31:00 - API reachability: REACHABLE

Steps to Reproduce

1. Open Task Manager and end any lingering Claude processes: - Claude.exe

• Any claude or node processes related to it
• 2. Cold-boot your machine (or just ensure it's been a while since Claude last ran — the VM image needs to be "cold")
• 3. 3. Launch Claude Desktop
• 4. 4. Immediately open the log file to watch in real time: %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs\main.log
• 5. 5. Wait — within ~60–90 seconds you should see: [VM:start] Connection timeout, last completed step: add_plan9_shares [VM:start] Startup failed: VM connection timeout after 60 seconds - 6.6. followed shortly by: [VM] Network status: CONNECTED

[VM] API reachability: REACHABLE
Note: This may not reproduce every time — it's a cold-start timing issue, so it's more likely on first launch after a reboot or when the system is under load. If it doesn't trigger, try rebooting Windows first and launching Claude Desktop immediately after login.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.79 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_