[Windows Store App] App crashes on launch — renderer process crashes immediately, no window displayed

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

v0.139.0 (Microsoft Store)

What subscription do you have?

Plus

What platform is your computer?

Windows 11 x64

What issue are you seeing?

The Codex desktop app (Microsoft Store) fails to open on Windows 11. The main process starts but the renderer crashes immediately every time, resulting in no window being displayed. The CLI works perfectly in the same environment.

Symptoms:

• Double-clicking the app icon shows no window
• App icon briefly appears in taskbar then disappears
• No error dialog is shown to the user
• 7 crash dump files found in Crashpad/reports/

Log evidence (from %LocalAppData%\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\Codex\Logs\):

2026-06-13T06:05:53.056Z info  Launching app ... buildFlavor=prod platform=win32
2026-06-13T06:05:58.171Z warning Failed to load shell env caller=startup
  detail="Timed out after 5000ms."
  durationMs=5109
  path="...\AppData\Roaming\npm"
  status=timed_out timeoutMs=5000
2026-06-13T06:05:59.745Z info  Appshot hotkey inactive

After the shell env timeout, the renderer crashes with no window appearing.

Things tried (none resolved the issue):

• Uninstall and reinstall from Microsoft Store
• Set OPENAI_API_KEY as user environment variable + restart
• Set OPENAI_API_KEY as system environment variable
• Created ~/.codex/config.json with API key
• Disabled hardware acceleration via Local State file

Workaround: Running codex directly via PowerShell works fine. Only the Store app wrapper fails.

Node.js: v22.22.3 | npm: 10.9.8 | @openai/codex CLI: v0.139.0 (works)

What steps can reproduce the bug?

1. Install Codex from Microsoft Store
2. 2. Double-click the Codex app icon
3. 3. Observe: taskbar icon appears briefly then disappears, no window shown

Note: Running codex in PowerShell works fine.

What is the expected behavior?

The Codex desktop app should launch and display a functional window, as it does when running codex via PowerShell CLI.

Additional information

_No response_