Codex for Windows stuck on loading spinner after update; unable to access app even when already logged in #48615

Since the recent Codex update, the application gets stuck on the loading screen every time it is relaunched after a full exit; it fails to load even after waiting more than two minutes.
Currently, the only workaround is to fully exit the app, delete the auth.json file from the .codex user directory, and then relaunch and log in again. However, this method is unreliable—sometimes the process must be repeated several times to gain access—which is disrupting normal usage.
App versions:

• In-app version: 26.924.22138, build 11645
• Windows installer version: 26.924.2738.0
  Reproduction steps:

1. Log in to Codex and access the main interface normally.
2. Fully exit the app and immediately relaunch it.
3. The app displays a continuous loading animation and fails to load the main interface.
   Another key observation: If a working window is kept open and a second window is launched via "File -> New Window," the second window also gets stuck on the loading spinner, while the original window continues to function normally.
   Troubleshooting steps taken:

• The issue persists after rebuilding the Cache and Code Cache.
• Logs from the stuck window indicate successful account reading, login status checks, and server connections, but show no record of the main interface completing its load.
• All 14,020 UI script and style files in the installation package passed the internal integrity check.
• No clear evidence of login token refresh failure was found in the checked logs.
  The issue was reproduced on September 27, 2026, at 11:53 (Beijing Time) when opening a new window. A diagnostic package has been prepared, containing the reproduction time, version details, and key log excerpts, but excluding login tokens or chat content.
  The issue is currently suspected to be related to "window initialization while already logged in" following the update, though the specific cause remains unconfirmed. Please assist in investigating this and provide a fix to avoid the need to delete login files and re-authenticate upon every launch.