6 people reported
All time, since Sep 19, including 3 thumbs-up on GitHub.
Runtime checksum mismatch
“The download completes, but Codex rejects it during checksum verification.”
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/16152/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
Primary runtime 26.915.20218 install fails with checksum mismatch. The downloaded archive's SHA-256 does not match the app's expected hash, and the scheduled updater redownloads it hourly on Windows and macOS.
Is this your bug?
File my report- Where
- runtime updater
- Error text
errorCategory=checksum_mismatch- Versions
- 26.915.20218 to 26.915.31945
- Platforms
- macOS, Windows
- How bad
- Stops work: a core feature can't be used. Some reports say it used to work.
Not quite your bug?
- Startup rename_staging EPERM5 people
- Older runtime bundle selected2 people
- Runtime install loop2 people
Original reports3, newest first
- Codex desktop (9922 / 26.915.31945): primary-runtime 26.915.20218 fails with permanent checksum_mismatch — published archive hash ≠ manifestOn GitHub#46933
- [Windows][Desktop 26.915.4065.0] Runtime updater redownloads a 495 MB archive hourly on two independent PCsOn GitHub#46768
- Windows: Codex dependencies runtime 26.915.20218 fails to install due to SHA-256 checksum mismatchOn GitHub#46699