Windows: shell commands fail with helper_sandbox_lock_failed (error 5)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.908.40834
What subscription do you have?
Plus
What platform is your computer?
windows
What issue are you seeing?
All local shell commands fail before execution, including read-only commands.
Error:
helper_sandbox_lock_failed
lock sandbox bin dir C:/Users//.codex/.sandbox-bin failed
SetNamedSecurityInfoW sandbox dir failed: 5
Sandbox setting: workspace-write.
The built-in dependency diagnostic reports that Codex dependencies are healthy. The displayed dependency bundle version is 26.909.12148.
The affected directory is owned by BUILTIN\Administrators. The reported permissions are:
- SYSTEM: Modify, Synchronize
- Administrators: Modify, Synchronize
- Current user: Modify, Synchronize
- CodexSandboxUsers: ReadAndExecute, Synchronize
The sandbox.log file was not found at the default .codex/.sandbox/sandbox.log location.
Expected: local commands should start within the permitted workspace.
Actual: every command fails during sandbox initialization.
Feedback ID: 01a08b52-fc41-7b61-a2f9-45373dced88f
What steps can reproduce the bug?
Feedback ID: 01a08b52-fc41-7b61-a2f9-45373dced88f
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure on Windows and running the built-in dependency diagnostic. Inspect sandbox initialization around C:/Users//.codex/.sandbox-bin and check whether .codex/.sandbox/sandbox.log is generated. Done means read-only and write shell commands start successfully within the permitted workspace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100