Rank, 14 days: 23 on the Codex sheet
399 people reported

All time, since Sep 14, including 131 thumbs-up on GitHub.

Windows sandbox setup blocks commands

“Browser control, Windows computer use, and sandboxed shell commands fail before they can perform any action.”

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/themes/107/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

Growing. 7 reports and thumbs-up in the last 7 days and 2 the week before, down from 324 a week at the early-October peak.

18 bugs in this theme

  1. Sandbox setup refresh failsHas a workaround308 people
  2. Setup refresh error blocks commandsNo workaround yet23 people
  3. Sandbox setup lock failureHas a workaround12 people
  4. Root read access sandbox errorNo workaround yet12 people
  5. Windows sandbox setup fails validating long cua_node runtime pathsHas a workaround11 people
  6. Sandbox fails at deny-read ACLsNo workaround yet10 people
  7. Sandbox fails on WSL UNC pathsNo workaround yet4 people
  8. Split writable root sandbox failureNo workaround yet3 people
  9. Windows setup stops without UACNo workaround yet3 people
  10. Windows sandbox provisioning failsNo workaround yet3 people
Show all 18Show only the largest 10
  1. Sandbox ACL update failureNo workaround yet2 people
  2. Sandbox ACL refresh failsNo workaround yet2 people
  3. Managed networking sandbox errorNo workaround yet2 people
  4. Sandbox refresh fails on old runtimeNo workaround yet2 people
  5. Sandbox fails on Google DriveHas a workaround2 people
  6. Sandbox provisioning failedHas a workaround2 people
  7. Windows sandbox setup access deniedNo workaround yet2 people
  8. Shell and Node tools fail with MXC 0x80070020 on WindowsNo workaround yet2 people

What's included

  • Setup refresh exits with "helper_unknown_error: setup refresh had errors" during ACL work: os error 32 or 5 on cua_node runtime files, stale or over-long runtime paths, a NUL-filled deny_read_acl_state.json, Google Drive or WSL UNC workspaces, or Administrators-owned folders
  • "sandbox provisioning failed" with helper_sandbox_lock_failed, access denied on %USERPROFILE%\.codex\.sandbox-bin, returning after an ACL repair
  • "Setup stopped" right after Retry setup with no UAC prompt, then "registered Core setup has not completed"
  • Sandbox preparation refuses to run: "managed networking requires the elevated Windows sandbox backend" or "cannot enforce split writable root sets" in Work, delegated or scheduled tasks
  • CreateProcessSecurityEnvironment fails with HRESULT 0x80070020 before any command starts

Not included

  • Command failures on macOS or Linux sandboxes
  • Commands that start but then fail or time out inside the sandbox
  • Approval prompt or permission-mode behavior once commands do run

Original reports270, newest first

  1. Windows app 26.1103.3517.0: sandbox setup still fails after granting SYSTEM WRITE_DAC to .sandbox-binOn GitHub#60057
  2. Access being deined to SandboxOn GitHub#59744
  3. Windows CLI 0.166.0: exec_command blocked by policy in read-only and split writable-root failure in workspace-writeOn GitHub#59314
  4. Windows: MXC CreateProcessSecurityEnvironment 0x80070020 blocks shell, Node and local workbook accessOn GitHub#59072
  5. Windows sandbox initialization fails: SYSTEM denied WRITE_DAC on .sandbox-binOn GitHub#59038
  6. Windows app (Store 26.1027.3384.0): no window for ~5 min after update – main thread synchronously copies cua_node; killing it restarts the copy. Also sandbox setup resets .sandbox-bin ACL every runOn the forum#1410972
  7. Windows app 26.1023.6621.0: sandbox setup fails with helper_sandbox_lock_failed on protected .sandbox-bin ACLOn GitHub#57617
  8. Windows Work local execution blocked by helper_sandbox_lock_failed on 26.1016.6573.0; persists after reboot and RepairOn GitHub#56605
  9. Windows desktop 26.1016.61520: shell and Node tools fail with MXC CreateProcessSecurityEnvironment 0x80070020 after rebootOn GitHub#56138
  10. Windows elevated sandbox ACL refresh fails with os error 5 in both existing and fresh Git workspaces (CLI 0.163.0)On GitHub#56078
