3 people reported
All time, since Oct 4, including 1 thumbs-up on GitHub.
MXC launcher startup failure
“MXC launcher: failed to create the process security environment: CreateProcessSecurityEnvironment failed (HRESULT = 0x80070002)”
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/11947/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
MXC launcher fails to start commands on Windows desktop app. Local commands and browser actions fail before starting with "failed to create the process security environment" and HRESULT 0x80070002, persisting after restart, repair and reinstall.
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 = 0x80070002)- Versions
- 26.930.3930.0
- Platforms
- Windows
- How bad
- Stops work: a core feature can't be used.
Part of: Browser/Computer Use runtime won't start8 bugs
- MXC launcher browser init failure38 people
- Browser control fails at startup with sandbox-exec TIOCSTI error19 people
- MXC sandbox startup failure11 people
- Browser control fails with trusted Node process exiting on Windows5 people
- Computer use initialization fails3 people
- Computer Use startup failure2 people
- Node REPL calls time out2 people
Not quite your bug?
- MXC startup fails with error 13266 people
- Sandbox setup refresh fails308 people