Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Cowork Windows: cowork-vm-nat HNS network never created, bridge sockets fail on every session [5 comments, 5 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#49365•Fetched 2026-04-17 08:43:13
View on GitHub
Comments
5
Participants
5
Timeline
20
Reactions
1
Author
ViscteViscte
Participants
BrozeyBrozeychris84wachris84wagithub-actions[bot]github-actions[bot]SeniorStorytellerSeniorStorytellerViscteViscte
Timeline (top)
cross-referenced ×7commented ×5labeled ×4mentioned ×2

Error Message

[warn] [vm-stderr] Error: Failed to create bridge sockets after 5 attempts [info] [VM:steps] create_network completed (0ms) [info] [Process] Exited, code=1, signal=null, duration=1023ms, oom=false

Root Cause

Root cause identified through log analysis: cowork-vm-nat HNS network is never created. Get-HnsNetwork only shows Default Switch. The VM boots successfully (confirmed via hcsdiag list) but the bridge socket layer fails because the NAT network doesn't exist.

Code Example

[warn] [vm-stderr] Error: Failed to create bridge sockets after 5 attempts
[info] [VM:steps] create_network completed (0ms)
[info] [Process] Exited, code=1, signal=null, duration=1023ms, oom=false
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 fails on every session with "Failed to create bridge sockets after 5 attempts".

Root cause identified through log analysis: cowork-vm-nat HNS network is never created. Get-HnsNetwork only shows Default Switch. The VM boots successfully (confirmed via hcsdiag list) but the bridge socket layer fails because the NAT network doesn't exist.

Suspicious log line: [VM:steps] create_network completed (0ms) — network creation completes instantly, suggesting it is silently no-oping rather than actually creating the HNS network.

CoworkVMService is running. VM boots and SDK installs successfully. API is reachable. Only the bridge socket step fails.

What Should Happen?

Cowork session should start successfully and execute tasks

Error Messages/Logs

[warn] [vm-stderr] Error: Failed to create bridge sockets after 5 attempts
[info] [VM:steps] create_network completed (0ms)
[info] [Process] Exited, code=1, signal=null, duration=1023ms, oom=false

Steps to Reproduce

  1. Open Claude Desktop
  2. Switch to Cowork tab
  3. Start any new session
  4. Session immediately fails with "Claude Code process exited with code 1"

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

unknown

Claude Code Version

1.3036

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Get-HnsNetwork shows only "Default Switch" — cowork-vm-nat is never created. VM boots successfully (hcsdiag list confirms running VM). CoworkVMService is running. HypervisorPlatform and VirtualMachinePlatform both enabled. ESET Smart Security installed. Windows 11 Pro. Claude Desktop version 1.3036.

extent analysis

TL;DR

Investigate and resolve the issue with the HNS network creation, as the "cowork-vm-nat" network is not being created, causing the bridge socket layer to fail.

Guidance

  • Verify the HypervisorPlatform and VirtualMachinePlatform settings to ensure they are correctly enabled, as these are required for HNS network creation.
  • Check the ESET Smart Security configuration to see if it's interfering with the HNS network creation, as some security software can block or restrict virtual network creation.
  • Run the Get-HnsNetwork command with administrative privileges to ensure that the command has sufficient permissions to create and manage HNS networks.
  • Investigate the "create_network completed (0ms)" log line to determine why the network creation is completing instantly, suggesting a potential issue with the network creation process.

Example

No code snippet is provided as the issue is related to a specific configuration and network setup.

Notes

The issue seems to be related to a regression, as it worked in a previous version. The exact cause of the issue is still unknown, and further investigation is required to determine the root cause.

Recommendation

Apply a workaround by checking the security software configuration and HypervisorPlatform settings, as these are potential causes of the issue, and resolving these may allow the HNS network to be created successfully.

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…
#api#serialization error#model compatibility#GPU setup#container setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING