Codex Windows app will not launch after a clean reinstall.

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

• #25297
• #25188
• #25368
• #25203
• #25157

Powered by Codex Action

happening to me as well. any workaround?

UPDATE to 26.527.60818. it works.

still not working for me after update

<img width="565" height="207" alt="Image" src="https://github.com/user-attachments/assets/26904169-4cd5-4fa7-8eda-70acf924a62c" />

I'm still struggling with this, do you know if Codex CLI works properly?

same problem

plus one

I have met the same issue.

same problem; how to do fix it?

same problem

same problem; how to do fix it?

It's working fine after today's update.

Same problem here for days now..
Paying $200 a month for an app that does not work... wow
cli kind of does the job, but my daily office work without the desktop feels like walking with a stone in my shoe..

Same issue here for a week now.

Codex desktop (Windows / MS Store) crashes ~0.3s after launch — unhandled C++ exception (0xE06D7363), no window ever shown

Summary

The Codex desktop app (Microsoft Store / MSIX) crashes almost immediately on every launch. No window is ever displayed. The main/browser process starts, logs two lines, begins the local app-server connection, then dies ~0.3s in, writing a ~34 MB Crashpad minidump on every attempt. The Codex CLI works perfectly on the same machine.

This looks like the same class of problem as #25489, #24998, #27175, #17485 — posting a fully-diagnosed instance with a crash signature.

Environment

• App: OpenAI.Codex (MS Store), version 26.609.3341.0 (AUMID OpenAI.Codex_2p2nqsd0c76g0!App)
• Bundled Chromium: 149.0.7827.54
• Backend: codex-cli 0.130.0-alpha.5 (works fine)
• OS: Windows 11 Pro 26200 (LG gram laptop)
• CPU/GPU: Intel Core Ultra (Lunar Lake) with Intel Arc 140T iGPU + NVIDIA RTX 4050 Laptop dGPU (hybrid)

Crash signature (parsed from the minidump)

• Exception code: 0xE06D7363 — i.e. an unhandled C++ exception (raised via KERNELBASE!RaiseException), not an access violation / driver fault.
• A new ~34 MB minidump is written on every launch to:

%LOCALAPPDATA%\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Roaming\Codex\web\Codex\Crashpad\reports

Logs before the crash

Main process log (...\LocalCache\Local\Codex\Logs\...) ends identically every time after 2 lines:

info Launching app ... buildFlavor=prod packaged=true platform=win32
info Appshot hotkey inactive configured=true enabled=true platform=win32

With --enable-logging=stderr --v=1, stdout reaches the app-server stage and then the process dies:

[AppServerConnection] Starting app-server connection hostId=local transport=stdio
[AppServerConnection] app_server_connection.state_changed ... next=connecting ...
[remote-connections/window-context] remote_project_connection_restore_skipped reason=no_remote_projects

No FATAL / CHECK / ERROR line is logged before death (only a benign google_update_settings_win.cc usagestats key warning).

What was ruled out (extensive)

• GPU drivers: updated Intel Arc → 32.0.101.8826 (2026-05) and NVIDIA → 32.0.16.1047 (2026-05). No change.
• Rendering backend: crashes with default, --no-sandbox, --use-angle=d3d11, --disable-features=Vulkan/SkiaGraphite/Dawn, --use-angle=swiftshader, --disable-gpu, --in-process-gpu. Only --disable-gpu --disable-software-rasterizer together avoid the crash — but then no window is ever shown (rendering fully disabled).
• Chromium profile: deleting/recreating the web\Codex profile → fresh profile still crashes.
• Caches: clearing GPUCache / GrShaderCache / ShaderCache → no change.
• Clean reinstall: full uninstall + removal of package data + reinstall of the same Store version → still crashes.
• Windows security policy: Exploit Protection / ACG / CIG / WDAC / Smart App Control all OFF or default.
• 3rd-party security agent: stopping the endpoint-security service entirely → still crashes.
• Config: moving ~/.codex aside (clean config) → still crashes.
• System Chromium baseline: Microsoft Edge launches and keeps a healthy GPU process on the same machine → system graphics stack is fine; the problem is Codex-specific.

Reproducibility

100% — every launch crashes (8+ consecutive attempts, each producing a minidump).

Notes for triage

