[Windows 10][26.810.7004.0] Startup crashes in chrome.dll 151.0.7922.137 at stable offset 0x507535B

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

The UI never opens, so the About dialog is unavailable. The registered Microsoft Store package version is:

OpenAI.Codex 26.810.7004.0 (x64)

Package family: OpenAI.Codex_2p2nqsd0c76g0

Registered AUMID: OpenAI.Codex_2p2nqsd0c76g0!App

Bundled chrome.dll version: 151.0.7922.137

What subscription do you have?

Unknown. The application crashes before its UI or account information becomes available.

What platform is your computer?

Windows 10 Pro 22H2, build 10.0.19045.6466, x64.

What issue are you seeing?

The Microsoft Store app activates, creates several ChatGPT.exe processes, and then exits before any window appears. There is no visible error dialog.

The current-user package is registered with Status=Ok, and the Start menu entry resolves to the exact AUMID above. Process-handle monitoring captured the primary process exiting after approximately 0.45-0.63 seconds with:

ExitStatus=3221225477 (0xC0000005)

Twelve recent Crashpad minidumps from repeated launch attempts have the exact same signature:

ExceptionCodeHex=0xC0000005
ExceptionFlagsHex=0x00000000
FaultModule=chrome.dll
ModuleVersion=151.0.7922.137
ModuleOffsetHex=0x507535B

All 12 dumps point to the same module version and native offset. Windows Application Error 1000 and WER 1001 were not emitted for these attempts; the crashes appear to have been captured by the application's own Crashpad handler.

No raw dump, memory stream, stack, command line, user path, SID, account identifier, or application content is included in this public report.

What steps can reproduce the bug?

1. Install Microsoft Store package OpenAI.Codex_26.810.7004.0_x64__2p2nqsd0c76g0 on Windows 10 x64 build 19045.
2. Launch the registered ChatGPT Start menu entry normally.
3. Observe multiple short-lived ChatGPT.exe processes.
4. The main process exits in less than one second with 0xC0000005; no application window appears.
5. A new Crashpad dump is created with chrome.dll 151.0.7922.137 + 0x507535B.

The failure reproduced across repeated Store uninstall/reinstall cycles and repeated normal activations.

Additional controlled attempts:

• Activation through IApplicationActivationManager with --disable-gpu, --disable-gpu-compositing, and Vulkan/Skia-related features disabled still produced the same immediate failure.
• No existing GPU/shader cache directories were present under the current package profile, so there was no stale GPU cache to clear.
• No WindowsApps ACL, package ownership, UAC, system policy, or dump settings were modified.

What is the expected behavior?

The signed and correctly registered Store app should remain running and display its main window, or show an actionable error instead of silently terminating.

Additional information

This appears related to the existing Windows startup-crash class, but the affected package, Chromium version, and stable offset are newer and were not found in an existing report:

• #25376
• #28883
• #34923
• #36084

The 12 original minidumps are retained locally and are not safe for public upload because they may contain process memory. A narrowly scoped dump or symbolicated excerpt can be provided through a private maintainer-approved channel if requested.

Start by reproducing the registered Microsoft Store AUMID launch on Windows 10 x64 and compare the Crashpad minidumps for chrome.dll 151.0.7922.137 at offset 0x507535B. No source file or test is named; progress requires a maintainer-approved dump or symbolicated excerpt, and done means the app remains running with a main window or shows an actionable error.