›_ Codex Issues
Codex Issues / #33909

Windows desktop app hangs immediately after launch after updating to 26.715.2305.0 (Application Hang 1002 / MoAppHang)

Resolved 💬 6 comments Opened Jul 17, 2026 by windsel Closed Jul 18, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.715.2305.0

Application version: 150.0.7871.124

Package: OpenAI.Codex_26.715.2305.0_x64__2p2nqsd0c76g0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

  • Windows 11 Pro
  • Version 25H2
  • OS Build 26200.8655
  • x64
  • CPU: Intel Core i7-12700KF
  • GPU: NVIDIA RTX 3070
  • RAM: 32 GB

What issue are you seeing?

Immediately after updating the Windows desktop app to version 26.715.2305.0, the application became unusable.

The app freezes within a few seconds of launch. Windows marks it as Not Responding, and the UI does not recover.

The previous version worked normally on the same machine. Reinstalling the current version does not resolve the problem.

This prevents access to existing Codex projects during active development work.

What steps can reproduce the bug?

  1. Install or update to the Windows desktop package OpenAI.Codex_26.715.2305.0_x64.
  2. Launch the ChatGPT/Codex desktop app.
  3. Wait a few seconds.
  4. The app becomes unresponsive before meaningful interaction is possible.

The freeze happens immediately after startup on every launch.

What is the expected behavior?

The app should complete startup normally and allow access to existing Codex projects.

Additional information

The issue began immediately after the update. The prior desktop version worked correctly on the same hardware and Windows installation.

Troubleshooting already performed:

  • Restarted Windows.
  • Reinstalled the desktop application from the official OpenAI website.
  • Renamed %USERPROFILE%\.codex to force a clean startup.
  • Signed in again after the clean startup.
  • Restored the original .codex directory.

Renaming .codex allowed the application to launch once as a fresh installation. Restoring the original .codex directory restored the existing Codex projects, confirming that the project data was still present locally. However, the app again froze immediately after launch.

Task Manager observations while the app is frozen:

  • CPU usage stays near 0%.
  • Memory usage is approximately 400–450 MB.
  • Disk activity is effectively idle.
  • Windows reports the app as Not Responding.

Windows Event Viewer records the following:

Application Hang
  • Log: Application
  • Source: Application Hang
  • Event ID: 1002
  • Task category: Hanging Events
  • Application: ChatGPT.exe
  • Application version: 150.0.7871.124
  • Executable path: C:\Program Files\WindowsApps\OpenAI.Codex_26.715.2305.0_x64__2p2nqsd0c76g0\app\ChatGPT.exe
  • Package: OpenAI.Codex_26.715.2305.0_x64__2p2nqsd0c76g0
  • Package relative application ID: App
  • Hang type: Unknown
Windows Error Reporting
  • Event ID: 1001
  • Event name: MoAppHang
  • Fault bucket: 2020343198852172000
  • Bucket type: 5
  • Package: OpenAI.Codex_26.715.2305.0_x64__2p2nqsd0c76g0
  • Application version: 150.0.7871.124
  • Hashed bucket: 61cf54cf289d829fbc09b36f63f5c8e0
  • Report status: 268435456

No personal files or .codex data are attached to this report.

The local project data appears intact, but the desktop client is unusable and blocks access to those projects.

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 3 days ago

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

  • #33780
  • #33873

Powered by Codex Action

Bluestar2k7 · 3 days ago

Confirmed trigger and immediate workaround

The desktop-app hang is now reproducibly tied to the HID/USB accessory path, not to a Codex project, account, or the Codex CLI.

After temporarily disconnecting the Corsair wireless adapters, the Windows desktop app was restarted. Its visible main window remained responsive for more than 65 seconds and no new Application Hang (Event ID 1002) or MoAppHang was recorded.

The affected system had both of the following present before the workaround:

  • A Corsair HID interface in an error state: VID_1B1C&PID_1B6D&MI_02
  • USB-hub identifiers VID_05E3&PID_0610 and VID_05E3&PID_0612

Those identifiers and the recovery behavior match the current HID-enumeration reports in #33780 and #33924. The likely trigger is synchronous HID enumeration on the desktop app's main process; an unresponsive HID endpoint blocks the UI.

Working workaround: keep the affected Corsair wireless adapters / related USB-switch path disconnected while using the desktop app, or connect required input devices directly to the PC. Reconnecting the affected path may reintroduce the hang.

Additional anonymous reproduction data:

  • Windows 11 Insider build 26200.8875
  • ChatGPT.exe: 150.0.7871.124
  • Package: OpenAI.Codex
  • Reproduces in both Stable and Beta; the update to 26.715.3651.0 did not resolve it before the HID workaround.
  • Web ChatGPT and Codex CLI work normally on the same installation and account.
  • GPU-disable launch and temporary plugin disabling did not resolve the desktop-app hang.
  • No correlated display-driver, WHEA, disk/NTFS, Defender, Code Integrity, firewall, or proxy failures were found in Event Viewer.

No personal files, local paths, project data, account data, or logs are attached.

Bluestar2k7 · 3 days ago

One additional isolation point: Codex CLI works normally on the same Windows installation and account. The failure therefore appears limited to the Windows desktop app/UI process rather than authentication, account access, local projects, or the Codex CLI core.

windsel · 3 days ago

Resolution / workaround confirmed

I was able to restore normal desktop-app behavior by fully power-cycling the connected USB/HID devices.

Test sequence

  1. Closed all ChatGPT/Codex processes in Task Manager.
  2. Disconnected all nonessential USB devices.
  3. Launched Codex with only the keyboard and mouse connected.
  4. The app opened normally and remained responsive.
  5. Reconnected the USB microphone and tested again — no lag.
  6. Reconnected the drawing tablet and restarted its tablet software — no lag.
  7. Reconnected the remaining USB devices, including a multi-function card reader / USB expansion device with storage and multiple USB ports — no lag.
  8. Returned to the original full hardware/software setup.

The app is now working normally with all original devices reconnected.

Conclusion

This strongly suggests that one USB/HID endpoint or driver had entered a temporary stuck state. Codex then blocked while enumerating HID/accessory devices during startup. Disconnecting and reconnecting the devices reset the affected endpoint or driver state.

No single peripheral could be isolated as the permanent trigger because the issue did not return after all devices were reconnected. The effective workaround was a full USB/HID disconnect and reconnect cycle rather than permanently removing one device.

Practical workaround

If the startup hang returns:

  • Fully close all ChatGPT/Codex processes.
  • Disconnect nonessential USB/HID devices.
  • Launch Codex with only a basic keyboard and mouse.
  • Reconnect devices one at a time.

This appears consistent with the HID-enumeration problem documented in #33780. Since the app is now working again and this report appears to be a duplicate of that root issue, I am closing this issue as a duplicate.

No personal files, local paths, account data, or project contents are included in this update.

craiga24 · 2 days ago

I have been having the same problem after hours of pulling my hair out it turned out to be my K55 corsair keyboard causing the issues. I unplugged it an plugged in a wireless keyboard and no hang or crash in 2 hours (this only started happening after the latest update for me)

0-Press · 1 day ago

Same startup hang and MoAppHang/Application Hang 1002.

Windows:
Microsoft Windows NT 10.0.26200.0 x64
Windows 11 Home 25H2, build 26200.8875

Hardware:
Corsair mouse, exact model currently unknown

Package originally affected:
OpenAI.Codex_26.715.2305.0_x64__2p2nqsd0c76g0

The issue persists after later Microsoft Store updates.
Fresh app profile, reinstall, GPU-disabled launch flags, and app updates did not resolve it.