The crash is a C++ exception thrown during early startup, correlated with graphics/compositor initialization (only fully disabling rendering avoids it, but that also suppresses the window). A symbolicated stack from any of the attached minidumps should pinpoint the throw site. Happy to upload a minidump.

# Codex desktop (Windows / MS Store) crashes ~0.3s after launch — unhandled C++ exception (0xE06D7363), no window ever shown ## Summary The Codex desktop app (Microsoft Store / MSIX) crashes almost immediately on every launch. No window is ever displayed. The main/browser process starts, logs two lines, begins the local app-server connection, then dies ~0.3s in, writing a ~34 MB Crashpad minidump on every attempt. The Codex CLI works perfectly on the same machine. This looks like the same class of problem as #25489, #24998, #27175, #17485 — posting a fully-diagnosed instance with a crash signature. ## Environment App: OpenAI.Codex (MS Store), version 26.609.3341.0 (AUMID OpenAI.Codex_2p2nqsd0c76g0!App) Bundled Chromium: 149.0.7827.54 Backend: codex-cli 0.130.0-alpha.5 (works fine) OS: Windows 11 Pro 26200 (LG gram laptop) CPU/GPU: Intel Core Ultra (Lunar Lake) with Intel Arc 140T iGPU + NVIDIA RTX 4050 Laptop dGPU (hybrid) ## Crash signature (parsed from the minidump) Exception code: 0xE06D7363 — i.e. an unhandled C++ exception (raised via KERNELBASE!RaiseException), not an access violation / driver fault. A new ~34 MB minidump is written on every launch to: %LOCALAPPDATA%\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Roaming\Codex\web\Codex\Crashpad\reports ## Logs before the crash Main process log (...\LocalCache\Local\Codex\Logs\...) ends identically every time after 2 lines: `` info Launching app ... buildFlavor=prod packaged=true platform=win32 info Appshot hotkey inactive configured=true enabled=true platform=win32 ` With --enable-logging=stderr --v=1, stdout reaches the app-server stage and then the process dies: ` [AppServerConnection] Starting app-server connection hostId=local transport=stdio [AppServerConnection] app_server_connection.state_changed ... next=connecting ... [remote-connections/window-context] remote_project_connection_restore_skipped reason=no_remote_projects ` No FATAL / CHECK / ERROR line is logged before death (only a benign google_update_settings_win.cc usagestats key warning). ## What was ruled out (extensive) * **GPU drivers**: updated Intel Arc → 32.0.101.8826 (2026-05) and NVIDIA → 32.0.16.1047 (2026-05). No change. * **Rendering backend**: crashes with default, --no-sandbox, --use-angle=d3d11, --disable-features=Vulkan/SkiaGraphite/Dawn, --use-angle=swiftshader, --disable-gpu, --in-process-gpu. **Only --disable-gpu --disable-software-rasterizer together avoid the crash — but then no window is ever shown** (rendering fully disabled). * **Chromium profile**: deleting/recreating the web\Codex profile → fresh profile still crashes. * **Caches**: clearing GPUCache / GrShaderCache / ShaderCache → no change. * **Clean reinstall**: full uninstall + removal of package data + reinstall of the same Store version → still crashes. * **Windows security policy**: Exploit Protection / ACG / CIG / WDAC / Smart App Control all OFF or default. * **3rd-party security agent**: stopping the endpoint-security service entirely → still crashes. * **Config**: moving ~/.codex` aside (clean config) → still crashes. System Chromium baseline: Microsoft Edge launches and keeps a healthy GPU process on the same machine → system graphics stack is fine; the problem is Codex-specific. ## Reproducibility 100% — every launch crashes (8+ consecutive attempts, each producing a minidump). ## Notes for triage The crash is a C++ exception thrown during early startup, correlated with graphics/compositor initialization (only fully disabling rendering avoids it, but that also suppresses the window). A symbolicated stack from any of the attached minidumps should pinpoint the throw site. Happy to upload a minidump.

I'm experiencing the exact same issue. I was ultimately able to successfully launch the Codex app using this command:

"C:\Program Files\WindowsApps\OpenAI.Codex_26.623.13972.0_x64__2p2nqsd0c76g0\app\Codex.exe" --enable-logging=stderr --disable-gpu --disable-gpu-compositing