Windows desktop app crashes on launch in windows-updater.node

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

26.608.12217

What subscription do you have?

business

What platform is your computer?

Windows 11 Pro 10.0.26200 Build 26200, x64

What issue are you seeing?

The Windows Codex desktop app crashes immediately on launch.

Installed package:

- Package: OpenAI.Codex
- Version: 26.608.1337.0
- PackageFullName: OpenAI.Codex_26.608.1337.0_x64__2p2nqsd0c76g0
- InstallLocation: C:\Program Files\WindowsApps\OpenAI.Codex_26.608.1337.0_x64__2p2nqsd0c76g0
- Package status: Ok

Launch behavior:

- Starting the app from Start Menu or `shell:AppsFolder\OpenAI.Codex_2p2nqsd0c76g0!App` creates a process.
- The process exits after about 1-2 seconds.
- No usable desktop window remains.
- Running as Administrator does not fix it.

Logs only show

Launching app ... buildFlavor=prod enableSparkle=false enableUpdater=true packaged=true platform=win32
Appshot hotkey inactive configured=true enabled=true platform=win32
Every launch creates a Crashpad dump.
Minidump analysis:
Exception code: 0xe06d7363
Exception address: KERNELBASE.dll
Crashing stack/module references: windows-updater.node
Observed offsets include:
windows-updater.node + 0xf83e0
windows-updater.node + 0xdb648
windows-updater.node + 0xdb390
This looks like a native Windows updater crash during startup, not a CLI issue, permission issue, or GPU issue.

### What steps can reproduce the bug?

```markdown
1. Install/Open the Windows Codex desktop app.
2. Launch it from Start Menu, or run:

Start-Process 'shell:AppsFolder\OpenAI.Codex_2p2nqsd0c76g0!App'
Wait 1-2 seconds.
The app exits before a usable window appears.
A Crashpad dump is created under:
C:\Users\<user>\AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Roaming\Codex\web\Codex\Crashpad\reports
Workaround found:
Running a copied, unpackaged app directory from D:\Codex-Desktop\codex-desktop-local\app\Codex.exe avoids the fatal startup crash. In that mode updater setup logs an error about missing process package identity, but the app continues and reaches window ready-to-show.
Expected behavior:
The desktop app should open normally. If updater initialization fails, it should fail gracefully and not terminate the app.
Actual behavior:
The packaged Windows app crashes immediately during startup, apparently inside windows-updater.node.

What is the expected behavior?

_No response_

Additional information

_No response_