Windows: sandbox initialization fails with sharing violation (os error 32) after update
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
Research direction
The payload names no source files. Its concrete leads are node_repl.exe, the ACL update during sandbox setup, and the sandbox self-test, which reportedly passes once the app is fully closed. Start by finding where the sandbox setup refresh validates runtime read/execute permissions and applies ACLs, then reproduce the os error 32 sharing violation on Windows with the app running. Done means setup succeeds while the app is running, with a regression test if one is feasible.
Written by the indexing model from the issue text.
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.1002.52244 (build 13536)
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
Environment
- Windows desktop package: OpenAI.Codex_26.1002.7124.0
- Runtime version changed from 0.160.1 to 0.162.0-alpha.2
Problem
After the update, sandbox initialization started failing with:
helper_unknown_error: setup refresh had errors
The logs show a failure while validating runtime read/execute permissions and updating the ACL for node_repl.exe. Windows reports a sharing violation (os error 32: the file is being used by another process).
Observed behavior
- The standalone sandbox self-test succeeds after fully exiting the Codex app.
- The problem returns after reopening the app.
- Using the Windows app Repair option did not resolve the issue.
- The failure prevents sandboxed commands from starting.
Expected behavior
Sandbox initialization should succeed while the Codex app is running.
Request
Could you confirm whether this is a known regression or a runtime file-locking issue?
Please provide a supported fix or workaround. If a rollback is required, please provide an official Windows installation source and rollback instructions.
Feedback / Session ID: 01a11938-9188-7670-8b19-7a09e6f22ebe
What steps can reproduce the bug?
Environment
- Windows desktop package: OpenAI.Codex_26.1002.7124.0
- Runtime version changed from 0.160.1 to 0.162.0-alpha.2
Problem
After the update, sandbox initialization started failing with:
helper_unknown_error: setup refresh had errors
The logs show a failure while validating runtime read/execute permissions and updating the ACL for node_repl.exe. Windows reports a sharing violation (os error 32: the file is being used by another process).
Observed behavior
- The standalone sandbox self-test succeeds after fully exiting the Codex app.
- The problem returns after reopening the app.
- Using the Windows app Repair option did not resolve the issue.
- The failure prevents sandboxed commands from starting.
Expected behavior
Sandbox initialization should succeed while the Codex app is running.
Request
Could you confirm whether this is a known regression or a runtime file-locking issue?
Please provide a supported fix or workaround. If a rollback is required, please provide an official Windows installation source and rollback instructions.
Feedback / Session ID: 01a11938-9188-7670-8b19-7a09e6f22ebe
What is the expected behavior?
No response
Additional information
No response
- Dominant language
- Rust
- Stars
- 129k
- Forks
- 20.3k
- Avg merge
- 1m
- Merged PRs (30d)
- 998
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from openai/codex
-
Python SDK: CodexClient.close() leaves the app-server's stdout/stderr pipes open (and never waits after kill)Possibly taken @akhil9tiet claimed this 1 day ago. Openapp-server bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openai/codex#54908 · 2 comments ·
Maintainers usually reply within 1 day
-
bug CLI tool-calls windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug tool-calls
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Clarification about NODE_REPL_TRUSTED_BROWSER_CLIENT_SHA256S in the VS Code extension environmentOpendocumentation extension windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
openai/codex#54780 · 1 comment ·
Maintainers usually reply within 1 day
-
bug context
Difficulty 2/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
521xueweihan/HelloGitHub#4023 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cloudflare/pingora#1055 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day