21 people reported
All time, since Sep 25, including 14 thumbs-up on GitHub.
Background daemon fails at startup
“Error: Access is denied. (os error 5)”
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/themes/209/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
3 bugs in this theme
- "No complete local package" errorHas a workaround11 people
- Daemon access denied on WindowsHas a workaround7 people
- WinGet daemon fails to startHas a workaround3 people
What's included
- Windows WinGet install fails with "the CLI package does not match this platform or executable"
- Windows npm install fails with "Access is denied (os error 5)" or "failed to open daemon process"
- Arch Linux package or manually placed Windows binaries fail with "this CLI has no complete local package"
- Starts after upgrading to 0.157.x or later; running with --no-daemon works around it
Not included
- Extra terminal windows spawned per command on the npm build
- Failures that persist with --no-daemon
Original reports7, newest first
- Codex CLI v0.163.0 fails opening daemon process at launch on Windows 11 26H2, using Windows Terminal Powershell 7.6.7On GitHub#54569
- Windows WinGet package cannot start app-server daemon: "the CLI package does not match this platform or executable"On GitHub#51721
- Windows: background daemon still fails with "Access is denied (os error 5)" on Codex CLI 0.160.1On GitHub#51339
- Windows: Codex CLI 0.160.1 fails on normal startup with Access is denied (os error 5)On GitHub#51283
- Windows 10: "no complete local package" on 0.157.1/0.158.0On GitHub#48899
- Error: the CLI package does not match this platform or executableOn GitHub#48366
- Codex 0.157.0 no longer starts with the Arch Linux package unless --no-daemon is usedOn GitHub#48050