Forumics logo Forumics
Issue 01

Back to issue

All Codex known issues

CLAIM C113 Supported 2026-11-13

GitHub issue #50520 in openai/codex, opened 2026-10-03 by gwdonnor, records a report that the native Windows sandbox repeatedly fails before shell commands start with `helper_sandbox_lock_failed` when opening the `.codex\.sandbox-bin` directory, that granting SYSTEM and Administrators Full Control on that directory and retrying Windows setup restores sandbox access but the problem later recurs with the ACL entries again at Modify, that this is an observed recurrence with a successful workaround and not a confirmed diagnosis of which component resets the ACL, and that the report was observed October 1-2, 2026 with command-runner 0.160.0 in workspace-write filesystem mode, with no root cause asserted.

Verbatim Excerpts from Cited Records
“The native Windows sandbox repeatedly fails before shell commands start with `helper_sandbox_lock_failed` when opening `%USERPROFILE%\.codex\.sandbox-bin`.”
— gwdonnor · openai/codex (issue 50520 opening body, Summary section) · 2026-10-03T04:40:49Z ·GitHub Issue ↗
“Granting SYSTEM and Administrators Full Control on that directory and retrying Windows setup restores sandbox access, but the problem later recurred and the ACL entries were again Modify.”
— gwdonnor · openai/codex (issue 50520 opening body, Summary section) · 2026-10-03T04:40:49Z ·GitHub Issue ↗
“This is an observed recurrence with a successful workaround, not a confirmed diagnosis of which component resets the ACL.”
— gwdonnor · openai/codex (issue 50520 opening body, Summary section) · 2026-10-03T04:40:49Z ·GitHub Issue ↗
“Sandbox provisioning should succeed with the permissions established by its own setup process.”
— gwdonnor · openai/codex (issue 50520 opening body, Expected behavior section) · 2026-10-03T04:40:49Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 22 comments were read. github-actions[bot] (2026-10-03) flags potential duplicates #49299 and #49677. Reynellmds (2026-10-04) independently reproduces and traces the cause to the LocalSystem provisioning service opening the directory with READ_CONTROL | WRITE_DAC. StarLit12 (2026-10-04), cheerynik (2026-10-04), alanwang1818 (2026-10-09), and others confirm the same failure across Windows 10 and 11 and multiple desktop builds. spidikor (2026-10-04) and cheerynik (2026-10-05) report workarounds reapplying WRITE_DAC or changing the directory owner to SYSTEM. dragon940111-bot (2026-10-06), cervinho (2026-11-03), and jarrod-wright (2026-11-07) report the `takeown /A` ownership workaround holding across re-provisionings. Reproductions continue into November: kaimorih (2026-11-06), xrick435-alt (2026-11-08), M-T-D-N (2026-11-08), dgoulard93 (2026-11-12), and Bienveniedos (2026-11-12) on desktop 26.1106.6628.0. No maintainer fix and no retraction of the report appear in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #50520 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.

See also: Codex vs Cursor head-to-head comparison on 9bests