Daemon access denied on Windows

“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/issues/13686/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

Quiet. No reports and thumbs-up in the last two weeks, down from 5 a week at the early-October peak. A workaround is known.

Background daemon fails to start on Windows with os error 5. Plain codex exits immediately at launch in PowerShell; the CLI works when run with --no-daemon.

Is this your bug?

File my report

Where: background daemon
Error text: Error: Access is denied. (os error 5)Pasted in 2 reports
Versions: 0.160.1 to 0.163.0
Platforms: Windows
How bad: Breaks a normal workflow.

Part of: Background daemon fails at startup3 bugs

WinGet daemon fails to start3 people
"No complete local package" error11 people

Not quite your bug?

Windows daemon privilege startup error46 people
Git console error windows4 people

Original reports3, newest first

Oct 16, 2026Codex CLI v0.163.0 fails opening daemon process at launch on Windows 11 26H2, using Windows Terminal Powershell 7.6.7On GitHub#54569
Oct 6, 2026Windows: background daemon still fails with "Access is denied (os error 5)" on Codex CLI 0.160.1On GitHub#51339
Oct 6, 2026Windows: Codex CLI 0.160.1 fails on normal startup with Access is denied (os error 5)On GitHub#51283