Its theme's rank, 14 days: 102 on the Codex sheet
6 people reported
All time, since Oct 7, including 3 thumbs-up on GitHub.
In-app update fails to register
“The newer package is successfully downloaded/staged, but registration fails because Windows still considers the old application to be running.”
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/13541/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
Windows in-app update fails to register because Codex still running. The newer package is staged, but registration fails with 0x800700E9 because Windows considers the old app still running, so the update indicator returns.
Is this your bug?
File my report- Where
- Windows desktop app updater
- Versions
- 26.1016.61520 to 26.1023.50603
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Part of: Windows app updates break Codex5 bugs
- Startup rename_staging EPERM5 people
- Code-mode host not found3 people
- Auth fails after codex.exe moves5 people
- Windows app won't launch or stays on old version3 people
Not quite your bug?
- No window on launch3 people
- Crash in windows-updater.node10 people
Original reports3, newest first
- Subject: Windows in-app updates repeatedly fail; Microsoft Store “Retry” succeedsOn GitHub#57611
- [Windows 10][26.1016.61520] In-app update loop: staged MSIX fails to register because Codex is still runningOn GitHub#56428
- [Windows] Repeated in-app update failure after successful staging: 0x800700E9 / app still running (target 26.1002.6548.0)On GitHub#51588