Codex Desktop App immediately exits on Windows ARM64 (Snapdragon X Plus)

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

• #33392
• #33385
• #33381
• #33384
• #33389

Powered by Codex Action

Same crash here — Windows 11 Home 25H2 (build 26200.8875), ARM64, Store build 26.707.9981.0 (previous 26.707.6957.0 worked on the same machine; the broken build arrived via silent Store auto-update mid-session). I dug into the Crashpad dumps and believe I found the root cause:

The ARM64 ChatGPT.exe shell in 26.707.9981.0 ships without N-API exports.

Evidence:

• Every launch dies ~6 s in with exception 0xC06D007F (VC++ delay-load: procedure not found), raised via KERNELBASE.dll!RaiseException (+0x1233C4)
• Dereferencing DelayLoadInfo from ExceptionInformation[0] in the minidumps: szDll = node.exe, missing procedure = napi_create_function — identical across all dumps/sessions
• Byte-scan of the shipped binaries: app\ChatGPT.exe (arm64) contains no napi_* export strings at all, while the bundled cua_node\bin\node.exe has them — so the first native .node addon that loads in the main process raises the delay-load failure and the app exits
• Timing matches: the desktop log dead-stops right after [git-repo-watcher] Starting git repo watcher (first native addon load); a Crashpad dump appears that exact second under %LOCALAPPDATA%\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Roaming\Codex\web\Codex\Crashpad\reports\
• Explains the "No Application Error is logged" observation in the OP — Crashpad intercepts before WER logs Event 1000

Ruled out during triage: fresh Chromium profile (web\Codex reset), fresh ~/.codex/.codex-global-state.json (only delays the crash to ~90 s while project sync repopulates), plugins."browser@openai-bundled" enabled=false, memory/GPU/kernel issues, pending Windows reboot, git/repo problems (git 2.52, all repos probe < 0.5 s). codex CLI 0.144.2 works fine standalone, same as OP.

This matches the sibling reports #33381 / #33384 / #33385 (serialport addon, same missing napi_create_function). Happy to share the Crashpad dumps if useful.

Independent reproduction with a matching ARM64 environment and package build.

Environment:

• Windows 11 Pro 10.0.26200, ARM64
• Snapdragon-based Surface system
• Qualcomm Adreno X1-85 GPU, driver 31.0.137.0
• Store package OpenAI.Codex_26.707.9981.0_arm64__2p2nqsd0c76g0
• Bundled backend reports codex-cli 0.144.2

Timeline from Windows event logs:

• 2026-07-14 09:28: package 26.707.9564.0 launched successfully.
• 2026-07-14 09:30: interactive update installed 26.707.9981.0.
• 26.707.9981.0 launched after the update and remained active overnight.
• 2026-07-15 09:17:41: Windows resumed from hibernation/Modern Standby.
• 2026-07-15 09:17:46: the OpenAI.Codex 26.707.9981.0 AppX container was destroyed.
• Every subsequent cold launch of 26.707.9981.0 exited after roughly 7-10 seconds.
• Uninstalling, deleting app data, reinstalling the same Store build, and rebooting did not recover it.

Additional isolation:

• A completely fresh ~/.codex state was created during the failed launches, so stale SQLite/global state was not required to reproduce.
• The extracted, OpenAI-signed backend starts successfully with both codex.exe --version and codex.exe app-server --help.
• Sandbox audit completes successfully.
• WinHTTP and per-user proxy settings are direct/no proxy.
• WSL mode was not explicitly enabled; desktop state showed local agent mode auto.
• No Codex crash dump or archived WER report was produced. One later attempt generated Application Hang 1002 for ChatGPT.exe 150.0.7871.115.

This is consistent with the ARM64 shell/N-API failure described in the comment above, although no Crashpad dump survived locally because the app was uninstalled during troubleshooting. The hibernation resume appears to have been the boundary where the previously running process ended and cold launches began exercising the broken path.

Disclaimer: report generated by Codex (via Rider extension)

Independent reproduction on a different Windows ARM64 environment, with the same Store package build.

Environment:

