[Windows] Codex freezes the desktop and repeatedly crashes after migrating to the new ChatGPT app

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

• #33375
• #33438
• #33466
• #33474

Powered by Codex Action

Same here

What subscription do you have?

Pro

What platform is your computer?

Windows 11 ARM64 running in Parallels on an Apple Silicon Mac.

What issue are you seeing?

The July 16, 2026 Microsoft Store update broke the Codex/ChatGPT desktop application on Windows 11 ARM64.

The application worked normally before the update. Immediately after Microsoft Store installed the update, Codex began opening and then exiting almost immediately.

Reinstalling the application, restarting Windows, resetting the AppX package state, deleting %USERPROFILE%\.codex, disabling GPU acceleration, and clearing the packaged LocalCache did not resolve the issue.

What steps can reproduce the bug?

1. Install or update Codex through Microsoft Store.
2. Confirm that Microsoft Store installs package version 26.707.9981.0.
3. Open Codex from the Windows Start menu.
4. The application briefly launches and then immediately exits.
5. Reopening the application produces the same result.

What is the expected behavior?

Codex should open normally and remain running after being launched from the Windows Start menu.

Updating the application should not make it unusable, and reinstalling the application should restore normal functionality.

Additional information

Microsoft Store package:

• Package name: OpenAI.Codex
• Package version: 26.707.9981.0
• Full package name: OpenAI.Codex_26.707.9981.0_arm64__2p2nqsd0c76g0
• Architecture: ARM64
• Installation time: July 16, 2026 at 12:10:46 AM

The process exits with:

• Decimal exit code: -1066598273
• Hex exit code: 0xC06D007F

The installed executable was:

C:\Program Files\WindowsApps\OpenAI.Codex_26.707.9981.0_arm64__2p2nqsd0c76g0\app\ChatGPT.exe

The application log also reports:

[install-primary-runtime] primary_runtime_update_poll_failed errorMessage="Failed to download primary runtime manifest (404 Not Found)."

WinDbg showed that ChatGPT.exe reached ExitProcess during Chromium startup. It did not record 0xC06D007F as an unhandled exception.

Microsoft Store continued reinstalling the same ARM64 package version even when installation was requested with the x64 architecture option.

Same thing here.

Faulting application name: ChatGPT.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc06d007f
Fault offset: 0x00007ffeb9bc1ada
Faulting process id: 0x6070
Faulting application start time: 0x1DD15029CB0D6F5
Faulting application path: C:\Program Files\WindowsApps\OpenAI.Codex_26.707.12708.0_x64__2p2nqsd0c76g0\app\ChatGPT.exe
Faulting module path: unknown
Report Id: 5e19cf0f-5eb4-4d4f-979b-5e804becb135
Faulting package full name: OpenAI.Codex_26.707.12708.0_x64__2p2nqsd0c76g0
Faulting package-relative application ID: App

And

Fault bucket , type 0
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: OpenAI.Codex_26.707.12708.0_x64__2p2nqsd0c76g0
P2: praid:App
P3: 0.0.0.0
P4: 00000000
P5: StackHash_0000
P6: 0.0.0.0
P7: 00000000
P8: c06d007f
P9: PCH_84
P10: 

Windows 11 Pro - English
Enterprise subscription

Restarting, Repairing, Resetting the application didn't work.

Same here!! My computer stutters, freezes up and I also transfer files, and when I do that after having this app open file transfers become really slow when no chat is active or doing anything. Then after I close the program things go back to normal!

This appo has been messing with my PC's performance a lot.

I have the latest version too after many updates of this new App too and it's been a problem since the switch.
I have Microsoft Windows 11 Home (x64) Build 26200.8875 (25H2).

It was fixed for me after the last update.

Same here; it was the case before the migration and is worse after. The Windows app is extremely unstable; clicking on the skill button freezes the app, and opening the codex app makes my mouse jitter across the entire Windows OS.

It's still not fixed. Codex constantly hangs even after we were told the issue was resolved.
https://status.openai.com/incidents/kmkxgcrp

Uninstalled and reinstalled what seems to be the latest version - no difference.

