claude-code - 💡(How to fix) Fix [BUG] Cowork fails - VM cannot reach Claude API, Default Switch is Internal type with no external uplink (Windows 11 Pro, v1.3883.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#52128Fetched 2026-04-23 07:35:53
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
labeled ×4commented ×1

Error Message

Error Messages/Logs

Default Switch remains Internal with no uplink. VM boots but API is unreachable. Error: "Can't reach the Claude API from Claude's workspace."

Root Cause

Network — host reaches API fine: Test-NetConnection -ComputerName api.anthropic.com -Port 443 TcpTestSucceeded: True (160.79.104.10) Network adapters (sorted by metric): Ethernet IPv4 metric 4 Disconnected Wi-Fi IPv4 metric 10 Connected vEthernet (Default Switch) IPv4 metric 5000 Connected vEthernet (Default Switch) IPv6 metric 5000 Connected Root cause identified: Get-VMSwitch Name SwitchType NetAdapterInterfaceDescription Default Switch Internal The Hyper-V Default Switch is type Internal — it has no external adapter assigned as uplink. The Cowork VM boots and gets network status CONNECTED internally, but cannot route traffic to api.anthropic.com because the switch has no path to the physical network. Steps already tried without success:

Fix Action

Fix / Workaround

Expected behavior Cowork should either create an External virtual switch linked to the active network adapter, or configure NAT correctly so the VM can reach api.anthropic.com. Actual behavior Default Switch remains Internal with no uplink. VM boots but API is unreachable. Error: "Can't reach the Claude API from Claude's workspace." Question for the team Should Cowork automatically create an External switch or configure NAT on setup? Is there a manual workaround that doesn't require permanently bridging the physical Wi-Fi adapter?

Code Example

Can't reach the Claude API from Claude's workspace
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 consistently fails to start with "Can't reach the Claude API from Claude's workspace." Regular Chat mode works perfectly. A yellow validation_failed badge appears briefly in the Cowork tab.

What Should Happen?

Cowork should either create an External virtual switch linked to the active network adapter, or configure NAT correctly so the VM can reach api.anthropic.com.

Error Messages/Logs

Can't reach the Claude API from Claude's workspace

Steps to Reproduce

Start Cowork - it fails

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

1.3883.0 (93ff6c), 2026-04-21

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Troubleshooting performed Hyper-V & services — all OK:

Hyper-V enabled (Microsoft-Hyper-V-All → State: Enabled) CoworkVMService: Running vmcompute: Running vmms: Running Virtualization enabled in BIOS (HyperVRequirementVirtualizationFirmwareEnabled: True)

Network — host reaches API fine: Test-NetConnection -ComputerName api.anthropic.com -Port 443 TcpTestSucceeded: True (160.79.104.10) Network adapters (sorted by metric): Ethernet IPv4 metric 4 Disconnected Wi-Fi IPv4 metric 10 Connected vEthernet (Default Switch) IPv4 metric 5000 Connected vEthernet (Default Switch) IPv6 metric 5000 Connected Root cause identified: Get-VMSwitch Name SwitchType NetAdapterInterfaceDescription Default Switch Internal The Hyper-V Default Switch is type Internal — it has no external adapter assigned as uplink. The Cowork VM boots and gets network status CONNECTED internally, but cannot route traffic to api.anthropic.com because the switch has no path to the physical network. Steps already tried without success:

Updated Claude Desktop to latest version (1.3883.0) Enabled Hyper-V + reboot Cleared cache via Help → Troubleshooting → Clear cache and restart Deleted vm_bundles and claude-code-vm from %APPDATA%\Claude + restarted HNS and vmcompute Adjusted network adapter metrics (Wi-Fi to 10, Ethernet to 4) Full PC reboot after each attempt

Expected behavior Cowork should either create an External virtual switch linked to the active network adapter, or configure NAT correctly so the VM can reach api.anthropic.com. Actual behavior Default Switch remains Internal with no uplink. VM boots but API is unreachable. Error: "Can't reach the Claude API from Claude's workspace." Question for the team Should Cowork automatically create an External switch or configure NAT on setup? Is there a manual workaround that doesn't require permanently bridging the physical Wi-Fi adapter?

extent analysis

TL;DR

The most likely fix is to manually create an External virtual switch linked to the active network adapter or configure NAT correctly to allow the Cowork VM to reach the Claude API.

Guidance

  • The root cause is identified as the Hyper-V Default Switch being an Internal switch without an external adapter assigned as uplink, preventing the Cowork VM from routing traffic to the physical network.
  • To verify, check the output of Get-VMSwitch to confirm the switch type and NetAdapterInterfaceDescription.
  • A potential workaround is to manually create an External virtual switch linked to the active network adapter (e.g., Wi-Fi) and configure the Cowork VM to use this switch.
  • Another possible solution is to configure NAT correctly to allow the Cowork VM to reach the Claude API, although the exact steps for this are not specified in the issue.

Example

No code snippet is provided as the issue does not imply a specific code change, but rather a configuration or setup issue.

Notes

The issue lacks information on how to configure NAT correctly for the Cowork VM, and it is unclear if this is a supported configuration. Additionally, permanently bridging the physical Wi-Fi adapter may not be a desirable solution.

Recommendation

Apply a manual workaround by creating an External virtual switch linked to the active network adapter, as this is a more straightforward and reversible change compared to configuring NAT or permanently bridging the physical adapter.

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…

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 fails - VM cannot reach Claude API, Default Switch is Internal type with no external uplink (Windows 11 Pro, v1.3883.0) [1 comments, 2 participants]