• Windows 11 Pro 10.0.26200, ARM64
• Parallels VM running on Apple Silicon
• Parallels Display Adapter (WDDM), driver 20.18.1263.23929
• Store package OpenAI.Codex_26.707.9981.0_arm64__2p2nqsd0c76g0
• App release reported in diagnostics: 26.707.72221
• Electron/Chromium 150.0.7871.115
• Node.js 24.14.0
• Codex through the JetBrains Rider integration works correctly

Observed startup sequence:

• Windows AppModel activation succeeds without errors.
• The renderer mounts successfully.
• The local app server connects and initializes.
• Authentication, configuration, thread listing, and model listing complete successfully.
• Several ChatGPT.exe processes remain alive briefly, then all terminate.
• No conventional Application Error or .NET Runtime event is recorded.
• A roughly 40 MB Crashpad minidump is generated.

Minidump analysis:

• Exception code: 0xC06D007F
• Windows error: 127 (ERROR_PROC_NOT_FOUND)
• Fault raised through KERNELBASE.dll
• Delayed-load DLL: node.exe
• Missing procedure: napi_create_function

The native module containing the failed delay-load import is:

@worklouder/device-kit-oai/node_modules/@worklouder/wl-device-kit/node_modules/serialport/node_modules/@serialport/bindings-cpp/prebuilds/win32-arm64/node.napi.node

Loaded native modules at the time of the crash also included:

• better_sqlite3.node
• windows-updater.node
• windows-account.node
• the ARM64 @serialport/bindings-cpp node.napi.node

This strongly suggests that the bundled ARM64 serial-port native add-on expects the Electron host to expose node.exe!napi_create_function, but that export is unavailable in this ARM64 app build. The resulting delay-load exception terminates the main process.

Additional isolation:

• The installed app architecture matches the ARM64 operating system.
• Launching with Chromium GPU acceleration disabled does not prevent the exit.
• WSL is not installed, but the WSL detection warning is non-fatal and initialization continues afterward.
• Authentication and the Codex backend both initialize successfully.
• The Store currently reports no newer package version.
• The logs also show a secondary 404 Not Found while polling:

codex-primary-runtime/latest/win32-arm64/LATEST.json
This does not appear to be the immediate crash trigger because the local backend has already connected successfully.

Same error here! Suddenly the app crashed during use earlier today, and now it starts but immediately crashes.

Same crash here, confirming on another ARM64 machine.

Environment

• Microsoft Surface Pro, 11th Edition
• Windows 11 Home Insider Preview 10.0.26300 (build 26300), ARM64
• Snapdragon X Elite X1E80100 (12-core)
• Qualcomm Adreno X1-85 GPU, driver 31.0.137.0
• Store package OpenAI.Codex_26.707.9981.0_arm64__2p2nqsd0c76g0, app release 26.707.72221
• Codex CLI works fine standalone

App window appears for ~2.5 s, then process exits. Reinstalling from MSFT Store does not fix it.

Crash details (from local Crashpad minidump)

• Exception code 0xC06D007F (VC++ delay-load: procedure not found), dwLastError = 127 (ERROR_PROC_NOT_FOUND), raised via KERNELBASE.dll
• DelayLoadInfo: szDll = node.exe, missing procedure = napi_create_function; hmodCur resolves to the base of ChatGPT.exe
• Faulting native module: @worklouder/device-kit-oai/.../@serialport/bindings-cpp/prebuilds/win32-arm64/node.napi.node
• Other native addons loaded at crash time: better_sqlite3.node, windows-updater.node, windows-account.node
• Byte-scan of the shipped ARM64 app\ChatGPT.exe: 2 exports total, zero napi_* — so the serialport addon's delay-load of napi_create_function can never resolve and takes down the main process
• Main-process log dead-stops right after permissionProfile/list; Crashpad dump written the same second

Matches the analysis in this thread and sibling reports

Confirming the same issue on a Windows ARM64 Surface.

Device:
Microsoft Surface running Windows 11 ARM64

Codex package:
OpenAI.Codex_26.707.9981.0_arm64__2p2nqsd0c76g0

