2 people reported
All time, since Sep 24.
Sandbox fails on Google Drive
“Windows sandbox initialization fails when a Codex desktop chat has a writable workspace on a Google Drive for desktop G: path.”
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/13529/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
Windows sandbox setup fails on Google Drive workspace paths. With sandbox = "elevated", ACE grants on G: Google Drive folders fail with error 87 before shell commands run.
Is this your bug?
File my report- Where
- Windows sandbox
- Error text
SetNamedSecurityInfoW failed: 87- Versions
- 0.155.0
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
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
- Sandbox ACL refresh fails2 people
Show all 17Show only the largest 10
- Managed networking sandbox error2 people
- Sandbox refresh fails on old runtime2 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