›_ Codex Issues
Codex Issues / #35566

[Windows Desktop] Repeated GPU process crash (exitCode=101457950) after update, AppX breaks into NeedsRemediation state

Resolved 💬 4 comments Opened Jul 27, 2026 by 1Beyond1 Closed Aug 6, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Environment

  • App: OpenAI.Codex \26.721.4979.0\ x64 (Microsoft Store)
  • Windows: 10.0.26200 (Windows 11)
  • GPU: (user's GPU info from their machine, check dxdiag equivalent)
  • CLI: codex-cli 0.146.0-alpha.3.1

Symptoms

  1. Codex works for a while, then suddenly the GPU process crashes
  2. After the crash, Codex cannot be relaunched — clicking the icon does nothing
  3. AppX package status becomes \Modified, NeedsRemediation\
  4. The \codex://\ protocol handler becomes broken
  5. Re-registering (\Add-AppxPackage -Register\) and resetting (\Reset-AppxPackage\) from Windows Settings temporarily fix it, but the crash returns after some use

Logs (from \...\\LocalCache\\Local\\Codex\\Logs\)

Every crash ends with:

\\\
Recoverable Chromium child process gone
exitCode=101457950
name=null
processType=GPU
reason=crashed
serviceName=GPU

Recoverable Chromium child process gone
exitCode=18
name=null
processType=GPU
reason=launch-failed
serviceName=GPU
\\\

Before the GPU crash, the log shows many:
\\\
browser-sidebar-comment-mode-site-status failed to load
\\\
and occasional \ERR_CONNECTION_TIMED_OUT\ / \ERR_NETWORK_CHANGED\ on \/wham/usage\ and \/settings/user\.

After the GPU process fails to restart, Windows destroys the AppX container (Event ID 217) and the package moves to \NeedsRemediation\.

What was tried (none permanently fixed)

  • \wsreset.exe\ (Windows Store cache reset)
  • \Add-AppxPackage -Register ... -DisableDevelopmentMode\
  • \Reset-AppxPackage\
  • Store Settings → Reset / Repair
  • Full reinstall from Microsoft Store
  • Clearing \...\\LocalCache\\Local\\Codex\
  • Setting \ELECTRON_DISABLE_GPU=1\
  • Updating GPU drivers (failed)

Related issues

  • #35465 — same GPU exitCode 101457950 + AppX registration breakage
  • #32094 — same GPU exit code when in-app browser opens media pages (tracked as BRWPLAT-293)
  • #27828 — Cloudflare Turnstile GPU crash leads to unlaunchable app

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #35465

Powered by Codex Action

5y50541 · 1 month ago

Independent reproduction with the same Store build and exact GPU exit codes. This case broadens the trigger beyond media/WebCodecs or Cloudflare pages: an ordinary persisted Bing search tab in the in-app browser was enough to reproduce it.

Environment

  • Codex Windows Store app: 26.721.4979.0 x64
  • Bundled app-server/CLI: 0.146.0-alpha.3.1
  • NVIDIA GeForce GT 730, driver 30.0.14.7444 (2023-05-11)
  • Intel UHD Graphics 630, driver 27.20.100.9664 (2021-06-01)
  • Active Windows RDP session
  • Additional virtual display adapters present: GameViewer Virtual Display Adapter and OrayIddDriver, alongside Microsoft Remote Display Adapter
  • GameViewer, ToDesk, and Sunshine services/processes were also present. This may be relevant to adapter selection, but causality is not established.

Reproduction timeline

Reproduction 1

The app restored/created an in-app browser sidebar webview for a normal Bing search URL. The browser reached DOM ready, then the GPU process crashed:

2026-07-26T19:05:50.090Z IAB_LIFECYCLE renderer created browser sidebar webview
2026-07-26T19:05:58.314Z browser sidebar dom-ready
2026-07-26T19:06:06.454Z Recoverable Chromium child process gone exitCode=101457950 processType=GPU reason=crashed serviceName=GPU
2026-07-26T19:06:06.466Z Recoverable Chromium child process gone exitCode=18 processType=GPU reason=launch-failed serviceName=GPU

Windows destroyed the Desktop AppX container at local time 2026-07-27 03:06:07 (UTC+8), immediately after the GPU restart failure.

Reproduction 2

The same persisted browser tab and URL were automatically restored on the next affected launch:

2026-07-27T03:59:52.178Z IAB_LIFECYCLE renderer created browser sidebar webview
2026-07-27T04:00:05.206Z browser sidebar dom-ready
2026-07-27T04:00:09.907Z Recoverable Chromium child process gone exitCode=101457950 processType=GPU reason=crashed serviceName=GPU
2026-07-27T04:00:09.915Z Recoverable Chromium child process gone exitCode=18 processType=GPU reason=launch-failed serviceName=GPU

Windows destroyed the container at local time 2026-07-27 12:00:11 (UTC+8).

Startup loop / AppX behavior

After the browser-triggered termination, Codex repeatedly created a process but exited during very early initialization. The desktop logs for many launch attempts contained only Launching app and sometimes Appshot hotkey inactive; there was no standard Application Error event and no Crashpad report.

Microsoft Store reported NumberOfApplicableUpdates = 0 before repair. Windows then repaired/re-registered the same package version and logged:

Trying to repair ACLs for ...\WindowsApps\OpenAI.Codex_26.721.4979.0_x64__2p2nqsd0c76g0
ACLs repaired successfully

AppModel Runtime later changed the package status to 0x0 from 0x2. Repair/re-stage operations occurred repeatedly and only restored launchability temporarily.

The persisted in-app browser state appears important to the repeated crash-after-launch behavior: the same browser tab ID and Bing URL were restored before the second GPU crash. The low-level failure is strongly correlated with the Chromium GPU process, while the RDP/multiple-virtual-display environment may be an additional risk factor.

Only redacted excerpts are included; no conversation contents, local project paths, or credentials are attached.

neonglobe · 1 month ago

get codex crashes..
when it crashes i have to repair the install using the ms store.
i asked the agent to check the logs and report here is its anaylsis.

Four identical crashes occurred at 11:52:28, 11:55:29, 12:01:13, and 12:05:32 PM:
The in-app browser loaded dash.cloudflare.com.
The GPU process crashed with exit code 101457950.
GPU relaunch failed with exit code 18.
Chromium terminated with: GPU process isn't usable. Goodbye.
The crash telemetry also reported a locked DawnGraphiteCache file. Combined with the VMware/Remote Display graphics stack, this points to an embedded-browser hardware-acceleration/cache conflict. It was not an out-of-memory event or a Windows-wide graphics reset.

asully-oai · 22 days ago

this is likely a dup of #35352