46 people reported
All time, since Sep 25, including 45 thumbs-up on GitHub.
Windows daemon privilege startup error
“Codex CLI 0.157.0 fails to start and displays an error about launching the Windows daemon from a non-elevated terminal.”
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/15601/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
CLI fails to start on Windows with daemon privilege error. Launching codex from an elevated terminal shows an error that the daemon must start non-elevated and suggests rerunning with --no-daemon.
Is this your bug?
File my report- Where
- Windows CLI
- Error text
Error: start the Windows daemon from a non-elevated terminal; shared clients must not inherit administrator privileges- Versions
- 0.157.0
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Related: Background daemon fails at startup
Not quite your bug?
- Daemon access denied on Windows7 people
- WinGet daemon fails to start3 people
- "No complete local package" error11 people
Original reports1, newest first
- Codex CLI 0.157.0 fails to start on Windows with daemon privilege error (0.156.1 works)On GitHub#48043