Repository navigation
Codex Desktop App immediately exits on Windows ARM64 (Snapdragon X Plus) #33393
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Microsoft Store version 26.707.9981.0 CLI version: codex 0.144.2
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Windows 11 Home 24H2 ARM64 (Snapdragon X Plus) ASUS Vivobook S15 S5507QA Qualcomm Snapdragon X Plus Qualcomm Adreno X1-45 GPU
What issue are you seeing?
The Microsoft Store version of the Codex Desktop App immediately exits after launch.
The app window briefly appears and then closes automatically.
The Codex CLI works correctly.
Cursor works correctly.
Chrome works correctly.
The issue persists after uninstalling the app, rebooting Windows, and reinstalling the latest Microsoft Store version.
No Application Error is recorded in Windows Event Viewer.
Windows Error Reporting only records LiveKernelEvent 141.
This issue occurs every time.
What steps can reproduce the bug?
- Install Codex from Microsoft Store.
- Launch the Codex Desktop App.
- The window appears briefly.
- The application exits immediately.
What is the expected behavior?
The Codex Desktop App should remain open and allow normal usage.
Additional information
Environment:
- ASUS Vivobook S15 S5507QA
- Windows 11 Home 24H2
- ARM64
- Snapdragon X Plus
- Qualcomm Adreno X1-45 GPU
Additional notes:
- Microsoft Store version: 26.707.9981.0
- Codex CLI works normally.
- Codex Desktop App always exits immediately after launch.
- Cursor works normally.
- Chrome works normally.
- Reinstalling the app does not resolve the issue.
- No Application Error is logged.
- Windows reports LiveKernelEvent 141.
This appears to be specific to Windows on ARM64 (Snapdragon X Plus), because the Codex CLI works normally while only the Desktop App crashes immediately.
Activity
github-actions commentedon Jul 15, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
YoGoodBrother commentedon Jul 15, 2026
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.exeshell in 26.707.9981.0 ships without N-API exports.Evidence:
0xC06D007F(VC++ delay-load: procedure not found), raised viaKERNELBASE.dll!RaiseException(+0x1233C4)DelayLoadInfofromExceptionInformation[0]in the minidumps: szDll =node.exe, missing procedure =napi_create_function— identical across all dumps/sessionsapp\ChatGPT.exe(arm64) contains nonapi_*export strings at all, while the bundledcua_node\bin\node.exehas them — so the first native.nodeaddon that loads in the main process raises the delay-load failure and the app exits[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\Ruled out during triage: fresh Chromium profile (
web\Codexreset), 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.gabriellenz commentedon Jul 15, 2026
Independent reproduction with a matching ARM64 environment and package build.
Environment:
Timeline from Windows event logs:
Additional isolation:
codex.exe --versionandcodex.exe app-server --help.auto.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.
KhomyakAndriy commentedon Jul 15, 2026
Disclaimer: report generated by Codex (via Rider extension)
Independent reproduction on a different Windows ARM64 environment, with the same Store package build.
Environment:
OpenAI.Codex_26.707.9981.0_arm64__2p2nqsd0c76g026.707.72221150.0.7871.11524.14.0Observed startup sequence:
ChatGPT.exeprocesses remain alive briefly, then all terminate.Minidump analysis:
0xC06D007F127(ERROR_PROC_NOT_FOUND)KERNELBASE.dllnode.exenapi_create_functionThe 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.nodeLoaded native modules at the time of the crash also included:
better_sqlite3.nodewindows-updater.nodewindows-account.node@serialport/bindings-cppnode.napi.nodeThis 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:
404 Not Foundwhile polling:codex-primary-runtime/latest/win32-arm64/LATEST.jsonThis does not appear to be the immediate crash trigger because the local backend has already connected successfully.
TheBeems commentedon Jul 15, 2026
Same error here! Suddenly the app crashed during use earlier today, and now it starts but immediately crashes.
ryenwang commentedon Jul 15, 2026
Same crash here, confirming on another ARM64 machine.
Environment
OpenAI.Codex_26.707.9981.0_arm64__2p2nqsd0c76g0, app release 26.707.72221App window appears for ~2.5 s, then process exits. Reinstalling from MSFT Store does not fix it.
Crash details (from local Crashpad minidump)
0xC06D007F(VC++ delay-load: procedure not found),dwLastError = 127(ERROR_PROC_NOT_FOUND), raised viaKERNELBASE.dllDelayLoadInfo: szDll =node.exe, missing procedure =napi_create_function;hmodCurresolves to the base ofChatGPT.exe@worklouder/device-kit-oai/.../@serialport/bindings-cpp/prebuilds/win32-arm64/node.napi.nodebetter_sqlite3.node,windows-updater.node,windows-account.nodeapp\ChatGPT.exe: 2 exports total, zeronapi_*— so the serialport addon's delay-load ofnapi_create_functioncan never resolve and takes down the main processpermissionProfile/list; Crashpad dump written the same secondMatches the analysis in this thread and sibling reports
PCI-Statmonkey commentedon Jul 15, 2026
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:
"local":"auto"value from.codex-global-state.jsonNone of these steps resolved the problem.
Windows logs show that the application launches successfully:
app\ChatGPT.exeis startedThere 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.
TheBeems commentedon Jul 16, 2026
I had an update this morning to 26.707.12708.0, but the problem still persists. Please fix this!
MarkMasiak commentedon Jul 16, 2026
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.
zhdanau commentedon Jul 16, 2026
I just downloaded the latest version, and the program no longer crashes. The problem is resolved. Thank you!
KhomyakAndriy commentedon Jul 16, 2026
Follow up to #33393 (comment)
Confirmed, newest application is working fine on my environment.
Version 26.707.91948
Released Jul 16, 2026
MarkMasiak commentedon 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.