›_ Codex Issues
Codex Issues / #27581

Codex Desktop closes during normal work on Windows; Event Viewer shows Application Hang 1002

Open 💬 4 comments Opened Jun 11, 2026 by bakiev
💡 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.608.1337.0 Codex.exe version shown in Event Viewer: 148.0.7778.179

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex Desktop repeatedly becomes unresponsive on Windows and is closed by Windows as an Application Hang.

This is not showing as an Application Error 1000 crash for windows-updater.node on my machine. I found windows-updater.node, but Event Viewer / Reliability Monitor shows repeated Application Hang 1002 events for Codex.exe.

Codex package:

OpenAI.Codex_26.608.1337.0_x64__2p2nqsd0c76g0

Codex.exe version from Event Viewer:

148.0.7778.179

Path to windows-updater.node:

C:\Program Files\WindowsApps\OpenAI.Codex_26.608.1337.0_x64__2p2nqsd0c76g0\app\resources\native\windows-updater.node

Reliability Monitor / Event Viewer shows repeated Application Hang 1002 events:

2026-06-08 12:02:26
2026-06-07 15:17:33
2026-06-04 10:28:17
2026-05-27 14:13:31

Event message:

Program Codex.exe version 148.0.7778.179 stopped interacting with Windows and was closed.

I do not see an Application Error 1000 event for windows-updater.node on my machine.

---

What steps can reproduce the bug?

I cannot reproduce it reliably on demand yet. The issue happens during normal use of Codex Desktop on Windows.

Observed behavior:

  1. Open Codex Desktop.
  2. Use the app normally.
  3. After some time, Codex becomes unresponsive.
  4. Windows closes the application and records an Application Hang 1002 event.

I have seen this multiple times across different dates and versions.

---

What is the expected behavior?

Codex Desktop should remain responsive and should not be closed by Windows as an Application Hang. If an internal update check, network request, or background operation fails, the app should handle the failure without freezing.

---

Additional information

The issue appears to be a repeated hang rather than a direct native-module crash on my machine.

Relevant Event Viewer / Reliability Monitor entries:

TimeGenerated   : 08.06.2026 12:02:26
SourceName      : Application Hang
EventIdentifier : 1002
ProductName     : Codex.exe
Message         : Program Codex.exe version 148.0.7778.179 stopped interacting with Windows and was closed.

TimeGenerated   : 07.06.2026 15:17:33
SourceName      : Application Hang
EventIdentifier : 1002
ProductName     : Codex.exe
Message         : Program Codex.exe version 148.0.7778.179 stopped interacting with Windows and was closed.

TimeGenerated   : 04.06.2026 10:28:17
SourceName      : Application Hang
EventIdentifier : 1002
ProductName     : Codex.exe
Message         : Program Codex.exe version 148.0.7778.179 stopped interacting with Windows and was closed.

TimeGenerated   : 27.05.2026 14:13:31
SourceName      : Application Hang
EventIdentifier : 1002
ProductName     : Codex.exe
Message         : Program Codex.exe version 2962.0.0.0 stopped interacting with Windows and was closed.

I can provide a dump file if the hang happens again.

What steps can reproduce the bug?

cannot reproduce it reliably on demand yet.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 2 months ago

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

  • #26401
  • #27437
  • #27377

Powered by Codex Action

bakiev · 2 months ago

I reviewed the potential duplicates.

#27437 looks related because it is also about Codex becoming unresponsive on Windows, but my case is slightly different: Codex is not only temporarily “Not Responding” — Windows closes the application during normal work.

My Event Viewer / Reliability Monitor entries show repeated Application Hang 1002 events for Codex.exe.

Observed events:

2026-06-08 12:02:26 — Application Hang 1002 — Codex.exe 148.0.7778.179
2026-06-07 15:17:33 — Application Hang 1002 — Codex.exe 148.0.7778.179
2026-06-04 10:28:17 — Application Hang 1002 — Codex.exe 148.0.7778.179
2026-05-27 14:13:31 — Application Hang 1002 — Codex.exe 2962.0.0.0

Event message:

Program Codex.exe version 148.0.7778.179 stopped interacting with Windows and was closed.

So this is not just a short UI freeze on my machine. Codex becomes unresponsive and Windows closes it while I am working.

#26401 seems less related because it describes micro-freezes.
#27377 seems less related because I do not see evidence that my issue is specifically stuck at “Update downloading”.

If maintainers consider this a duplicate of #27437, I am fine with closing this issue, but I wanted to provide the Application Hang 1002 details separately.

AxelDeathBR · 2 months ago

The staff at Open are very irresponsible. I've been having this problem for days, wasting credits, and they haven't resolved this annoying issue. It keeps closing on its own for no reason.

Culacco · 2 months ago

I can reproduce a very similar Windows desktop hang on a Windows 10 22H2 x64 machine.

  • Codex MSIX package: OpenAI.Codex_26.616.10790.0_x64__2p2nqsd0c76g0
  • Codex.exe version: 149.0.7827.115
  • Windows Error Reporting event: MoAppHang
  • Event Viewer: Application Hang Event ID 1002; Windows reports that Codex.exe stopped interacting with Windows and was closed.
  • I do not have a corresponding Application Error 1000 event or a Crashpad stack trace for this occurrence.

The hang happened immediately after an app update/relaunch. There is also a strong environment correlation with a third-party enterprise sync/security client that uses a global Windows hook: with that client running, Codex repeatedly hung during startup; after stopping the client, Codex was able to launch. I have not captured a dump proving DLL injection or causality, so I am reporting this only as a correlation, not as a confirmed root cause.

This looks closer to the Application Hang 1002 pattern in this issue than to a conventional native crash.