What version of the Codex App are you using?
- Microsoft Store package:
OpenAI.Codex 26.721.11231.0 (x64)
- Bundled Codex CLI reported by the desktop log:
0.146.0-alpha.3.1
- Bundled
chrome.dll: 150.0.7871.128
What subscription do you have?
Pro Lite ($100)
What platform is your computer?
- Windows 11 Pro
10.0.26200, x64
- Microsoft Store/MSIX installation
- AMD Radeon Graphics, driver
32.0.21037.1004
- Parsec Virtual Display Adapter
0.45.0.0 is also installed
What issue are you seeing?
Normal AppX activation succeeds, but the app exits silently about 2.4 seconds after launch. No usable window or error dialog remains.
The desktop log shows that the bundled Codex app-server starts and initializes successfully. Immediately afterward, the main UI fails to load:
Launching app ... packaged=true platform=win32
[StdioConnection] stdio_transport_spawned ... codex.exe
[AppServerConnection] initialize_handshake_result ... outcome=success
[AppServerConnection] Codex CLI initialized
[window-manager] Failed to load bundle at errorCode=ERR_FAILED errorMessage="ERR_FAILED (-2) loading 'app://-/index.html'"
A single reproduction generated three Crashpad minidumps:
- Renderer process:
0xC0000005 access violation, operation execute, exception/invalid address 0x00007FFEE98F3CB0.
- Second renderer process: the same
0xC0000005 execute violation at the same address.
- Browser/main process:
0x80000003 in bundled chrome.dll+0x15C4CC8.
The two renderer dumps are small early-process dumps and do not contain chrome.dll in their module lists, so I am not claiming that their exception address maps to a specific module. The reliable facts are the identical renderer execute violations, the subsequent browser-process breakpoint in bundled chrome.dll, and the UI bundle load failure.
This reproduced on all three observed launches. On the measured launch, the ChatGPT.exe process tree was gone after approximately 2.4 seconds.
What steps can reproduce the bug?
- Install or register Microsoft Store package
OpenAI.Codex_26.721.11231.0_x64__2p2nqsd0c76g0.
- Launch the normal Start menu entry or activate
OpenAI.Codex_2p2nqsd0c76g0!App.
- Observe the processes start and then disappear after approximately 2.4 seconds.
- Inspect the desktop log and Crashpad reports under the package's local app-data directory.
- Observe two renderer
0xC0000005 dumps and one browser/main-process dump per launch.
What is the expected behavior?
The signed Store app should open and remain usable. If the renderer or local app:// bundle cannot initialize, the app should show a recoverable diagnostic instead of silently terminating the entire desktop host.
Additional diagnostic results
Get-AppxPackage reports package status Ok.- AppX Stage/Register operations completed successfully.
- The Microsoft Store package catalog signature is valid.
app.asar is present and its header contains webview/index.html (size=14213, SHA-256 recorded in the ASAR metadata), so the logged URL failure is not explained by a missing packaged HTML entry.- No matching Code Integrity block was found around the crash.
- No Windows Display, GPU-reset, WHEA, or related System error was recorded around the reproduction.
NODE_OPTIONS, ELECTRON_RUN_AS_NODE, ELECTRON_NO_ASAR, and Electron logging override variables are unset at process, user, and machine scope.- AppInit DLL loading is disabled and no
ChatGPT.exe IFEO debugger entry is configured.
- The application log contains no Codex/ChatGPT WER crash event; the crashes are captured by the app's own Crashpad handler.
Related issues
Raw dumps are retained locally because minidumps can contain private process memory, paths, and session data. A narrowly scoped dump or symbolicated excerpt can be provided privately to OpenAI maintainers if requested. No raw dump, full log, username, SID, machine name, session ID, or account data is attached publicly.
What version of the Codex App are you using?
OpenAI.Codex 26.721.11231.0(x64)0.146.0-alpha.3.1chrome.dll:150.0.7871.128What subscription do you have?
Pro Lite ($100)
What platform is your computer?
10.0.26200, x6432.0.21037.10040.45.0.0is also installedWhat issue are you seeing?
Normal AppX activation succeeds, but the app exits silently about 2.4 seconds after launch. No usable window or error dialog remains.
The desktop log shows that the bundled Codex app-server starts and initializes successfully. Immediately afterward, the main UI fails to load:
A single reproduction generated three Crashpad minidumps:
0xC0000005access violation, operationexecute, exception/invalid address0x00007FFEE98F3CB0.0xC0000005execute violation at the same address.0x80000003in bundledchrome.dll+0x15C4CC8.The two renderer dumps are small early-process dumps and do not contain
chrome.dllin their module lists, so I am not claiming that their exception address maps to a specific module. The reliable facts are the identical renderer execute violations, the subsequent browser-process breakpoint in bundledchrome.dll, and the UI bundle load failure.This reproduced on all three observed launches. On the measured launch, the
ChatGPT.exeprocess tree was gone after approximately 2.4 seconds.What steps can reproduce the bug?
OpenAI.Codex_26.721.11231.0_x64__2p2nqsd0c76g0.OpenAI.Codex_2p2nqsd0c76g0!App.0xC0000005dumps and one browser/main-process dump per launch.What is the expected behavior?
The signed Store app should open and remain usable. If the renderer or local
app://bundle cannot initialize, the app should show a recoverable diagnostic instead of silently terminating the entire desktop host.Additional diagnostic results
Get-AppxPackagereports package statusOk.app.asaris present and its header containswebview/index.html(size=14213, SHA-256 recorded in the ASAR metadata), so the logged URL failure is not explained by a missing packaged HTML entry.NODE_OPTIONS,ELECTRON_RUN_AS_NODE,ELECTRON_NO_ASAR, and Electron logging override variables are unset at process, user, and machine scope.ChatGPT.exeIFEO debugger entry is configured.Related issues
chrome.dllaccess-violation regression on Store package26.715.10079.0and Windows build26200.26200, but for an older package and without this dump sequence.NODE_OPTIONS; that variable is not set on this system, and this app reaches successful Codex CLI initialization.Raw dumps are retained locally because minidumps can contain private process memory, paths, and session data. A narrowly scoped dump or symbolicated excerpt can be provided privately to OpenAI maintainers if requested. No raw dump, full log, username, SID, machine name, session ID, or account data is attached publicly.