[Windows ARM64] App crashes immediately after sign-in — delay-load failure: napi_create_function not found (0xc06d007f)

Open 💬 6 comments Opened Jul 16, 2026 by SwordKirito33

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.707.12708.0 (arm64, Microsoft Store)

What subscription do you have?

plus

What platform is your computer?

Windows 11 build 26200, ARM64 (Snapdragon)

What issue are you seeing?

The app crashes ~2-3 seconds after launch, but only once signed in.

Not signed in (sitting on the login screen): app is completely stable.
Immediately after completing sign-in: app closes itself every time.

This started after a recent app update. The first crash happened while I was
using Codex mid-session; every launch since then crashes right after sign-in.

No Windows Application Error event is logged (Crashpad catches it), but a
new minidump is written on every crash.

What steps can reproduce the bug?

On a Windows 11 ARM64 machine (Snapdragon), install the Codex/ChatGPT app from Microsoft Store.
Launch the app — it opens fine and stays on the login screen indefinitely.
Sign in.
The app crashes ~2-3 seconds after sign-in completes. Reproduces 100% of the time.

What is the expected behavior?

The app should stay running after sign-in. ChatGPT.exe (arm64) should export the
N-API symbols that its bundled native addons delay-import.

Additional information

Crash analysis (from minidumps)

Two minidumps taken hours apart show an identical failure:

Exception code: 0xc06d007f (VcppException — delay-load failure)
Exception addr: KERNELBASE.dll +0x1233c4 (RaiseException)

Parsing the DelayLoadInfo struct passed to the exception:

Target DLL: node.exe
Import by name: true
Missing export: napi_create_function
GetLastError: 127 (ERROR_PROC_NOT_FOUND)
hmod: 0x7ff6bb660000

The hmod in DelayLoadInfo is identical to the load base of ChatGPT.exe itself —
i.e. the delay-load helper resolved "node.exe" to the host executable (expected for
Electron), but then failed to find napi_create_function exported from it.

So: a bundled native addon delay-imports napi_create_function, and the arm64 build
of ChatGPT.exe does not export it. This raises a fatal delay-load exception and the
process dies. This is consistent with the sign-in-only trigger — the addons are
loaded during post-login initialization, so the missing export is never hit while
the app sits on the login screen.

Native addons loaded in the dump (any of these may be the importer):

app\resources\app.asar.unpacked\node_modules\better-sqlite3\build\Release\better_sqlite3.node
app\resources\native\windows-updater.node
app\resources\native\windows-account.node
app\resources\app.asar.unpacked\node_modules\@worklouder\device-kit-oai\...\serialport\...\prebuilds\win32-arm64\node.napi.node

Likely an arm64 packaging/linking regression — the x64 build presumably exports the
N-API symbols correctly, which would explain the lack of other reports.

Things I tried that did NOT help

