Last verified:
Codex Windows sandbox: fixing “setup refresh had errors” (os error 32)
On the Windows Codex app, builds released around Oct 7–9, 2026 (26.1002.52244, 26.1002.7124.0) can fail every command with setup refresh had errors or helper_unknown_error. The elevated sandbox can't update permissions on files Codex itself is using, so Windows returns os error 32 (sharing violation).
Update to 26.1007.21434 (reported fixed by a user). If you can't, switch to the unelevated sandbox as a temporary fallback.
Symptoms
- Shell commands fail before they start:
helper_unknown_error: setup refresh had errors. - Computer Use and browser control fail to initialize; Node REPL reports
trusted Node process exited unexpectedlyor times out. - The sandbox log in
%USERPROFILE%\.codex\.sandbox\showsopen ACL target for root-only update: The process cannot access the file because it is being used by another process. (os error 32), namingnode_repl.exeorVCRUNTIME140_1.dll.
Why it happens
During setup, the elevated sandbox validates and updates ACLs across Codex's runtime folder. Some of those files, such as node_repl.exe and VCRUNTIME140_1.dll, are already running or loaded, so Windows refuses to open them and setup aborts. This is the community diagnosis in #51601, #51590 and #52033, not an official root-cause statement.
How to fix it
Didn't help according to reports: restarting the app, rebooting alone, reinstalling, and disabling plugins.
Update the app to 26.1007.21434 or later
A user confirmed this build fixed the error. Check “About Codex” for your version.
Sign out, then reboot
Some users report that signing out of Codex, rebooting Windows, and signing back in cleared it.
Temporary: use the unelevated sandbox
Back up, then edit
%USERPROFILE%\.codex\config.tomland add (this key is in the official Windows sandbox docs):[windows] sandbox = "unelevated"Fully quit Codex (end leftover
node_repl.exe/node.exeprocesses in Task Manager) and reopen. This is temporary. OpenAI callsunelevateda legacy fallback with weaker network isolation and no denied read paths. Change it back toelevatedonce you're on a fixed build.
Not fully fixed everywhere: a user on CLI 0.162.1 still reported the error on Oct 15, 2026. Follow the issues below before assuming it's gone.
“Broken pipe (os error 32)” is a different problem
Despite the same error number, Broken pipe (os error 32) means a connection or output stream closed mid-session, for example a dropped network stream. It isn't the sandbox sharing violation. Retry the turn, check your network or VPN, and see the network section of the troubleshooting hub.
Sources
- openai/codex #51601: sandbox setup sharing violation (26.1002.51308)
- openai/codex #51590: node_repl.exe ACL update error 32; Computer Use and shell blocked
- openai/codex #52033: 26.1002.52244 node_repl.exe runtime validation error 32
- OpenAI Windows sandbox docs
FAQ
What does 'setup refresh had errors' mean in Codex on Windows?
The elevated Windows sandbox failed while updating file permissions (ACLs) on Codex's own runtime files, because files like node_repl.exe or VCRUNTIME140_1.dll were in use (os error 32). Every command fails before it starts.
Which Codex Windows versions have the os error 32 sandbox bug?
Reports from Oct 7–9, 2026 cite desktop builds 26.1002.52244 and 26.1002.7124.0 (and 26.1002.51308). A user reported 26.1007.21434 fixed it, but a CLI 0.162.1 user still hit it on Oct 15, so it is not confirmed fully fixed.
Does reinstalling Codex fix the sandbox error?
Users reported that restarting, reinstalling and disabling plugins did not help. Updating to 26.1007.21434 or signing out and rebooting did help some users.
Is it safe to set the Windows sandbox to unelevated?
It is an official legacy fallback, but OpenAI says it has weaker network isolation than elevated and does not support denied read paths. Use it only temporarily and if your organization's policy allows it, then switch back.
Is 'Broken pipe (os error 32)' the same problem?
No. Broken pipe means a connection or stream closed mid-session. It is a different problem from the sandbox sharing violation.
This is an independent, unofficial help site. It is not affiliated with or endorsed by OpenAI. Plans, limits and versions change; always check the official pages linked here.