openai / openai/codex

[Windows] Codex desktop updater repeatedly fails with 0x80190194

Open
#38,758 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug windows-os
Dominant language
Rust
Stars
125k
Forks
19.5k
PR merge metrics
PR metrics pending

Description

What happened?

The Windows Codex desktop app repeatedly detects an update but cannot install it. The same failure returns on each retry, and it has recurred across more than one release.

Environment
  • OS: Windows 10 Enterprise 25H2, x64 (build 26200.9168)
  • Package: OpenAI.Codex (Microsoft Store/MSIX app)
  • Installed version: 26.803.10989.0
  • Update target observed: 26.810.7004.0
Steps to reproduce
  1. Install the Windows desktop app from the official Microsoft Store listing.
  2. Launch Codex and leave it running.
  3. Let the app detect a newer package.
  4. Start the update and retry after it fails.
Expected behavior

The update should download and install successfully, or the app should fall back to a supported Microsoft Store installation/update path and present a clear recovery action.

Actual behavior

The app reports that it is unable to install the ChatGPT/Codex update. The updater log repeatedly records an HTTP/MSIX staging failure:

[windows-store-updater] ... buildVersion=26.803.10989.0 manifestBuildVersion=26.810.7004.0 packageIdentity=OpenAI.Codex
[windows-store-updater] ... hasUpdate=true ... overallState=SilentDownloadNotAllowed
[windows-updater] Failed to install prepared Windows update ... 0x80190194

The staged manifest currently contains the package URL but no length or SHA-256 metadata:

{
  "buildVersion": "26.810.7004.0",
  "length": null,
  "packagePath": "https://persistent.oaistatic.com/codex-app-prod/releases/26.810.7004.0/ChatGPT-x64.msix",
  "sha256": null
}

The same 0x80190194 failure occurred during an earlier update cycle as well.

What I checked
  • Microsoft Store/AppX-related services (AppXSvc, ClipSVC, DoSvc, and InstallService) were running.
  • Microsoft Store automatic-download policy was enabled (AutoDownload=2).
  • The official Store product ID was recognized by winget, but it did not offer a newer package at the time of testing.
  • No app data, project files, or .codex state was deleted.
Workaround

Using the Microsoft-signed Store Installer from the official OpenAI Windows app documentation and choosing Update successfully moved the app from an older package version to 26.803.10989.0. The next update then failed again with the same updater error.

Possible root cause

The Windows updater appears to receive a staged update manifest whose package metadata is incomplete, then fails while the MSIX staging session reads the manifest and marks the update as SilentDownloadNotAllowed even though Store auto-download is enabled. The 0x80190194 error may indicate a missing/unavailable resource in the updater/CDN or a mismatch between the app's update manifest and the Store package metadata.

Related Windows updater reports include #25770, #24010, and #35366, but I could not find an existing open issue for this exact 0x80190194 / SilentDownloadNotAllowed combination.

I can provide additional sanitized log excerpts and timestamps if maintainers need them.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the windows-store-updater and windows-updater paths that emit the reported manifest and installation log messages, then trace how the package URL, missing metadata, and SilentDownloadNotAllowed state are handled. Reproduce the update from 26.803.10989.0 to 26.810.7004.0 and verify that the package installs successfully or that a supported recovery path is presented.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.