Environment
- Codex for Windows (latest version downloaded from OpenAI)
- Windows 11 25H2
- OS Build: 26200.8894
Problem
Since installing the latest Windows 11 update, the Codex desktop app no longer starts.
Expected behavior
The application should load normally and show the sign-in or main interface.
Actual behavior
The app opens and remains indefinitely on the OpenAI logo. It never progresses beyond the splash screen.
Additional information
- ChatGPT and Codex work normally in the web browser.
- Internet connection is working correctly.
- The problem started immediately after installing the Windows update.
- Restarting Windows did not resolve the issue.
Steps to reproduce
1. Install Windows 11 25H2 Build 26200.8894.
2. Launch the latest Codex Windows app.
3. Observe that the application remains stuck on the OpenAI splash screen indefinitely.
Thank you for investigating this issue.
EricGT
July 20, 2026, 9:12am
2
Welcome back!
You are welcome to discuss Codex issues on the forum, however the official place to report and track them is the GitHub issue tracker for OpenAI Codex .
I had ChatGPT look for the closest related issue and it identified:
opened 01:39AM - 29 Apr 26 UTC
bug
windows-os
app
### What version of the Codex App are you using (From “About Codex” dialog)?
Un… able to access About Codex because the app is stuck on the logo/loading screen.
### What subscription do you have?
ChatGPT Plus
### What platform is your computer?
Windows 11 Home 25H2 Acer Nitro ANV15-51 Intel 13th Gen Core i5-13420H 16GB RAM 64-bit operating system, x64-based processor
### What issue are you seeing?
Codex Windows desktop app is stuck indefinitely on the logo/loading screen.
The app initially opened successfully and allowed me to complete onboarding/setup and add a local project folder. After a Windows update/restart, the desktop app stopped loading and now remains stuck on the Codex logo/loading screen indefinitely.
Codex web works correctly in the browser, so this appears isolated to the Windows desktop app.
Troubleshooting already attempted:
- Restarted Windows multiple times
- Reinstalled Codex from Microsoft Store / OpenAI link
- Killed Codex processes via Task Manager and PowerShell
- Cleared/renamed Codex local state/cache folders:
%APPDATA%\Codex
%USERPROFILE%\.codex
%LOCALAPPDATA%\Codex
%LOCALAPPDATA%\Packages\OpenAI.Codex_...\LocalCache
- Installed/repaired Microsoft Edge WebView2 Runtime
- Checked Windows Defender Firewall; Codex is allowed on private/public networks
- Confirmed Codex web works in browser
Expected result:
Codex desktop app should load to the main interface/login/project screen.
Actual result:
Codex desktop app remains stuck on the logo/loading screen indefinitely.
### What steps can reproduce the bug?
1. Install Codex Windows desktop app.
2. Open Codex and complete initial onboarding/setup.
3. Add a local project folder.
4. Restart Windows after a Windows update.
5. Reopen Codex desktop app.
6. App remains stuck on the Codex logo/loading screen indefinitely.
7. Reinstalling Codex, clearing local cache/state folders, repairing WebView2, and allowing Codex through Windows Defender Firewall does not resolve it.
### What is the expected behavior?
Codex desktop app should launch normally and load the main interface, allowing me to sign in, access projects, and continue working with the local project folder.
### Additional information
Codex web works correctly in the browser using the same account, so the issue appears isolated to the Windows desktop app.
The app worked before the Windows update/restart, then became stuck on the logo/loading screen afterwards.
If that issue matches your problem, consider adding a reaction on the GitHub issue page itself, not just on the forum topic, as reactions on GitHub help the developers gauge impact and prioritize work. Since there are also many other issues like it, give each issue that seems close a reaction to help the developers gauge impact and prioritize work.
If it is not the same issue, try searching the existing GitHub issues for a closer match. If you cannot find one, then open a new issue with as much detail as possible.
The best thing I ever did was switch from Windows to Linux.