Rank, 14 days: 133 on the Codex sheet
2 people reported

All time, since Oct 26.

Session fails: missing SYSTEMROOT

“MXC launcher: The supplied process.env cannot launch a Windows process container because it is missing the required variable(s): SYSTEMROOT.”

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/21565/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

Session creation fails with missing SYSTEMROOT in MXC launcher on Windows. Fails while loading AGENTS.md instructions for environment local; the fs sandbox helper exits with code 1 and the supplied process.env lacks SYSTEMROOT.

Is this your bug?

File my report
Where
fs sandbox helper
Error text
MXC launcher: The supplied `process.env` cannot launch a Windows process container because it is missing the required variable(s): SYSTEMROOT.
Versions
0.164.0
Platforms
Windows
How bad
Stops work: a core feature can't be used.

Related: WSL agent cannot run commands

Not quite your bug?

  1. Sandbox setup refresh fails308 people
  2. MXC launcher startup failure3 people
  3. Root read access sandbox error12 people

Original reports2, newest first

  1. Explicit filesystem deny rule causes session initialization to fail with missing SYSTEMROOTOn GitHub#59152
  2. [Windows] Cannot create or resume local threads: MXC filesystem helper is missing SYSTEMROOT (related to #56264)On GitHub#57082

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.