5 people reported
All time, since Oct 1, including 4 thumbs-up on GitHub.
Unified exec ENOENT in WSL2
“Failed to create unified exec process: No such file or directory (os error 2)”
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/14450/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
Command execution fails in WSL2 with unified exec ENOENT. Codex Desktop on Windows with the agent in WSL2 fails before simple commands such as pwd or ls start, though the WSL terminal and project work normally.
Is this your bug?
File my report- Where
- Codex Desktop WSL2
- Error text
Failed to create unified exec process: No such file or directory (os error 2)- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Original reports1, newest first
- [Windows][WSL2] Temporary workaround for unified exec ENOENTOn GitHub#50146