2 people reported
All time, since Oct 12.
Sandbox ACL refresh fails
“Sandbox setup cannot open workspace ACLs with READ_CONTROL | WRITE_DAC (os error 5: Access is denied).”
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/11926/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
Elevated Windows sandbox fails updating workspace ACL before commands run. Sandbox setup cannot open workspace ACLs with READ_CONTROL | WRITE_DAC (os error 5: Access is denied), so "setup refresh had errors" and no shell command executes.
Is this your bug?
File my report- Where
- Windows elevated sandbox
- Error text
Failed to create unified exec process: helper_unknown_error: setup refresh had errors- Versions
- 0.162.1 to 0.163.0
- Platforms
- Windows
- How bad
- Stops work: a core feature can't be used.
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
- Sandbox setup lock failure12 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
- 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