Windows desktop app crashes on launch unless GPU is disabled (AMD Radeon 780M)

Open 💬 1 comment Opened Jun 14, 2026 by taccaya

Summary

The Codex Windows desktop app crashes shortly after launch. Reinstalling the app,
restarting Windows, changing the default browser to Edge, and logging into ChatGPT in Edge
did not resolve the issue.

The app stays running when launched directly with GPU disabled, so this appears related to
Chromium/Electron GPU initialization or GPU driver compatibility.

### Environment

  • OS: Windows 10 Pro, build 26200, 64-bit
  • Codex app package: OpenAI.Codex 26.609.4994.0
  • GPU: AMD Radeon 780M Graphics
  • GPU driver version: 32.0.22024.13003
  • GPU driver date: 2025-12-22
  • WSL2 installed: yes

### Steps to reproduce

  1. Launch Codex from the Start menu or normal desktop app entry.
  2. Watch the process start in Task Manager.
  3. Within a few seconds, the Codex process exits.

### Expected behavior

Codex should launch normally and remain open.

### Actual behavior

Codex starts and then exits shortly after launch.

Crashpad dump files are created under the Codex app Crashpad reports directory, but I am
not attaching dump files here to avoid sharing personal or sensitive data.

### Diagnostics performed

  • Rebooted Windows.
  • Uninstalled and reinstalled Codex.
  • Changed the default browser to Edge.
  • Logged into ChatGPT in Edge.
  • Temporarily disabled WSL-related Codex settings.
  • Temporarily reset the Codex web profile/local app profile.
  • Temporarily tried disabling Appshots through local requirements.
  • None of the above fixed normal startup.

The desktop log stops shortly after this line:

```text
Appshot hotkey inactive configured=true enabled=true platform=win32

### Workaround

Launching Codex.exe directly with GPU disabled keeps the app running:

Start-Process -FilePath "<Codex install location>\app\Codex.exe" -ArgumentList "--disable-
gpu","--disable-gpu-compositing","--disable-software-rasterizer"

This strongly suggests a GPU initialization or GPU driver compatibility issue.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