openai / openai/codex

Windows desktop app 26.825.5331.0 hangs before creating a window (MoAppHang 1002)

Open
#41,551 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app app-server bug windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of Codex CLI is running?

0.149.1

What subscription do you have?

ChatGPT Plus

Which model were you using?

N/A – desktop app hangs before UI; CLI default is gpt-5.6-sol

What platform is your computer?

Windows 11 10.0.26200 x64

What terminal emulator and version are you using (if applicable)?

Windows Terminal with Windows PowerShell 5.1

Codex doctor report
The full codex-doctor-report.json and logs are included in uploaded thread 01a04e61-7032-7371-92c8-626db7145142. Codex Doctor v0.149.1 summary: 19 ok, 1 idle, 4 notes, 3 warnings, 1 failure.
What issue are you seeing?

The Windows ChatGPT/Codex desktop app package OpenAI.Codex 26.825.5331.0 launches multiple ChatGPT.exe processes but never creates or displays a window. Windows Event Viewer records Application Hang Event ID 1002 / MoAppHang for ChatGPT.exe 151.0.7922.174. Package activation succeeds, but startup logging stops at AppServerConnection state=connecting.

What steps can reproduce the bug?

Uploaded thread: 01a04e61-7032-7371-92c8-626db7145142

What is the expected behavior?

The desktop app should complete the app-server connection and display its main window after launch.

Additional information

Troubleshooting already performed: Windows Repair and Reset, complete Microsoft Store uninstall/reinstall, clean .codex and AppData directories, disabled GPU launch, clean user-data directory, no-proxy launch, successful Codex CLI authentication, unelevated Windows sandbox mode, and temporary Microsoft Defender process exclusions for nine Codex executables. All tests produced the same hang. The Defender exclusions were removed after testing. No third-party DLL injection was found. ChatGPT web and Codex CLI work normally.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the uploaded codex-doctor-report.json and logs in thread 01a04e61-7032-7371-92c8-626db7145142, then review the startup path around AppServerConnection state=connecting. Reproduce on Windows 11 and use Event Viewer’s MoAppHang 1002 record for comparison. Done means the app completes the app-server connection and displays its main window.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.