Root Cause Identified – CyberArk EPM Caused Codex Desktop App to Be Stuck on Logo Screen

Open 💬 2 comments Opened Jun 27, 2026 by edgarchou

What version of the Codex App are you using (From “About Codex” dialog)?

26.616.66310

What subscription do you have?

ChatGPT Enterprise

What platform is your computer?

Windows 11 x64 ( 23H2/24H2)

What issue are you seeing?

After updating Codex Desktop App to 26.616.5445.0 (released around June 20, 2026), the application no longer starts correctly.

The app remains stuck on the OpenAI/Codex logo screen and never reaches the sign-in page or main interface.

After extensive troubleshooting, I found that the issue is related to CyberArk Endpoint Privilege Manager (EPM).

Uninstalling CyberArk EPM immediately resolved the issue. No other system changes were required.

This indicates a compatibility regression introduced in version 26.616.5445.0, where Codex Desktop App appears to conflict with CyberArk EPM.

What steps can reproduce the bug?

  1. Install CyberArk Endpoint Privilege Manager (EPM).
  2. Install Codex Desktop App.
  3. Launch Codex Desktop App.
  4. Observe that the application remains stuck on the logo/loading screen.
  5. Uninstall CyberArk EPM.
  6. Launch Codex Desktop App again.
  7. The application starts normally.

What is the expected behavior?

Codex Desktop App should start normally regardless of whether CyberArk Endpoint Privilege Manager (EPM) is installed.

Additional information

Previous version worked correctly.
The issue started immediately after updating to 26.616.5445.0 on June 20, 2026.
Windows 11 x64.
CyberArk Endpoint Privilege Manager (EPM) was installed.
Reinstalling Codex did not resolve the problem.
Clearing local data did not resolve the problem.
Restarting Windows did not resolve the problem.
After uninstalling CyberArk EPM, Codex Desktop App launched normally.

This appears to be a compatibility issue between Codex Desktop App (possibly Microsoft Edge WebView2 or another startup component) and CyberArk EPM.

Since the previous version worked correctly and the issue began immediately after upgrading to 26.616.5445.0, this may be a regression introduced in that release.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