Auth fails after codex.exe moves

“Codex Desktop on Windows silently replaces runtime executable, causing firewall block and misleading 401 API-key error”

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/14518/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 4 a week at the late-September peak. A workaround is known.

Auth fails after updates create new codex.exe runtime. Windows desktop updates place codex.exe in a new hash-named directory, so existing path-based firewall exceptions no longer cover it.

Is this your bug?

File my report

Where: Windows desktop app
Error text: token_exchange_failed: error sending request for url (https://auth.openai.com/oauth/token)
Versions: 26.924.1866.0 to 26.924.2738.0
Platforms: Windows
How bad: Breaks a normal workflow. Most reports say it used to work.

Part of: Windows app updates break Codex5 bugs

Startup rename_staging EPERM5 people
In-app update fails to register6 people
Code-mode host not found3 people
Windows app won't launch or stays on old version3 people

Not quite your bug?

Stale CODEX_CLI_PATH backend hang2 people
Stuck on startup splash7 people

Original reports3, newest first

Oct 1, 2026Windows desktop updates change codex.exe path, breaking persistent TinyWall exceptions and OAuth loginOn GitHub#50022
Sep 26, 2026[Windows] New Codex runtimes are classified as Low Restricted by Kaspersky, causing token_exchange_failedOn GitHub#48441
Sep 25, 2026Codex Desktop on Windows silently replaces runtime executable, causing firewall block and misleading 401 API-key errorOn GitHub#48316