Windows installer 0.145.0 missing codex-windows-sandbox-setup.exe
What version of the Codex App are you using (From “About Codex” dialog)?
Codex CLI 0.145.0
What subscription do you have?
Pro
What platform is your computer?
Windows 11 build 26200
What issue are you seeing?
Environment
- Windows 11
- Codex CLI 0.145.0
Problem
Managed sandbox operations consistently fail with:
orchestrator_helper_launch_failed:
setup refresh failed to launch helper:
helper=codex-windows-sandbox-setup.exe
error=program not found
I reinstalled Codex using the official installer.
Installation completed successfully, but the helper executable is still missing.
Diagnostics
Searching the installation directory:
Get-ChildItem -LiteralPath "$env:LOCALAPPDATA\Programs\OpenAI\Codex" -Recurse |
Where-Object { $_.Name -eq "codex-windows-sandbox-setup.exe" }
returns no results.
The bin directory contains only:
codex.exe
codex-code-mode-host.exe
The sandbox log repeatedly shows:
setup refresh: spawning codex-windows-sandbox-setup.exe
error=program not found
Result
- Read-only commands sometimes work.
- Any managed sandbox write or apply_patch eventually fails because the helper cannot be launched.
Question
Is the Windows installer missing codex-windows-sandbox-setup.exe, or has its location/name changed?
What steps can reproduce the bug?
The installer completed successfully.
codex-windows-sandbox-setup.exe is not found anywhere in the installation.
The sandbox log repeatedly reports:
orchestrator_helper_launch_failed
helper=codex-windows-sandbox-setup.exe
error=program not found
The bin directory contains only:
codex.exe
codex-code-mode-host.exe
What is the expected behavior?
not to spend a full day trying to figure out why the sandbox will not work
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I reviewed the existing Windows sandbox and CLI issues before filing this report.
Although there are several reports involving Windows sandbox startup failures, the investigation attached here isolates a different failure boundary:
If maintainers determine this is part of an existing tracked issue, I am happy to have this linked or merged as supporting evidence rather than maintained separately.