Rank, 14 days: 102 on the Codex sheet
22 people reported
All time, since Sep 14, including 5 thumbs-up on GitHub.
Windows app updates break Codex
“The relocation repeatedly fails at the rename_staging operation with Windows EPERM.”
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/192/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
5 bugs in this theme
- In-app update fails to registerHas a workaround6 people
- Startup rename_staging EPERMNo workaround yet5 people
- Auth fails after codex.exe movesHas a workaround5 people
- Code-mode host not foundHas a workaround3 people
- Windows app won't launch or stays on old versionNo workaround yet3 people
What's included
- In-app update stages the new package but registration fails with 0x800700E9 or 0x80073D28; the old version stays or the app no longer launches
- Startup fails with "Unable to locate the Codex CLI binary" after rename_staging EPERM while relocating bundled executables
- Tools fail with os error 2 because codex-code-mode-host.exe is looked up in an old or parent bin directory after an update
- New hash-named codex.exe path after an update is blocked by Malwarebytes, Kaspersky or TinyWall, showing 401 or token_exchange_failed at sign-in
Not included
- Codex on Windows failing to start or sign in with no app update or runtime change involved
- Sandbox or tool failures on macOS or Linux
Original reports17, newest first
- Subject: Windows in-app updates repeatedly fail; Microsoft Store “Retry” succeedsOn GitHub#57611
- [Windows] Codex cannot load organization settings (Unable to load organization settings): codex.exe deployment rename_staging / EPERMOn GitHub#57005
- [Windows 10][26.1016.61520] In-app update loop: staged MSIX fails to register because Codex is still runningOn GitHub#56428
- Windows Store app: code-mode host resolved from wrong directory, blocking local toolsOn GitHub#54698
- [Windows] Repeated in-app update failure after successful staging: 0x800700E9 / app still running (target 26.1002.6548.0)On GitHub#51588
- Codex Tools DeleteOn GitHub#51262
- Windows desktop updates change codex.exe path, breaking persistent TinyWall exceptions and OAuth loginOn GitHub#50022
- [Windows] New Codex runtimes are classified as Low Restricted by Kaspersky, causing token_exchange_failedOn GitHub#48441
- Codex Desktop on Windows silently replaces runtime executable, causing firewall block and misleading 401 API-key errorOn GitHub#48316
- [Windows] End-to-end workaround: rename_staging EPERM -> sandbox helper missing -> code-mode host missing with CODEX_CLI_PATHOn GitHub#47759
Show all 17Show only the newest 10
- Windows: stale codex-code-mode-host.exe path after app updates causes tool failuresOn GitHub#47432
- [Windows] 26.915.4065.0: rename_staging EPERM leaves Browser / Chrome / Computer Use without node_replOn GitHub#46748
- [Windows][26.915.4065.0] Store auto-update deregisters old version, fails to register new one (0x80073D28, packaged sandbox service) — app becomes silently unlaunchableOn GitHub#46628
- [Windows 10][26.903.8094.0] Stable ChatGPT/Codex does not launch at all, while Beta worksOn GitHub#46611
- [Windows][26.915.3509.0] In-app updater stages package but leaves old version registered after LocalSystem sandbox service was addedOn GitHub#46370
- [Windows] Startup fails after a Store update with rename_staging EPERM for CLI and Node runtimeOn GitHub#45858
- [Windows] Desktop startup repeatedly fails with EPERM during bundled executable rename_staging; succeeds after ProcMon changes timingOn GitHub#45593