Its theme's rank, 14 days: 23 on the Codex sheet
2 people reported
All time, since Oct 22.
Shell and Node tools fail with MXC 0x80070020 on Windows
“Local shell commands and the Node tool kernel consistently fail before the requested command runs.”
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/24358/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
Local commands exit with code 1 before running, and the Node kernel exits with stdout_eof; a restart of Windows did not clear it.
Is this your bug?
File my report- Where
- Windows desktop app
- Error text
MXC launcher: failed to create the process security environment: CreateProcessSecurityEnvironment failed (HRESULT = 0x80070020)- Versions
- 26.1016.61520
- 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
- 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 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
Not quite your bug?
- MXC sandbox startup failure11 people
- MXC launcher startup failure3 people