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
18 bugs in this theme
- Sandbox setup refresh failsHas a workaround308 people
- Setup refresh error blocks commandsNo workaround yet23 people
- Sandbox setup lock failureHas a workaround12 people
- Root read access sandbox errorNo workaround yet12 people
- Windows sandbox setup fails validating long cua_node runtime pathsHas a workaround11 people
- Sandbox fails at deny-read ACLsNo workaround yet10 people
- Sandbox fails on WSL UNC pathsNo workaround yet4 people
- Split writable root sandbox failureNo workaround yet3 people
- Windows setup stops without UACNo workaround yet3 people
- Windows sandbox provisioning failsNo workaround yet3 people
Show all 18Show only the largest 10
- Sandbox ACL update failureNo workaround yet2 people
- Sandbox ACL refresh failsNo workaround yet2 people
- Managed networking sandbox errorNo workaround yet2 people
- Sandbox refresh fails on old runtimeNo workaround yet2 people
- Sandbox fails on Google DriveHas a workaround2 people
- Sandbox provisioning failedHas a workaround2 people
- Windows sandbox setup access deniedNo workaround yet2 people
- 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
- Windows app 26.1103.3517.0: sandbox setup still fails after granting SYSTEM WRITE_DAC to .sandbox-binOn GitHub#60057
- Access being deined to SandboxOn GitHub#59744
- Windows CLI 0.166.0: exec_command blocked by policy in read-only and split writable-root failure in workspace-writeOn GitHub#59314
- Windows: MXC CreateProcessSecurityEnvironment 0x80070020 blocks shell, Node and local workbook accessOn GitHub#59072
- Windows sandbox initialization fails: SYSTEM denied WRITE_DAC on .sandbox-binOn GitHub#59038
- 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
- Windows app 26.1023.6621.0: sandbox setup fails with helper_sandbox_lock_failed on protected .sandbox-bin ACLOn GitHub#57617
- Windows Work local execution blocked by helper_sandbox_lock_failed on 26.1016.6573.0; persists after reboot and RepairOn GitHub#56605
- Windows desktop 26.1016.61520: shell and Node tools fail with MXC CreateProcessSecurityEnvironment 0x80070020 after rebootOn GitHub#56138
- 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
- Windows: local file operations fail with “setup refresh had errors”On GitHub#55760
- Unknown — selected model is GPT Astra 6 Light, but I haven’t located the app version.On GitHub#54621
- helper_sandbox_lock_failed — access denied to C:\Users\User\.codex\.sandbox-bin.On GitHub#54617
- Windows command tool fails to start: setup refresh had errorsOn GitHub#54613
- Local process bridge is unavailableOn GitHub#54577
- [Windows] codex exec fails with helper_unknown_error during sandbox setup; standalone sandbox succeedsOn GitHub#54405
- Windows Codex CLI repeatedly fails with helper_unknown_error: setup refresh had errorsOn GitHub#54325
- Closed by the author; see #51932On GitHub#54284
- 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
- Windows elevated sandbox: every command exits -1 when node_repl.exe is running (os error 32 during setup refresh)On GitHub#54138
- Windows Work Mode: command execution blocked by managed-networking sandbox error; runtime dependencies fail to loadOn GitHub#54117
- Windows Codex command runner fails on existing Git workspace due to sandbox ACL errorOn GitHub#53946
- Windows scheduled heartbeat omits cwd write permission and fails before command startup with split writable root setsOn GitHub#53863
- Workspace fails even after reinstall of appOn GitHub#53834
- Windows sandbox setup fails with ERROR_SHARING_VIOLATION (32) on node_repl.exe — Codex CLI 0.162.1On GitHub#53798
- Chat GPT Work BugOn GitHub#53722
- 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
- 01a0c275-af4a-7032-b322-1ec31ababbeaOn GitHub#53611
- "helper_unknown_error: setup refresh had errors" observed when accessing my local Folder which is connect with a ProjectOn GitHub#53575
- [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
- Windows][Codex CLI 0.162.1] Sandbox initialization intermittently fails when updating workspace ACLOn GitHub#53454
- Windows ARM64: open in-app browser inaccessible to Computer Use; sandbox file-lock failures consume paid usageOn GitHub#53415
- Windows: every shell command fails with "helper_unknown_error: setup refresh had errors" (v0.162.1)On GitHub#53158
- Windows shell setup fails with sharing error 32 on Codex node_repl.exeOn GitHub#53151
- [Windows][VS Code] Terminal creation fails: helper_unknown_error / setup refresh had errorsOn GitHub#53121
- Codex fails to use Shell commands (Get-ChildItem, Get-Content, etc.)On GitHub#53096
- Windows desktop: setup refresh failure prevents local document access and both shell and Node executionOn GitHub#53078
- Codex CLI fails to create unified exec process on WindowsOn GitHub#53060
- Windows sandbox "setup refresh" fails with sharing violation on node_repl.exe, which codex itself just spawned (helper_unknown_error)On GitHub#52976
- Windows: commands fail before execution with “setup refresh had errors”On GitHub#52975
- [CLI Bug] Failed to create unified exec process: helper_unknown_error: setup refresh had errorsOn GitHub#52944
- Windows app 26.1007.2314.0: active 0.162.1 sandbox helper fails with error 32 / MAXIMUM_ALLOWED on CUA runtimeOn GitHub#52897
- Windows elevated sandbox startup blocked by 22-NUL-byte deny_read_acl_state.jsonOn GitHub#52859
- Codex workspace command runner fails to initialize with “setup refresh had errors”On GitHub#52772
- Windows sandbox fails with os error 32 on node_repl.exe before local shell executionOn GitHub#52757
- [Windows desktop] Sandbox setup refresh fails with sharing violation on app tools node.exe after browser/computer-use isolationOn GitHub#52740
- GPT-6 File Reader Not WorkingOn the forum#1404899
- Windows sandbox provisioning always fails: setup tries to ACL runtime binaries Codex itself is executing (os error 32)On GitHub#52735
- Windows browser control fails: sandbox setup error 32 on node_repl.exe, persists after rebootOn GitHub#52722
- Windows ARM64 sandbox provisioning fails with os error 32 (elevated and unelevated)On GitHub#52712
- Windows: elevated sandbox setup refresh errors block local tools after 26.1002 updateOn GitHub#52662
- Unable to read the contentOn GitHub#52657
- Windows dot local delegation: sandbox setup refresh keeps failingOn GitHub#52630
- Chrome automation fails on Windows before connecting to a healthy extensionOn GitHub#52626
- File Creation FailOn GitHub#52624
- Codex browser runtime failureOn GitHub#52617
- Windows sandbox fails on two workstations: node_repl.exe ACL validation os error 32; Full Access succeedsOn GitHub#52616
- Windows non-admin user: previously working Browser and shell fail with sandbox mutex and .sandbox-bin errorsOn GitHub#52614
- Windows: sandbox setup fails with os error 32 on node_repl.exe; browser and terminal tools unavailableOn GitHub#52611
- Windows sandbox: process creation fails with setup refresh had errors while full access worksOn GitHub#52606
- Windows elevated sandbox setup fails with os error 32 on CUA runtime filesOn GitHub#52601
- Windows Codex App 26.1002.52244: sandbox refresh fails on node_repl.exe with os error 32 after rebootOn GitHub#52595
- Persistent command-execution failure on connected Windows computerOn GitHub#52589
- Windows desktop sandbox ACL refresh fails on VCRUNTIME140_1.dll (os error 32); request supported recoveryOn GitHub#52586
- Windows sandbox fails before Get-Location: node_repl.exe sharing violation (error 32)On GitHub#52583
- Windows sandbox setup fails with OS error 32 when computer-use runtime files are in useOn GitHub#52572
- Windows desktop: sandbox runtime ACL validation sharing violation persists after update and reinstallOn GitHub#52571
- codex not workOn GitHub#52569
- Windows sandbox is permanently unusable: setup refresh races the app's own runtime helpers and always fails with ERROR_SHARING_VIOLATIONOn GitHub#52566
- Windows: local tools fail during sandbox setup with OS error 32 on node_repl.exeOn GitHub#52561
- Chat gpt showing errorOn GitHub#52558
- 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
- Windows sandbox setup blocks shell and Node tools; approved execution outside sandbox succeedsOn GitHub#52545
- Windows command execution fails with “helper_unknown_error: setup refresh had errors” despite connected computerOn GitHub#52541
- [Windows] Shell execution fails: helper_unknown_error: setup refresh had errorsOn GitHub#52538
- Windows IDE: browser helper groups persist across conversation resumes and block sandbox ACL refresh (node_repl.exe error 32)On GitHub#52537
- codex - unable to run local commandsOn GitHub#52526
- Has stopped being able to operate programs on my PC (but could do this 2 days ago)On GitHub#52525
- Windows elevated sandbox setup refresh fails with os error 32 in 0.162.0-alpha.2On GitHub#52518
- [Windows App] Sandbox setup refresh fails after updateOn GitHub#52514
- Windows elevated sandbox setup fails with error 32 on node_repl.exeOn GitHub#52506
- [Windows] Sandbox setup fails when Codex’s own node_repl.exe is running (os error 32)On GitHub#52504
- 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
- [Windows] Sandbox setup failure blocks local commands and file editing (helper_unknown_error / os error 32)On GitHub#52499
- Windows sandbox unusable: setup refresh fails with os error 32 (app-tools MCP holds the cua_node runtime exe)On GitHub#52488
- Windows sandbox failed: setup refresh had errorsOn GitHub#52482
- Windows sandbox failure caused repeated task failures and wasted usage quota — request for quota restorationOn GitHub#52481
- Windows Codex shell blocked by node_repl.exe sharing violation during sandbox setup (os error 32, Oct 9 repro)On GitHub#52476
- Windows desktop: terminal fails after update with helper_unknown_error: setup refresh had errorsOn GitHub#52467
- Codex Desktop Windows sandbox initialization fails with a locked node_repl.exeOn GitHub#52462
- [Windows] delegated tasks fail before shell startup with “setup refresh had errors”; logs report error 32 on node_repl.exeOn GitHub#52461
- Codex Windows Desktop – Shell fails to start: sandbox setup refresh / OS error 32On GitHub#52453
- no-active-thread-01a11f91-521e-7f61-a88f-2ea6b8627687On GitHub#52448
- Windows: local commands fail with "helper_unknown_error: setup refresh had errors"On GitHub#52445
- Windows desktop app: sandbox setup fails with OS error 32 on node_repl.exe, blocking browser and local commandsOn GitHub#52441
- Windows desktop: node_repl / Computer Use startup fails with sandbox setup refresh sharing violation (os error 32)On GitHub#52438
- “Windows sandbox: setup refresh had errors”On GitHub#52434
- Windows desktop 26.1002.52244: runtime ACL sharing violation persists after full shutdown and app repairOn GitHub#52433
- Windows Codex 26.1002.7124.0: elevated sandbox ACL refresh fails on running node_repl.exe (os error 32); process timelineOn GitHub#52432
- Windows elevated sandbox fails on live runtime ACL refresh; unelevated restores executionOn GitHub#52427