claude-code - 💡(How to fix) Fix Cowork — HNS virtual network never created, NAT rule orphaned, API unreachable (Windows 11 Pro) [1 comments, 2 participants]

Error Messages/Logs

TL;DR

Create the missing HNS virtual network and vEthernet adapter to establish a route to the Claude API.

Guidance

• Verify that the HNS service is running and properly configured on the Windows 11 Pro system.
• Check the PowerShell output of hnsdiag.exe list networks to confirm the absence of the cowork-vm-nat network.
• Run the command Get-NetNat to confirm the existence of the cowork-vm-nat NAT rule, and check its configuration.
• Attempt to manually create the cowork-vm-nat HNS network and vEthernet adapter using PowerShell commands to test if this resolves the issue.

Example

No specific code example is provided due to the lack of explicit details on the required network configuration.

Notes

The issue seems to be related to a regression in the Claude Desktop application, where it fails to create the necessary HNS virtual network and vEthernet adapter for the VM to route through. The exact commands or configuration required to manually create these components are not specified in the issue.

Recommendation

Apply a workaround by manually creating the necessary HNS virtual network and vEthernet adapter, as the root cause of the issue is likely related to a missing configuration step in the Claude Desktop application.