Hello,
I have been unable to use the ChatGPT desktop application on Windows for the past few days.
The application was working perfectly until recently. Now, whenever I launch it, it freezes almost immediately. As soon as I click anywhere in the application or try to interact with one of my Codex projects, the entire window becomes unresponsive.
Windows then displays the following message:
“Codex is not responding.”
The issue occurs every single time I open the application, making it completely unusable.
Troubleshooting already attempted
I have already tried the following:
- Completely closing all ChatGPT and Codex processes;
- Restarting my computer;
- Repairing the application through Windows Settings;
- Resetting the application through Windows Settings;
- Completely uninstalling the application;
- Reinstalling the latest version from the Microsoft Store.
Unfortunately, none of these steps resolved the issue.
System information
- Operating system: Windows 11 Pro
- Windows version: 25H2
- System architecture: 64-bit
- Installed application package: OpenAI.Codex
- Application version: 26.715.4045.0
- ChatGPT in a web browser: Working normally
- Issue frequency: Every time the desktop application is launched
- Approximate date the issue started: A few days ago (2-3)
- Exact Windows message: “Codex is not responding”
Has anyone else experienced this problem ?
Thank you very much for your help.
I have had the same issue for 4 days, and have gone through all of the same issues and diagnostic routes you have done. While I have no solution (and I need one myself), I wanted to add a couple of extra things I noticed about the behavior:
It usually hangs less on startup of the computer, usually taking a prompt before starting minute-long freezing.
On one reinstall where I forced the app to not have my login on download, the login process was issue free until the moment where I actually got into the app logged in.
Changing what plugins are enabled seems to massively change how long/often it hangs, but with no discernable reliable patterns.
Further update: I now have a reproducible trigger and a reliable temporary recovery workaround.
The issue strongly points to synchronous HID enumeration involving my Corsair K55 keyboard:
- Unplugging my webcam and other USB devices from the same hub did not recover the frozen app.
- Unplugging only the K55 immediately unfroze the already-running Codex/ChatGPT window.
- The freeze also recurred with the K55 connected directly to a motherboard USB port, so the external hub is not required to trigger it.
- A fresh .codex profile, reconnecting the account, Windows repair/reset, reinstalling, and subsequent app updates did not fix the underlying issue.
I then tested a targeted software restart of only the physical K55 PnP device. It recovers the frozen UI immediately without restarting Codex or physically unplugging the keyboard. I have successfully used this recovery five times so far.
Run this from an elevated PowerShell window:
$pattern = 'USB\VID_1B1C&PID_1B3D\*'
$expected = 'Corsair Gaming K55 RGB Keyboard'
$devices = @(
Get-PnpDevice -PresentOnly -Class USB |
Where-Object InstanceId -like $pattern |
Where-Object {
$p = Get-PnpDeviceProperty -InstanceId $_.InstanceId `
-KeyName 'DEVPKEY_Device_BusReportedDeviceDesc' `
-ErrorAction SilentlyContinue
$p.Data -eq $expected
}
)
if ($devices.Count -ne 1) {
throw "Safety stop: expected exactly one physical K55, found $($devices.Count)."
}
& "$env:SystemRoot\System32\pnputil.exe" /restart-device $devices[0].InstanceId
if ($LASTEXITCODE -ne 0) {
throw "PnPUtil failed with exit code $LASTEXITCODE."
}
The keyboard briefly disconnects and reconnects. This exact VID/PID and description are for the Corsair K55 only; other devices require their own verified identifiers.
Technical details and the same controlled observations are also documented in the openai/codex GitHub repository, issue #33780, comment 5020258667.
This is only a recovery workaround, not the underlying fix. The app should prevent HID enumeration or a slow HID driver call from blocking the Electron main/UI thread.
the problem come to usb devices (keyboard mouses etc…) me its my keyboard , codex make me a script , when codex not responding, i use this script for kill my usb device and restart it , … codex unlock instantanly ,
Thank you very much to everyone who helped investigate this, especially Andrew_Rosso and Enguerrand_Kalfaian for identifying the USB/HID trigger.
I can now confirm that I was able to reproduce the same behavior with my Corsair K70 keyboard:
-
With the K70 connected, the ChatGPT/Codex Windows application froze almost immediately and displayed “Not responding.”
-
Unplugging only the K70 instantly unfroze the already-running application.
-
Reconnecting the keyboard caused the application to freeze again.
-
Current application version after the update: OpenAI.Codex 26.715.7063.0
This strongly confirmed that the issue was related to the keyboard’s USB/HID interface rather than my Codex projects, configuration, Windows user profile, or account.
I had already tested all of the following without success:
-
Repairing and resetting the application;
-
Completely uninstalling and reinstalling it;
-
Using a clean .codex profile and config.toml;
-
Testing from a completely new Windows user profile;
-
Repairing the Windows App Runtime.
Just before installing today’s ChatGPT desktop client update, unplugging the K70 was still the only action that immediately stopped the freezing.
I then reconnected the keyboard and installed the latest ChatGPT desktop update. Since that update, the application appears to be working normally with the K70 still connected, and the freezing has not returned so far.
I have also successfully restored my local Codex projects, sessions, and archived sessions from my .codex.backup folder, and everything currently appears to be working correctly.
For now, the issue seems resolved, although I will continue monitoring it before considering it permanently fixed. It is possible that today’s client update included a fix or mitigation for the HID enumeration issue.
Thank you again for the help and for sharing the K55 findings. Without that information, I would probably still be investigating unrelated Windows, runtime, or configuration issues.
Thank you very much for the detailed follow-up and for confirming the same behavior with your Corsair K70.
I can confirm that the issue is now fully resolved on my side as well after installing the latest desktop update. The app remains responsive with my Corsair K55 connected, the freezing has not returned, and I have not needed to use the PnP recovery script since the update.
I’m glad the K55 tests helped isolate the USB/HID trigger. Thank you again for your testing and for sharing your results.