GitHub issue #25770 in openai/codex, opened 2026-06-02 by zyzhen, records a report that Codex Desktop from Microsoft Store repeatedly fails to update on Windows 10 Enterprise (version 10.0.19044, x64); that the update reaches the AppX/MSIX registration phase and then fails because Windows still considers the old `OpenAI.Codex` package/application to be in use, with AppXDeployment-Server failures including `0x80073CF9`, `0x8007001F` and `0x80073D02`; that this happened repeatedly on the same machine, and also on another machine in the same LAN; that closing visible Codex windows is not enough, since Windows still reports the old package/app as in use; and that the update succeeded only after manually quiescing the old package state and reinstalling from Microsoft Store. The report notes the failure appears to be in the Windows Store/MSIX update lifecycle around releasing the old package identity, rather than in normal application runtime behavior after the package is successfully installed. No root cause beyond the reporter's stated attribution is asserted.
Verbatim Excerpts from Cited Records
“Codex Desktop from Microsoft Store repeatedly fails to update on Windows. The update reaches the AppX/MSIX registration phase, then fails because Windows still considers the old `OpenAI.Codex` package/application to be in use.”
·
openai/codex (issue 25770 opening body, What issue are you seeing? section)
·
2026-06-02T04:39:24Z
·GitHub Issue ↗
“This has happened repeatedly on the same machine, and also on another machine in the same LAN.”
·
openai/codex (issue 25770 opening body, What issue are you seeing? section)
·
2026-06-02T04:39:24Z
·GitHub Issue ↗
“Closing visible Codex windows is not enough; Windows still reports the old package/app as in use.”
·
openai/codex (issue 25770 opening body, What steps can reproduce the bug? section)
·
2026-06-02T04:39:24Z
·GitHub Issue ↗
“The app/update flow repeatedly leaves the old package considered "in use", causing Store/AppX registration to fail. The user is forced into repeated manual repair, package unregister/reinstall, or reboot-like cleanup.”
·
openai/codex (issue 25770 opening body, Actual behavior section)
·
2026-06-02T04:39:24Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 23 comments were read. zyzhen (2026-06-17) reported the failure still happening on later updates. tolga-guldutuna (2026-08-15) added an independent reproduction on Windows 11 Enterprise 24H2 with a controlled success comparison. hanjie-chen (2026-09-02) confirmed the pattern on Windows 10 Pro with at least four occurrences. Disaer (2026-09-03) reproduced on two Windows 10 machines. Lang45 (2026-09-24) added a precise Stage/Register split and a recovery trap that re-registers the old version. tolga-guldutuna (2026-09-25) switched to a controlled manual-update workflow as an operational workaround, not a root-cause fix. SergeyPomelov (2026-09-25) reported a related severe consequence with 7,129 diagnostic files consuming 37.95 GB. RobiLiam (2026-09-26), g67rn4mwz7-glitch (2026-09-28), Phrolova0515 (2026-09-28), Earr22 (2026-09-30), evlst (2026-09-30), Tr1n1t4 (2026-10-01), post1917a (2026-10-02 and 2026-10-03), bakaxiaoxie (2026-10-02), deepanshu223 (2026-10-22), y614516676 (2026-10-26) and before-we-build (2026-10-29) added further independent reproductions, and andkondev (2026-11-12) reported the failure still happening as of 2026-11-11 on Windows 10 Pro 22H2. thisisntjon (2026-09-14) distinguished related issue #45511 as a different symptom. No maintainer fix and no retraction appear in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #25770 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.