After the update, it seems worse. It keep freezing and I can barely use the app. I eventually go to use the cli version and wait for the update

I began experiencing an intermittent freezing issue after updating to ChatGPT version 26.715.4045.0 (Inside the app, the version was 26.715.31925 ), released on July 18, 2026, on Windows 11. The application would repeatedly freeze, show as not responding, and then become responsive again.

In Windows Task Manager, I noticed that one of the ChatGPT subprocesses named “ChatGPT” had a “Not responding” status. The other processes, including those with Codex in their names, appeared to be running normally.

I tried several troubleshooting methods, but none resolved the issue. The solution that worked for me was to uninstall the latest version and reinstall the older version 26.707.9981.0 (Inside the app, the version is 26.707.72221), released on July 14, 2026.

Since downgrading to the older version, I have not experienced the freezing issue anymore.

This is ridiculous. I guess we have to wait until Monday for people to show up.

I began experiencing an intermittent freezing issue after updating to ChatGPT version 26.715.4045.0 (Inside the app, the version was 26.715.31925 ), released on July 18, 2026, on Windows 11. The application would repeatedly freeze, show as not responding, and then become responsive again. In Windows Task Manager, I noticed that one of the ChatGPT subprocesses named “ChatGPT” had a “Not responding” status. The other processes, including those with Codex in their names, appeared to be running normally. I tried several troubleshooting methods, but none resolved the issue. The solution that worked for me was to uninstall the latest version and reinstall the older version 26.707.9981.0 (Inside the app, the version is 26.707.72221), released on July 14, 2026. Since downgrading to the older version, I have not experienced the freezing issue anymore.

Because of Auto-update (there is no option to disable it), after the restart, ChatGPT installs the latest version automatically, and I need to uninstall and install the old version again and again and again /:

I have another reproducible data point for this freeze on Windows 11, using package OpenAI.Codex_26.715.4045.0_x64__2p2nqsd0c76g0.

In my case the trigger appears to be a HyperX Cloud III USB headset (VID_03F0&PID_089D), or more specifically its USB connection/control interface.

Observed sequence:

1. The Codex/ChatGPT window becomes intermittently responsive, then browser scrolling and the system mouse become very slow/jittery.
2. I can sometimes type one character after it briefly recovers.
3. Roughly five seconds later the app hangs again, sometimes for about a minute.
4. System CPU, disk, GPU, DPC, and interrupt load were normal during the freeze; this did not look like ordinary CPU saturation.
5. Unplugging my keyboard did not recover the already-frozen app.
6. Unplugging only the HyperX headset recovered the already-running app immediately, without restarting Codex.
7. After a reboot where the headset was not initially detected, Codex worked normally. Reconnecting the headset made its audio work, and the hangs then began again.
8. I moved the headset from the rear USB port to a top/front USB port, and Codex has remained responsive so far.

The USB topology changed meaningfully with the port move:

• Original rear port: headset connected directly on the root-controller path ending in USB(3)
• Current top port: headset is downstream of a Generic USB 2.1 hub on the path ending in USB(7)#USB(4)

The headset is a composite USB device. Its audio interface is separate from an MI_03 HID interface containing consumer-control and vendor-defined HID collections. That likely carries headset buttons/mute/status/configuration rather than audio itself.

One additional clue: the installed Codex package includes node-hid 3.3.0 and a native HID.node module under the bundled @worklouder/device-kit-oai dependency. I have not captured the exact runtime call stack proving that this module is where the hang occurs, but it makes a HID enumeration/control-call path plausible. A slow USB/HID driver call would also fit the otherwise-idle system and the immediate recovery when the headset is disconnected.

Games and normal audio playback did not show this problem, which may simply be because they use the audio endpoint and do not enumerate or query the headset's vendor HID control interface.

The port change is a reliable workaround so far, but it may only avoid the problematic USB-controller/hub state. It would still be valuable for the app to keep HID enumeration/report calls off the Electron main/UI thread and apply timeouts/cancellation around native device calls.

This appears consistent with the separate controlled HID observations in #33780.

Got an update about an hour ago. Been fine since.... so far....