## Summary The Codex desktop app on Windows ARM64 crash-loops: the window appea…rs, runs for ~10–15 seconds, then the whole app exits. No error dialog, no Windows Application Error event — but Crashpad writes a minidump on every launch. Reinstalling (including wiping all `LocalCache` app data) does not help; a fresh install crashes on first launch. Symptoms match #27574, but I was able to root-cause it from the minidump on my machine. ## Environment - Device: Surface, Windows 11 on ARM64 (Snapdragon / Qualcomm Adreno GPU), OS build 10.0.26200 - App: `OpenAI.Codex` MSIX from Microsoft Store, version **26.707.9981.0, arm64** (`OpenAI.Codex_26.707.9981.0_arm64__2p2nqsd0c76g0`) - Crashing process: Electron main process (`ptype=browser` in the Crashpad annotations) ## Root cause (from minidump analysis) Exception code is **`0xC06D007F`** — the VC++ delay-load helper's "procedure not found" exception, raised from `KERNELBASE!RaiseException`. Parsing the `DelayLoadInfo` structure pointed to by the exception parameter: - **Failing (importing) module:** `app\resources\app.asar.unpacked\node_modules\@worklouder\device-kit-oai\node_modules\@worklouder\wl-device-kit\node_modules\serialport\node_modules\@serialport\bindings-cpp\prebuilds\win32-arm64\node.napi.node` - **Delay-loaded DLL name:** `node.exe` - **Missing procedure:** `napi_create_function` - **`hmodCur` (module the delay-load resolved to):** `ChatGPT.exe` — i.e. the node-gyp delay-load hook correctly redirected `node.exe` to the host executable. So the redirect works, but the host exe doesn't have the symbol. Reading the PE export table of the ARM64 `ChatGPT.exe` confirms it: **the export directory contains only 2 named exports, and zero `napi_*` / `node_api_*` symbols.** A healthy Electron executable exports the full Node-API surface. The ARM64 build appears to have been linked without the Node export list. Any NAPI prebuilt that loads in the main process will therefore kill the app; on my machine the trigger is the serialport addon loaded by `@worklouder/device-kit-oai` roughly 10–15 seconds after startup. ## Why it looks like a sudden regression The app ran fine for ~9 hours overnight (July 14→15), then began crash-looping on every launch the morning of July 15 with no local changes, no app update (same version before/after), and it still crashes after a complete uninstall + data wipe + fresh Store install. That strongly suggests the device-kit/serialport load is gated by a server-side (Statsig) feature flag that was recently enabled — which would mean every Windows ARM64 user is affected as of that flag flip. If that's right, there are two fixes: 1. Short term: turn the flag off for `win32/arm64` (or skip loading `@worklouder/device-kit-oai` when the host exe lacks NAPI exports). 2. Proper fix: link the ARM64 `ChatGPT.exe` with the Node-API export list like the x64 build. ## Repro 1. Windows 11 ARM64 machine. 2. Install Codex app from the Microsoft Store (26.707.9981.0). 3. Launch. Window appears, app exits ~10–15 s later. 4. A new `.dmp` appears in `%LOCALAPPDATA%\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Roaming\Codex\web\Codex\Crashpad\reports\` with exception `0xC06D007F`. Happy to share a minidump privately if useful. ## Possibly related - #27574 (same disappear-after-launch symptom on x64 — may or may not be the same cause) - Unrelated but observed in logs: the updater polls a "primary runtime manifest" that 404s every 30 s for this build (`primary_runtime_update_poll_failed ... 404 Not Found`).