ChatGPT/Codex App 26.715.4045.0 exits silently seconds after launch after a clean reset; Beta works #34277

What version of the Codex App are you using (From “About Codex” dialog)?

Microsoft Store package: OpenAI.Codex 26.715.4045.0 x64 Internal desktop release from logs: 26.715.31925 (prod) Bundled app-server: 0.145.0-alpha.18 The About dialog is unavailable because the app exits seconds after launch.

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The production Microsoft Store app starts, briefly creates its main window, and then the entire AppX process tree disappears about 6 seconds after activation. No error dialog is shown.

Upgrade history and how I reached this state:

1. The problem originally started on the previous production package, OpenAI.Codex 26.707.9981.0. That version produced repeated Windows Application Error Event ID 1000 entries with exception 0xc06d007f, associated with the bundled serialport.node native module. The production app became unusable because it repeatedly crashed or closed.
2. I installed and switched to the Codex Beta package as a workaround. Beta remained usable on the same Windows installation and account.
3. After [Windows App] Repeated serialport.node delay-load failures cause severe UI lag #33375 was closed as completed on July 17, 2026, I installed the latest production ChatGPT/Codex Store package, OpenAI.Codex 26.715.4045.0, expecting the original native-module defect to be fixed.
4. The latest production package no longer contains serialport.node, and the old Event ID 1000 / 0xc06d007f failures stopped. However, the production app still cannot be used: it now initializes successfully and then exits silently after approximately 6–10 seconds.
5. Beta 26.715.3651.0 continues to work, while production 26.715.4045.0 consistently exits on the same machine.

Therefore, the latest package appears to have fixed the original #33375 failure mechanism, but it has not restored production-app usability on this system. The current silent-exit behavior is a distinct post-update failure rather than another observed serialport.node exception.

This is consistently reproducible with:

• Store package OpenAI.Codex_26.715.4045.0_x64__2p2nqsd0c76g0
• Internal desktop release 26.715.31925 (buildFlavor=prod)
• Windows 11 Pro, build 26200, x64

The app gets well past early Electron startup:

• the packaged app-server is spawned;
• the initialization handshake succeeds;
• the main frame finishes loading;
• the window reaches ready-to-show;
• React routes mount and logs report rendererWindowVisible=true;
• the in-app browser backend reports ready;
• the log then ends abruptly after otherwise successful requests.

Windows AppModel Runtime shows the package container being created at 15:00:25 and destroyed at 15:00:31. There is no corresponding Application Error event, WER event, Defender/Code Integrity/AppLocker block, or Crashpad/LocalDumps dump.

The separately installed Beta package (OpenAI.CodexBeta 26.715.3651.0) works normally on the same machine.

This does not appear to be the previously reported serialport.node / 0xc06d007f issue in #33375:

• the current production package contains no serialport.node file;
• no new Event ID 1000 / 0xc06d007f event is generated;
• the current failure is a silent full-process exit after the renderer is visible.

What steps can reproduce the bug?

1. Install or update the production app from Microsoft Store to OpenAI.Codex 26.715.4045.0 on Windows 11 x64.

2. Fully terminate all production app processes. A Windows restart and launching production before Beta produces the same result.

3. Launch the production app from Start, or activate it with:

   Start-Process explorer.exe 'shell:AppsFolder\OpenAI.Codex_2p2nqsd0c76g0!App'

4. Observe that the process tree starts and the window is initialized, but all production processes disappear after approximately 6–10 seconds.

5. Reset only the production package and retry:

   Get-AppxPackage -Name OpenAI.Codex | Reset-AppxPackage

6. Confirm that the issue remains reproducible from a completely empty production AppX state. In my clean-reset test, the process count was 5 after 1 second, 8 after 3–5 seconds, and 0 after 10 seconds.

What is the expected behavior?

The production app should remain running and display an interactive main window after its app-server, renderer, and routes initialize successfully. It should not silently terminate the complete AppX process tree without an error or crash report.

Additional information

Troubleshooting already completed:

• Initially reproduced the older 26.707.9981.0 production crash and used Codex Beta as the working fallback.
• Updated to the latest production ChatGPT/Codex package after [Windows App] Repeated serialport.node delay-load failures cause severe UI lag #33375 was marked completed; production still exits, although the old serialport.node exception is gone.
• Windows Settings: Terminate → Repair → restart Windows → launch production first: no change.
• Backed up and then reset only OpenAI.Codex; verified the package state was empty before relaunch: no change.
• Package status after reset: Ok.
• Disabled GPU and GPU compositing: no change.
• Checked Windows Application, Defender, Code Integrity, AppLocker, AppModel Runtime, and crash dump locations.
• No Application Error Event ID 1000, WER crash event, security-policy block, or dump is generated for the clean-reset reproduction.
• The clean-reset log contains only two warnings, both saying an IPC broadcast had no configured handler; no fatal/error/shutdown record precedes termination.
• Production executable SHA-256:
  305B25FA057C35241C2C27BCB1112450F35EEE12C1D4B1E4D74C073454914346

Clean-reset timeline (UTC):

07:00:25.538 Launching app (prod, packaged, win32)
07:00:26.384 packaged app-server spawned
07:00:26.715 initialize handshake outcome=success
07:00:26.870 main frame finished load
07:00:26.896 window ready-to-show
07:00:30.601 app routes mounted; rendererWindowVisible=true
07:00:30.790 in-app browser backend startup ready
07:00:31.101 last log line: successful account/read response
07:00:31.xxx AppX container destroyed

Potentially related silent-exit report: #22633. However, this reproduction reaches a visible, initialized renderer and generates normal desktop logs before the process tree disappears.

A sanitized diagnostic excerpt is attached. Raw logs are not attached because they may contain local paths, request IDs, and session metadata.