Repair and Reset via Windows Settings → Apps → Advanced options
Full uninstall + reinstall from Microsoft Store
Reinstalling the Edge WebView2 Runtime (installer reports it's already present)
Setting WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--disable-gpu
Renaming %USERPROFILE%\.codex → app launches and stays stable on the login screen,

but crashes again the moment I sign in

Environment notes

No Node.js installed system-wide
No WSL installed (wsl -l -v reports WSL is not installed)
No third-party security/monitoring software

Minidumps attached — both show the same napi_create_function failure.

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 4 days ago

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

#33429
#33415
#33516
#33525

Powered by Codex Action

megird · 4 days ago

• Confirmed root cause: This is a native module packaging defect in the current Codex App ARM64 build. It is not a user configuration, SSH, or graphics issue.

WinDbg results:

Exception code: 0xC06D007F (ERROR_PROC_NOT_FOUND)
Faulting module: node.napi.node
Target DLL: node.exe
Missing entry point: napi_create_function

The problematic file belongs to:

@worklouder/device-kit-oai
→ serialport
→ @serialport/bindings-cpp
→ win32-arm64/node.napi.node

This ARM64 native add‑on attempts to obtain N‑API from node.exe, but the App’s Electron host is actually ChatGPT.exe, ultimately causing the entire process to exit.

Actionable options:

Wait for OpenAI to release a fixed ARM64 build — this is the root‑cause solution.
If you can obtain the official x64 installer, run it under the x64 emulation layer on Windows ARM to bypass the defective win32-arm64/node.napi.node.
Submit a defect report to OpenAI support, including:

App: 26.707.12708.0 ARM64
Exception: 0xC06D007F
DLL/entry: node.exe!napi_create_function
Module: @serialport/bindings-cpp/prebuilds/win32-arm64/node.napi.node
Latest dump: 4e915651-62ae-4018-b5ea-b7d4fd9d8287.dmp

The full WinDbg log is saved in codex-crash-analysis.txt.

Not recommended: modifying the .node files inside WindowsApps — the package is signature‑protected, and even if forcibly changed, it could prevent the app from updating or launching. The official Windows App claims ARM64 support, so this is a compatibility defect that should be fixed in the release build.

SwordKirito33 · 4 days ago

• Confirmed root cause: This is a native module packaging defect in the current Codex App ARM64 build. It is not a user configuration, SSH, or graphics issue. WinDbg results: Exception code: 0xC06D007F (ERROR_PROC_NOT_FOUND) Faulting module: node.napi.node Target DLL: node.exe Missing entry point: napi_create_function The problematic file belongs to: `` @worklouder/device-kit-oai → serialport → @serialport/bindings-cpp → win32-arm64/node.napi.node ` This ARM64 native add‑on attempts to obtain N‑API from node.exe, but the App’s Electron host is actually ChatGPT.exe, ultimately causing the entire process to exit. **Actionable options**: 1. Wait for OpenAI to release a fixed ARM64 build — this is the root‑cause solution. 2. If you can obtain the official x64 installer, run it under the x64 emulation layer on Windows ARM to bypass the defective win32-arm64/node.napi.node. 3. Submit a defect report to OpenAI support, including: * App: 26.707.12708.0 ARM64 * Exception: 0xC06D007F * DLL/entry: node.exe!napi_create_function * Module: @serialport/bindings-cpp/prebuilds/win32-arm64/node.napi.node * Latest dump: 4e915651-62ae-4018-b5ea-b7d4fd9d8287.dmp The full WinDbg log is saved in codex-crash-analysis.txt. **Not recommended**: modifying the .node files inside WindowsApps` — the package is signature‑protected, and even if forcibly changed, it could prevent the app from updating or launching. The official Windows App claims ARM64 support, so this is a compatibility defect that should be fixed in the release build.

Thanks for confirming — matches my dump analysis exactly.

Re: option 2 — how did you obtain the x64 installer? On my machine both
chatgpt.com/download and the Store serve the arm64 package automatically
(Store picks by CPU arch). Is there a supported way to force the x64 build
on an ARM device?

megird · 4 days ago

Actionable options:

Wait for OpenAI to release a fixed ARM64 build — this is the root‑cause solution.
If you can obtain the official x64 installer, run it under the x64 emulation layer on Windows ARM to bypass the defective win32-arm64/node.napi.node.
Submit a defect report to OpenAI support, including:
App: 26.707.12708.0 ARM64
Exception: 0xC06D007F
DLL/entry: node.exe!napi_create_function
Module: @serialport/bindings-cpp/prebuilds/win32-arm64/node.napi.node
Latest dump: 4e915651-62ae-4018-b5ea-b7d4fd9d8287.dmp

The response above was generated using the Codex CLI exploration.

Jupiter363 · 4 days ago

我找到了一种可能的修复方案，我让codex给我安装了最新的cli版本的codex之后卡顿消失，原先也是windows持续崩溃0xC06D007F报错

MarkMasiak · 4 days ago

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.