WSL vsock error prevents any command execution (UtilBindVsockAnyPort: socket failed 1)

Open 💬 5 comments Opened Dec 19, 2025 by jrbrodie77

What version of Codex is running?

0.75.0

What subscription do you have?

Plus

Which model were you using?

codex 5.2 max

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

What happened
Any command execution from the Codex CLI inside WSL fails immediately with:
WSL (<pid> - ) ERROR: UtilBindVsockAnyPort:287: socket failed 1

This blocks building and even running wsl.exe --version.

Actual
Immediate failure with:
WSL (xxxx - ) ERROR: UtilBindVsockAnyPort:287: socket failed 1

Environment

WSL version: 2.4.13.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5716
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.7462

What steps can reproduce the bug?

Steps to reproduce

  1. Open WSL (Ubuntu).
  2. Run any command via Codex CLI (example: ./build.sh or powershell.exe -Command "dotnet build Automator2024.sln -c

Debug").

  1. Command fails with the vsock error before executing.

What is the expected behavior?

Expected
Command executes normally.

Additional information

Notes
The error appears to be WSL subsystem related rather than project-specific. It occurs before any build output.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