Show the newest 100 of 270Show only the newest 10
  1. Windows: local file operations fail with “setup refresh had errors”On GitHub#55760
  2. Unknown — selected model is GPT Astra 6 Light, but I haven’t located the app version.On GitHub#54621
  3. helper_sandbox_lock_failed — access denied to C:\Users\User\.codex\.sandbox-bin.On GitHub#54617
  4. Windows command tool fails to start: setup refresh had errorsOn GitHub#54613
  5. Local process bridge is unavailableOn GitHub#54577
  6. [Windows] codex exec fails with helper_unknown_error during sandbox setup; standalone sandbox succeedsOn GitHub#54405
  7. Windows Codex CLI repeatedly fails with helper_unknown_error: setup refresh had errorsOn GitHub#54325
  8. Closed by the author; see #51932On GitHub#54284
  9. Windows elevated sandbox: setup refresh fails fatally when a Codex runtime file is mapped (open ACL target for root-only update: os error 32)On GitHub#54165
  10. Windows elevated sandbox: every command exits -1 when node_repl.exe is running (os error 32 during setup refresh)On GitHub#54138
  11. Windows Work Mode: command execution blocked by managed-networking sandbox error; runtime dependencies fail to loadOn GitHub#54117
  12. Windows Codex command runner fails on existing Git workspace due to sandbox ACL errorOn GitHub#53946
  13. Windows scheduled heartbeat omits cwd write permission and fails before command startup with split writable root setsOn GitHub#53863
  14. Workspace fails even after reinstall of appOn GitHub#53834
  15. Windows sandbox setup fails with ERROR_SHARING_VIOLATION (32) on node_repl.exe — Codex CLI 0.162.1On GitHub#53798
  16. Chat GPT Work BugOn GitHub#53722
  17. Windows sandbox setup fails ("setup refresh had errors") whenever the Codex desktop app is installed: runtime validation can't open cua_node\…\node_repl.exe (os error 32)On GitHub#53679
  18. 01a0c275-af4a-7032-b322-1ec31ababbeaOn GitHub#53611
  19. "helper_unknown_error: setup refresh had errors" observed when accessing my local Folder which is connect with a ProjectOn GitHub#53575
  20. [Windows] Elevated sandbox permanently broken after runtime self-update: setup refresh fails on self-locked node_repl.exe (os error 32); code-mode host pipe stuck BUSY (os error 231)On GitHub#53458
  21. Windows][Codex CLI 0.162.1] Sandbox initialization intermittently fails when updating workspace ACLOn GitHub#53454
  22. Windows ARM64: open in-app browser inaccessible to Computer Use; sandbox file-lock failures consume paid usageOn GitHub#53415
  23. Windows: every shell command fails with "helper_unknown_error: setup refresh had errors" (v0.162.1)On GitHub#53158
  24. Windows shell setup fails with sharing error 32 on Codex node_repl.exeOn GitHub#53151
  25. [Windows][VS Code] Terminal creation fails: helper_unknown_error / setup refresh had errorsOn GitHub#53121
  26. Codex fails to use Shell commands (Get-ChildItem, Get-Content, etc.)On GitHub#53096
  27. Windows desktop: setup refresh failure prevents local document access and both shell and Node executionOn GitHub#53078
  28. Codex CLI fails to create unified exec process on WindowsOn GitHub#53060
  29. Windows sandbox "setup refresh" fails with sharing violation on node_repl.exe, which codex itself just spawned (helper_unknown_error)On GitHub#52976
  30. Windows: commands fail before execution with “setup refresh had errors”On GitHub#52975
  31. [CLI Bug] Failed to create unified exec process: helper_unknown_error: setup refresh had errorsOn GitHub#52944
  32. Windows app 26.1007.2314.0: active 0.162.1 sandbox helper fails with error 32 / MAXIMUM_ALLOWED on CUA runtimeOn GitHub#52897
  33. Windows elevated sandbox startup blocked by 22-NUL-byte deny_read_acl_state.jsonOn GitHub#52859
  34. Codex workspace command runner fails to initialize with “setup refresh had errors”On GitHub#52772
  35. Windows sandbox fails with os error 32 on node_repl.exe before local shell executionOn GitHub#52757
  36. [Windows desktop] Sandbox setup refresh fails with sharing violation on app tools node.exe after browser/computer-use isolationOn GitHub#52740
  37. GPT-6 File Reader Not WorkingOn the forum#1404899
  38. Windows sandbox provisioning always fails: setup tries to ACL runtime binaries Codex itself is executing (os error 32)On GitHub#52735
  39. Windows browser control fails: sandbox setup error 32 on node_repl.exe, persists after rebootOn GitHub#52722
  40. Windows ARM64 sandbox provisioning fails with os error 32 (elevated and unelevated)On GitHub#52712
  41. Windows: elevated sandbox setup refresh errors block local tools after 26.1002 updateOn GitHub#52662
  42. Unable to read the contentOn GitHub#52657
  43. Windows dot local delegation: sandbox setup refresh keeps failingOn GitHub#52630
  44. Chrome automation fails on Windows before connecting to a healthy extensionOn GitHub#52626
  45. File Creation FailOn GitHub#52624
  46. Codex browser runtime failureOn GitHub#52617
  47. Windows sandbox fails on two workstations: node_repl.exe ACL validation os error 32; Full Access succeedsOn GitHub#52616
  48. Windows non-admin user: previously working Browser and shell fail with sandbox mutex and .sandbox-bin errorsOn GitHub#52614
  49. Windows: sandbox setup fails with os error 32 on node_repl.exe; browser and terminal tools unavailableOn GitHub#52611
  50. Windows sandbox: process creation fails with setup refresh had errors while full access worksOn GitHub#52606
  51. Windows elevated sandbox setup fails with os error 32 on CUA runtime filesOn GitHub#52601
  52. Windows Codex App 26.1002.52244: sandbox refresh fails on node_repl.exe with os error 32 after rebootOn GitHub#52595
  53. Persistent command-execution failure on connected Windows computerOn GitHub#52589
  54. Windows desktop sandbox ACL refresh fails on VCRUNTIME140_1.dll (os error 32); request supported recoveryOn GitHub#52586
  55. Windows sandbox fails before Get-Location: node_repl.exe sharing violation (error 32)On GitHub#52583
  56. Windows sandbox setup fails with OS error 32 when computer-use runtime files are in useOn GitHub#52572
  57. Windows desktop: sandbox runtime ACL validation sharing violation persists after update and reinstallOn GitHub#52571
  58. codex not workOn GitHub#52569
  59. Windows sandbox is permanently unusable: setup refresh races the app's own runtime helpers and always fails with ERROR_SHARING_VIOLATIONOn GitHub#52566
  60. Windows: local tools fail during sandbox setup with OS error 32 on node_repl.exeOn GitHub#52561
  61. Chat gpt showing errorOn GitHub#52558
  62. Windows 10: setup refresh had errors — sandbox setup cannot set the ACL on a running node_repl.exe (os error 32), provisioning stays failed foreverOn GitHub#52554
  63. Windows sandbox setup blocks shell and Node tools; approved execution outside sandbox succeedsOn GitHub#52545
  64. Windows command execution fails with “helper_unknown_error: setup refresh had errors” despite connected computerOn GitHub#52541
  65. [Windows] Shell execution fails: helper_unknown_error: setup refresh had errorsOn GitHub#52538
  66. Windows IDE: browser helper groups persist across conversation resumes and block sandbox ACL refresh (node_repl.exe error 32)On GitHub#52537
  67. codex - unable to run local commandsOn GitHub#52526
  68. Has stopped being able to operate programs on my PC (but could do this 2 days ago)On GitHub#52525
  69. Windows elevated sandbox setup refresh fails with os error 32 in 0.162.0-alpha.2On GitHub#52518
  70. [Windows App] Sandbox setup refresh fails after updateOn GitHub#52514
  71. Windows elevated sandbox setup fails with error 32 on node_repl.exeOn GitHub#52506
  72. [Windows] Sandbox setup fails when Codex’s own node_repl.exe is running (os error 32)On GitHub#52504
  73. Windows sandbox setup refresh fails with os error 32 (sharing violation) on running node_repl.exe — structural start-order conflict between cua_node runtime and ACL validationOn GitHub#52501
  74. [Windows] Sandbox setup failure blocks local commands and file editing (helper_unknown_error / os error 32)On GitHub#52499
  75. Windows sandbox unusable: setup refresh fails with os error 32 (app-tools MCP holds the cua_node runtime exe)On GitHub#52488
  76. Windows sandbox failed: setup refresh had errorsOn GitHub#52482
  77. Windows sandbox failure caused repeated task failures and wasted usage quota — request for quota restorationOn GitHub#52481
  78. Windows Codex shell blocked by node_repl.exe sharing violation during sandbox setup (os error 32, Oct 9 repro)On GitHub#52476
  79. Windows desktop: terminal fails after update with helper_unknown_error: setup refresh had errorsOn GitHub#52467
  80. Codex Desktop Windows sandbox initialization fails with a locked node_repl.exeOn GitHub#52462
  81. [Windows] delegated tasks fail before shell startup with “setup refresh had errors”; logs report error 32 on node_repl.exeOn GitHub#52461
  82. Codex Windows Desktop – Shell fails to start: sandbox setup refresh / OS error 32On GitHub#52453
  83. no-active-thread-01a11f91-521e-7f61-a88f-2ea6b8627687On GitHub#52448
  84. Windows: local commands fail with "helper_unknown_error: setup refresh had errors"On GitHub#52445
  85. Windows desktop app: sandbox setup fails with OS error 32 on node_repl.exe, blocking browser and local commandsOn GitHub#52441
  86. Windows desktop: node_repl / Computer Use startup fails with sandbox setup refresh sharing violation (os error 32)On GitHub#52438
  87. “Windows sandbox: setup refresh had errors”On GitHub#52434
  88. Windows desktop 26.1002.52244: runtime ACL sharing violation persists after full shutdown and app repairOn GitHub#52433
  89. Windows Codex 26.1002.7124.0: elevated sandbox ACL refresh fails on running node_repl.exe (os error 32); process timelineOn GitHub#52432
  90. Windows elevated sandbox fails on live runtime ACL refresh; unelevated restores executionOn GitHub#52427

Do you work on Codex?

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