WinGet daemon fails to start

“The official Codex CLI package installed via WinGet cannot start the app-server daemon on Windows.”

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

WinGet install cannot start app-server daemon on Windows. Running codex after installing or upgrading via WinGet fails to start the background server; --no-daemon still works.

Is this your bug?

File my report

Where: WinGet package
Error text: Error: the CLI package does not match this platform or executablePasted in 2 reports
Versions: 0.157.1 to 0.160.1
Platforms: Windows
How bad: Breaks a normal workflow.

Part of: Background daemon fails at startup3 bugs

Daemon access denied on Windows7 people
"No complete local package" error11 people

Not quite your bug?

Windows daemon privilege startup error46 people

Original reports2, newest first

Oct 7, 2026Windows WinGet package cannot start app-server daemon: "the CLI package does not match this platform or executable"On GitHub#51721
Sep 26, 2026Error: the CLI package does not match this platform or executableOn GitHub#48366