Windows sandbox cannot spawn shell processes after escalation disabled

Open 💬 1 comment Opened Apr 23, 2026 by JDLondon7

What version of Codex CLI is running?

v0.124.0

What subscription do you have?

pro

Which model were you using?

5.5

What platform is your computer?

windows 11 pro

What terminal emulator and version are you using (if applicable)?

Powershell7

What issue are you seeing?

Error

```text
windows sandbox: runner error: CreateProcessAsUserW failed: 5

### Repro

Try either of these from the shell tool:

rg -n "example" src

bash -lc 'pwd'

Both fail with the same sandbox runner error before the command
executes.

  • Normal sandboxed shell commands failed with

CreateProcessAsUserW failed: 5.

  • Escalated shell commands worked.

approval policy is currently never. Do not provide
sandbox_permissions for any reason

After that:

  • Normal PowerShell still failed.
  • Bash also failed.
  • Escalation could no longer be requested.
  • apply_patch still worked.

inside the workspace, or escalation should remain available when
the Windows sandbox cannot create the process.

### Notes

Windows error code 5 from CreateProcessAsUserW is Access Denied.
The failure appears to occur in the sandbox runner before
launching the requested command.

What steps can reproduce the bug?

go on full access gpt 5.5 had to use escalted powershell to get it to work which is weird

What is the expected behavior?

codex should be able to use its commands was fine a moment ago before i updated

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