Behavior:
The Codex desktop app opens normally, remains visible for approximately 8 seconds, and then closes without displaying an error.

What I have already tried:

• Repairing the app
• Resetting the app
• Uninstalling and reinstalling
• Restarting Windows
• Signing out and signing back in
• Running the app as Administrator
• Renaming/resetting the .codex folder
• Removing the saved "local":"auto" value from .codex-global-state.json

None of these steps resolved the problem.

Windows logs show that the application launches successfully:

• app\ChatGPT.exe is started
• The OpenAI.Codex AppX container is created successfully
• The process is added to the container
• Approximately 8 seconds later, the AppX container is destroyed

There is no conventional Application Error, exception code, Reliability Monitor failure, or failed activation event.

ChatGPT Classic continues to work normally on the same device and account.

This is preventing me from accessing and continuing work on an existing local development project. Based on the identical ARM64 package version and startup behavior reported here, this appears to be the same issue.

I had an update this morning to 26.707.12708.0, but the problem still persists. Please fix this!

I can confirm another ARM64 machine exhibiting the same behaviour.

In my case:

Surface Pro 11
Snapdragon X Elite
Windows 11 Insider Beta 26220.8764
ChatGPT desktop exits a few seconds after launch.

One additional observation:

Microsoft Store is also unstable on this machine and repeatedly crashes with:

gameplatformservices.dll
Exception 0xc0000005

I'm still investigating whether this is related or simply another symptom of the same underlying Windows issue.

That additional information may help others recognise a common pattern.

I just downloaded the latest version, and the program no longer crashes. The problem is resolved. Thank you!

Follow up to https://github.com/openai/codex/issues/33393#issuecomment-4983890395

Disclaimer: report generated by Codex (via Rider extension) Independent reproduction on a different Windows ARM64 environment, with the same Store package build. Environment: Windows 11 Pro 10.0.26200, ARM64 Parallels VM running on Apple Silicon Parallels Display Adapter (WDDM), driver 20.18.1263.23929 Store package OpenAI.Codex_26.707.9981.0_arm64__2p2nqsd0c76g0 App release reported in diagnostics: 26.707.72221 Electron/Chromium 150.0.7871.115 Node.js 24.14.0 Codex through the JetBrains Rider integration works correctly

Confirmed, newest application is working fine on my environment.
Version 26.707.91948
Released Jul 16, 2026

Possible workaround (worked for me on ARM64)

I wanted to share what finally resolved this for me in case it helps someone else.

Environment

Surface Pro 11 (Snapdragon X Elite)
Windows 11 Insider Beta 26220.8764 (ARM64)
Microsoft Store version of ChatGPT
Existing Codex installation migrated to ChatGPT

Symptoms

Codex worked previously.
After the migration to ChatGPT, the app would either:
display the "What's New"/onboarding screen for a few seconds and exit, or
exit immediately after launch.
Browser ChatGPT worked normally.

During troubleshooting I also noticed Microsoft Store crashing, although I'm not certain whether that was related.

What finally fixed it

A normal uninstall/reinstall was not enough.

The important difference was completely removing all remaining user data.

I manually deleted every remaining OpenAI/Codex folder I could find, including:

%USERPROFILE%\.codex
%USERPROFILE%\.cache
%USERPROFILE%\.agents
%LOCALAPPDATA%\OpenAI
Any remaining OpenAI/Codex folders under %LOCALAPPDATA%
Any remaining OpenAI package data I could locate

Only after removing all of the above did I reinstall ChatGPT.

The key observation

Every previous reinstall preserved my login and immediately returned to the existing state.

After deleting all remaining folders, ChatGPT behaved like a completely fresh installation:

prompted me to sign in again
displayed the full first-run onboarding
requested Windows integration permissions
completed setup successfully
now launches normally

This makes me suspect that some migration/profile state survives uninstall and can prevent the new ChatGPT desktop app from starting correctly.

I can't say with certainty which folder contained the problematic state, but removing all remaining OpenAI/Codex user data before reinstalling resolved the issue for me.