Windows startup crash: bundled @serialport/bindings-cpp delay-loads Node-API from ChatGPT.exe (0xc06d007f, ERROR_PROC_NOT_FOUND)

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

26.707.9981.0

What subscription do you have?

ChatGPT Crash error

What platform is your computer?

Windows 11

What issue are you seeing?

Checklist

• [x] I searched existing issues.
• [x] I can reproduce the issue consistently.
• [x] This issue occurs on the latest available desktop version.

Environment

• OS: Windows 11 24H2 (Build 26200)
• Application: ChatGPT Desktop / Codex
• Version: 26.707.9981.0

Summary

The application crashes during startup with:

Exception code: 0xc06d007f

WinDbg indicates this is a delay-load failure caused by a bundled native
module.

Crash analysis

The failing module is:

app.asar.unpacked
 └── node_modules
     └── @worklouder
         └── wl-device-kit
             └── node_modules
                 └── @serialport
                     └── bindings-cpp
                         └── build
                             └── Release
                                 └── serialport.node

The loader attempts to resolve:

napi_module_register

from:

ChatGPT.exe

and fails with:

LastError = 127
ERROR_PROC_NOT_FOUND

leading to:

0xc06d007f

during module initialization.

Root cause

This appears to be a packaging/linking issue.

serialport.node looks like it was built for a standard Node.js runtime,
where Node-API symbols are expected to be exported by the host executable.

However, in the current desktop application:

• ChatGPT.exe exports only a very small number of symbols

(e.g. GetHandleVerifier, IsSandboxedProcess).

• Node/N-API exports are instead provided by chrome.dll.

Other bundled native modules (for example better_sqlite3) load normally
and do not appear to rely on this delay-load mechanism.

serialport.node therefore attempts to resolve
napi_module_register from ChatGPT.exe, receives
ERROR_PROC_NOT_FOUND (127), and crashes before the application finishes
starting.

Things that do NOT appear related

• Windows 11 Build 26200 is fully supported.
• Samsung Knox DLLs (LSP4ShellLite64.dll, EpMng64.dll) are injected,

but the crash stack indicates they are not involved.

Possible workaround

Disconnecting USB serial devices or Work Louder hardware may prevent
wl-device-kit from being loaded, although this depends on whether the
module is loaded lazily.

If the module is always loaded during startup, there is no practical
workaround.

Expected behavior

The desktop application should not crash because of an optional hardware
integration.

Possible fixes include:

• rebuilding @serialport/bindings-cpp for the desktop runtime,
• removing the incorrect delay-load dependency,
• resolving N-API symbols from the correct runtime,
• or loading the Work Louder integration lazily so startup cannot fail.

Additional information

The crash is reproducible on every launch.

If needed, I can provide:

• WinDbg stack trace
• full crash dump
• PE export analysis of ChatGPT.exe
• PE export analysis of chrome.dll
• import table of serialport.node

What steps can reproduce the bug?

Environment

• OS: Windows 11 24H2 (Build 26200)
• App: ChatGPT/Codex Desktop
• Version: 26.707.9981.0

Observed behavior
The application crashes during startup with exception:

0xc06d007f (delay-load failure)

WinDbg analysis shows:

LastError = 127 (ERROR_PROC_NOT_FOUND)

The failing module is:

app.asar.unpacked
@worklouder\wl-device-kit
@serialport\bindings-cpp\build\Release\serialport.node

Root cause

serialport.node appears to have been built expecting standard Node.js
behavior and delay-loads Node-API exports such as:

napi_module_register

However the desktop app hosts Node differently.

ChatGPT.exe exports only a minimal set of symbols, while the Node-API
exports reside in chrome.dll.

Other native modules (for example better_sqlite3) appear to be built
correctly for this architecture and load successfully.

serialport.node instead attempts to resolve Node-API symbols from
ChatGPT.exe, causing ERROR_PROC_NOT_FOUND (127) and resulting in
exception 0xc06d007f during module load.

Additional observations

• Windows version is fully supported.
• Samsung Knox DLLs are injected but do not appear to participate in

the failure.

• Disconnecting USB serial devices may avoid loading the Work Louder

device kit, but this is only a possible workaround.

Expected behavior

Either:

• rebuild serialport.node against the desktop runtime,
• remove the delay-load dependency on node.exe exports,
• or ensure the Work Louder device kit is loaded lazily and cannot crash

application startup.

This appears to be a packaging/linking issue in the bundled native
module rather than an OS compatibility problem.

What is the expected behavior?

_No response_

Additional information

_No response_