[BUG] Cowork Windows: API unreachable from VM + 12GB vm_bundle on never-working install (Win 11 Home, Intel Ultra 7)
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 workspace fails to start on Windows 11 Home. The Hyper-V micro-VM boots successfully and gets network connectivity, but cannot reach api.anthropic.com from inside the VM. Host machine connects to the API without issues. Regular Chat and Claude Code CLI work perfectly — only Cowork is affected.
Error message: "Não foi possível iniciar o espaço de trabalho do Claude - Não é possível acessar a API do Claude no workspace do Claude."
This is the same issue reported in #24918, #24962, #25241 — adding another Windows data point with detailed diagnostics.
Additional issue: The Cowork VM bundle (vm_bundles/claudevm.bundle) consumes ~12GB of disk space immediately after installation, even without ever successfully using Cowork. Related to #22543.
Environment
- OS: Windows 11 Home Single Language (Build 10.0.26220)
- CPU: Intel Core Ultra 7 155H
- RAM: 15.5 GB
- Claude Desktop Version: 1.1.2685
- Commit Hash: f39a622da544d39d746a0aba120ee29d06b1bd28
- Platform: win32 / x64
- SDK Version: 2.1.34
- Bundle Version: fc96f5bc6a7aeee6e651437eba3c76d0fe9a16f3
NAT Configuration (appears incomplete)
Get-NetNat: EMPTY (no NAT rules configured)
IP Forwarding: Disabled on vEthernet (cowork-vm-nat)
ICS (SharedAccess): Running
The VM gets general connectivity (SDK install succeeds in 4.5s) but cannot route HTTPS traffic to api.anthropic.com.
Network Adapters
| Name | Description | Status |
|------|-------------|--------|
| Wi-Fi | Intel Wi-Fi 6E AX211 160MHz | Up / Connected |
| Bluetooth | Bluetooth Device (PAN) | Disconnected |
| Kaspersky VPN | Kaspersky VPN adapter | Disconnected |
| vEthernet (cowork-vm-nat) | Hyper-V Virtual Ethernet Adapter | Up / Connected |
Host Network Test (all OK from host)
- DNS Resolution:
api.anthropic.com→ 160.79.104.10 - No VPN active
- No proxy configured
- TCP connection to
api.anthropic.com:443: SUCCESS
Troubleshooting Steps Taken (all failed)
- Restarted Claude Desktop multiple times
- Restarted PC
- Added
api.anthropic.comand*.anthropic.comto Kaspersky trusted domains - Added Claude.exe as trusted application in Kaspersky with full traffic bypass
- Paused Kaspersky protection entirely — same result
- Fully uninstalled and reinstalled Claude Desktop — same result
- Verified host connectivity to
api.anthropic.com— works fine - Submitted support log via in-app feedback on Feb 11 — no response after 6 days
Disk Space Impact
The vm_bundles directory consumes 11.89 GB despite Cowork never successfully starting:
vm_bundles: 11.89 GB
claude-code: 0.22 GB
claude-code-vm: 0.21 GB
Total Claude AppData: 12.51 GB
Related Issues
- #22543 — 10GB VM bundle, performance degradation (high-priority)
- #24918 — API unreachable from VM (Windows 11 Home)
- #24962 — Wrong DNS config, missing sessiondata.vhdx, no NAT
- #25241 — API unreachable (Windows 11 Home)
- #25206 — VM crashes within 5 minutes (Windows 11 Pro)
What Should Happen?
- Cowork VM should successfully connect to
api.anthropic.com - NAT rules should be properly configured (Get-NetNat should not be empty)
- IP forwarding should be enabled on the virtual adapter
- VM bundle should not consume 12GB when Cowork has never worked
- Support should respond to detailed bug reports
Error Messages/Logs
2026-02-11 05:14:19 [info] [VM] Network status: NOT_CONNECTED
2026-02-11 05:14:20 [info] [VM] Network status: CONNECTED
2026-02-11 05:14:25 [info] [VM] API reachability: PROBABLY_UNREACHABLE
2026-02-11 05:14:53 [info] [VM] API reachability: UNREACHABLE
2026-02-11 05:14:53 [warn] [VM:network] API is unreachable
Steps to Reproduce
- Install Claude Desktop v1.1.2685 on Windows 11 Home
- Open Claude Desktop → Click "Cowork" tab
- Wait for VM to download and initialize
- VM boots, network shows CONNECTED
- API reachability check fails: PROBABLY_UNREACHABLE → UNREACHABLE
Claude Model
None
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
1.1.2685 (Claude Desktop)
Platform
Other
Operating System
Windows
Additional Information
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