[Bug] Segmentation fault in seccomp binary on Windows WSL2 after update

Resolved 💬 2 comments Opened Mar 22, 2026 by talha-KL Closed Apr 20, 2026

Bug Description
I'm getting a segmentation fault when launching Cowork on Windows. The error is:
CLI output was not valid JSON. This may indicate an error during startup. Output: /usr/bin/bash: line 4: 5 Segmentation fault (core dumped) /usr/local/lib/node_modules_global/lib/node_modules/@anthropic-ai/sandbox-runtime/vendor/seccomp/x64/apply-seccomp
My setup:

OS: Windows 11
WSL: Version 2.6.3, Ubuntu (fresh install)
WSL Kernel: 6.6.87.2-microsoft-standard-WSL2
Node: v22.19.0
claude-code + sandbox-runtime: latest (just reinstalled)

What I tried:

Updated WSL, reinstalled Ubuntu
Reinstalled @anthropic-ai/claude-code and @anthropic-ai/sandbox-runtime
Set CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, DISABLE_SECCOMP, CLAUDE_CODE_SKIP_SANDBOX env variables
The apply-seccomp binary is not found anywhere in WSL — it appears to be inside Cowork's internal container

It was working fine before today — stopped working after a Windows/WSL update.
Please advise on how to disable the seccomp sandbox or fix the binary incompatibility.

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.81
  • Feedback ID: f48a7ced-bdb6-4410-8ba1-f9e76e4a2603

Errors

[]

View original on GitHub ↗

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