AI coding · fixes · 2026-10-24

Codex “helper_unknown_error” on Windows: how to fix it

As of 24 October 2026. This is a fast-moving problem. OpenAI may change things at any time, so check the linked issue and docs before you follow any step.

If you want the next step, read Codex desktop “Cannot serialize value” error on new worktree chats: how to fix it.

If every command in Codex on Windows fails before it runs, you may see this:

Failed to create unified exec process: helper_unknown_error: setup refresh had errors

That's the exact line quoted in openai/codex #53623 (opened 13 Oct 2026), on Codex CLI 0.162.1 in PowerShell on Windows 11 Pro. The reporter says the same command runs fine in PowerShell outside Codex, and "Restarting the computer and opening Codex again did not fix the issue."

Quick fix: rerun the Windows sandbox setup

OpenAI's Windows sandbox page says, for a failed setup: "Try the elevated sandbox setup again and approve the administrator prompt if your environment allows it." Restart Codex, run the setup again, and approve the Windows UAC prompt if you're allowed to.

What the error means

OpenAI's docs don't name helper_unknown_error as of 24 October 2026. In #53623, the codex doctor report ties it to the sandbox: its sandbox.helpers check failed with the summary "elevated Windows sandbox provisioning recorded a structured failure", "sandbox backend": "elevated", and "error code": "helper_unknown_error". So the likely meaning is that the elevated sandbox setup didn't complete.

Per OpenAI's troubleshooting page, the most common causes of a failed elevated setup are: "the Windows UAC or administrator prompt was declined, the machine does not allow local user or group creation, the machine does not allow firewall rule changes, the machine blocks the logon rights needed by the sandbox users, or another enterprise policy blocks part of the setup flow."

Try MXC instead

The docs call mxc "The recommended sandbox on compatible Windows devices", which "Uses native process isolation without administrator-approved setup, additional Windows accounts, or local firewall rules." In Codex CLI 0.162.0 and later, you can test it for one command from your project directory:

codex -c windows.sandbox=mxc sandbox --include-managed-config --permission-profile :workspace -- cmd.exe /d /c echo MXC_OK
$LASTEXITCODE

The docs say the expected output is MXC_OK with exit code 0. If it works, turn MXC on in config.toml:

[features]
prefer_mxc = true

The docs say Microsoft introduced MXC process isolation in Windows 11 24H2 (build 26100.9278) and 25H2 (build 26200.9278), so older builds may not support it.

Fall back to the unelevated sandbox

If setup still fails and your organization's policy allows it, the docs suggest using unelevated "while the issue is investigated":

[windows]
sandbox = "unelevated"

Know the trade-off. The docs call unelevated "A legacy fallback when elevated setup is unavailable and organizational policy permits it" that "Has weaker network isolation than elevated and doesn’t support denied read paths." Treat it as a temporary step and switch back once setup works.

On a work laptop: what to ask IT

The docs suggest asking IT "whether the machine allows administrator-approved setup for local user/group creation, firewall configuration, and the required sandbox-user logon rights." IT can also set up the elevated sandbox for you from an elevated deployment process:

codex sandbox setup --elevated --user 'DOMAIN\alice' --codex-home 'C:\Users\alice\.codex'

They replace the identity and path with yours. If Codex warns that some folders are writable by Everyone, the docs suggest reviewing those folders, removing Everyone write access where appropriate, and re-running setup.

Don’t do this

Don't try to turn off unified exec. The config reference says features.unified_exec is "(stable; enabled on all platforms). User opt-outs are ignored."
Don't switch to full access as a fix. The Windows sandbox page warns: "Running Codex in full access mode means Codex is not limited to your project directory and might perform unintentional destructive actions that can lead to data loss." Commands may run again, but you lose the sandbox's protection for your files.

Send diagnostics

If none of this helps, add your details to #53623 or contact OpenAI. The docs ask for CODEX_HOME/.sandbox/sandbox.log, the sandbox implementation you selected, the error message, your Windows build, and whether you're on Windows 11 or Windows 10. They also say: do not send the contents of CODEX_HOME/.sandbox-secrets/.

FAQ

Can I turn off unified exec? No. The config reference says user opt-outs are ignored.

Is unelevated safe? It's still sandboxed, but the docs say it has weaker network isolation than elevated. Use it as a temporary fallback where policy allows.

Does WSL avoid it? This error comes from the native Windows sandbox. OpenAI has a separate WSL page, but we haven't tested whether WSL avoids it.

Which Windows builds support MXC? The docs name Windows 11 24H2 (build 26100.9278) and 25H2 (build 26200.9278). Run the probe above to check your device.

What's error 1385? The docs say it means "Windows is denying the logon type the sandbox user needs in order to start the command", which is usually a device policy for IT to check.

Do I need admin rights? The elevated sandbox "Requires administrator-approved setup", per the docs. MXC doesn't, on compatible devices.

Sources

Checked 24 Oct 2026: github.com/openai/codex issue #53623 and its comments; developers.openai.com/codex/windows; developers.openai.com/codex/config-reference.

OpenAI and Codex are trademarks of OpenAI. Windows, Windows 11, PowerShell, and WSL are trademarks of Microsoft Corporation. GitHub is a trademark of GitHub, Inc. Other names belong to their owners. Names are used only to identify products and compatibility. Stack & Ship is not affiliated with or endorsed by any of them.