23 people reported

All time, since Sep 19, including 12 thumbs-up on GitHub.

Setup refresh error blocks commands

“Codex cannot execute terminal commands on Windows.”

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/14525/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

Quiet. No reports and thumbs-up in the last two weeks, down from 10 a week at the late-September peak.

Local commands fail with setup refresh error on Windows. Windows sandbox cannot initialize, so every local command, even Get-Location, fails before the process starts; MCP tool calls still execute.

Is this your bug?

File my report
Where
Windows sandbox
Error text
helper_unknown_error: setup refresh had errors
message: "Rejected(\"Failed to create unified exec process: helper_unknown_error: setup refresh had errors\")"Pasted in 3 reports
CreateProcess: Rejected("Failed to create unified exec process: helper_unknown_error: setup refresh had errors")Pasted in 2 reports
Versions
0.162.1 to 26.928.31416
Platforms
Windows
How bad
Stops work: a core feature can't be used. Some reports say it blocks them completely.

Part of: Windows sandbox setup blocks commands18 bugs

  1. Sandbox setup refresh fails308 people
  2. Sandbox fails at deny-read ACLs10 people
  3. Sandbox setup lock failure12 people
  4. Split writable root sandbox failure3 people
  5. Sandbox fails on WSL UNC paths4 people
  6. Windows sandbox setup fails validating long cua_node runtime paths11 people
  7. Windows setup stops without UAC3 people
  8. Sandbox ACL update failure2 people
  9. Sandbox ACL refresh fails2 people
  10. Managed networking sandbox error2 people
Show all 17Show only the largest 10
  1. Sandbox refresh fails on old runtime2 people
  2. Sandbox fails on Google Drive2 people
  3. Sandbox provisioning failed2 people
  4. Windows sandbox provisioning fails3 people
  5. Windows sandbox setup access denied2 people
  6. Root read access sandbox error12 people
  7. Shell and Node tools fail with MXC 0x80070020 on Windows2 people

Not quite your bug?

  1. WSL agent commands fail to spawn70 people
  2. MXC sandbox startup failure11 people

Original reports11, newest first

  1. Windows command tool fails to start: setup refresh had errorsOn GitHub#54613
  2. Local process bridge is unavailableOn GitHub#54577
  3. Codex CLI fails to create unified exec process on WindowsOn GitHub#53060
  4. Windows sandbox initialization fails with “setup refresh had errors”On GitHub#50007
  5. Windows desktop: exec_command fails before process creation with helper_unknown_error: setup refresh had errorsOn GitHub#49851
  6. Windows: all commands fail with “helper_unknown_error: setup refresh had errors”On GitHub#49234
  7. Local scheduled tasks in Codex on Windows cannot run: setup refresh initialization failsOn GitHub#49142
  8. Windows local commands fail before starting: helper_unknown_error: setup refresh had errorsOn GitHub#49017
  9. Windows sandbox fails with helper_unknown_error: setup refresh had errorsOn GitHub#48979
  10. Setup Refresh had ErrorsOn GitHub#48759
Show all 11Show only the newest 10
  1. Windows sandbox failure wasted user time and Codex usage while blocking all local workOn GitHub#46668

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.