exec_command fails with os error 2

“Every attempted sandboxed exec_command invocation in this session fails during process creation, including the minimal command pwd.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/14543/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Sandboxed exec_command fails with os error 2 in WSL sessions. Codex Desktop on Windows with the agent in WSL2 fails at "unified_exec_startup", even for pwd with a Linux-native cwd.

Is this your bug?

File my report

Where: WSL sandboxed shell
Error text: exec_command failed: CreateProcess { message: "Rejected(\"Failed to create unified exec process: No such file or directory (os error 2)\")" }
Versions: 0.159.0
Platforms: Windows
How bad: Breaks a normal workflow.

Part of: WSL agent cannot run commands3 bugs

WSL agent commands fail to spawn70 people
node_repl rejects Linux cwd3 people

Not quite your bug?

Project creation fails in WSL5 people
Sandbox setup refresh fails308 people

Original reports2, newest first

Oct 1, 2026Windows Desktop WSL unified_exec_startup fails with ENOENT even with valid Linux-native cwd and bashOn GitHub#49969
Sep 29, 2026Codex Desktop: exec_command fails in WSL-style session with os error 2, including pwd in /tmp, after restartOn GitHub#49365