Its theme's rank, 14 days: 23 on the Codex sheet
12 people reported
All time, since Sep 15, including 3 thumbs-up on GitHub.
Sandbox setup lock failure
“Codex for Windows repeatedly displays "Finish Windows setup to continue" and fails to initialize its elevated sandbox.”
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/14218/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
Windows sandbox setup fails locking .sandbox-bin with access denied. Setup stops with helper_sandbox_lock_failed and Windows error 5 when opening %USERPROFILE%\.codex\.sandbox-bin, so the app keeps asking to finish Windows setup.
Is this your bug?
File my report- Where
- Windows sandbox setup
- Error text
setup error: helper_sandbox_lock_failed: lock sandbox bin dir \\?\C:\Users\<user>\.codex\.sandbox-bin failed: open directory ... NtCreateFile: Access is denied. (os error 5)NtCreateFile: Access is denied. (os error 5)Pasted in 2 reports- Versions
- 26.908.9136.0 to 26.1027.3384.0
- 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
- Sandbox setup refresh fails308 people
- Sandbox fails at deny-read ACLs10 people
- Setup refresh error blocks commands23 people
- Split writable root sandbox failure3 people
- Sandbox fails on WSL UNC paths4 people
- Windows sandbox setup fails validating long cua_node runtime paths11 people
- Windows setup stops without UAC3 people
- Sandbox ACL update failure2 people
- Sandbox ACL refresh fails2 people
- Managed networking sandbox error2 people
Show all 17Show only the largest 10
- Sandbox refresh fails on old runtime2 people
- Sandbox fails on Google Drive2 people
- Sandbox provisioning failed2 people
- Windows sandbox provisioning fails3 people
- Windows sandbox setup access denied2 people
- Root read access sandbox error12 people
- Shell and Node tools fail with MXC 0x80070020 on Windows2 people
Original reports10, 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 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
- 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 sandbox: recurring helper_sandbox_lock_failed after .sandbox-bin permissions return to ModifyOn GitHub#50520
- Windows Sandbox setup fails with helper_sandbox_lock_failed / SetNamedSecurityInfoW failed: 5On GitHub#45734