Description
After updating the Windows desktop app, the application gets stuck indefinitely on the loading screen.
The browser version of ChatGPT works normally on the same PC.
The issue is reproducible on both my normal home WAN and a mobile hotspot.
Environment
- Platform: Windows
- Store package:
OpenAI.Codex 26.924.2738.0
- Build number:
11645
- Build commit:
2e782921399a788a842b74ee1944a2e1e6e003a1
- App-server version:
0.158.0-alpha.2.1
- Windows osRelease from log:
10.0.26200
Reproduction
- Launch the Windows desktop app.
- The main window appears.
- The loading spinner remains indefinitely.
- The home UI / composer never becomes available.
Already tried:
- Exit and restart
- Windows App Repair
- Windows App Reset
- Uninstall/reinstall from Microsoft Store
- DNS cache flush
- Different DNS servers
- Home WAN and mobile hotspot
The browser version continues to work normally.
Latest reproduction timestamp
2026-09-27 00:15:07 +09:00
Relevant desktop log
The local app-server initializes successfully, authentication succeeds, and ChatGPT pub/sub opens/subscribes. The home/bootstrap request is issued, but startup eventually times out.
ext 2026-09-26T15:15:08.208Z info [AppServerConnection] initialize_handshake_result durationMs=211 initializeRequestId=__codex_initialize__ outcome=success transportKind=stdio 2026-09-26T15:15:08.208Z info [AppServerConnection] Codex CLI initialized 2026-09-26T15:15:09.834Z info [electron-message-handler] [chatgpt-account-lookup] completed accountInfoHttpStatus=undefined accountsHttpStatus=undefined authenticatedAccountPresent=true authMethod=chatgpt failureType=undefined hasEverErrored=false rendererWebContentsId=1 rendererWindowAppearance=primary rendererWindowFocused=true rendererWindowId=1 rendererWindowVisible=true result=succeeded windowType=electron 2026-09-26T15:15:10.321Z info [electron-fetch-handler] codex-home request hostId=undefined 2026-09-26T15:15:12.186Z info [electron-message-handler] chatgpt_pubsub_transport_opened rendererWebContentsId=1 rendererWindowAppearance=primary rendererWindowFocused=true rendererWindowId=1 rendererWindowVisible=true topicCount=1 windowFocused=true 2026-09-26T15:15:12.286Z info [electron-message-handler] chatgpt_pubsub_topic_subscribed catchupCount=0 hadPreviousOffset=false recovered=false rendererWebContentsId=1 rendererWindowAppearance=primary rendererWindowFocused=true rendererWindowId=1 rendererWindowVisible=true topicId=resource-updates 2026-09-26T15:17:08.958Z info [electron-message-handler] client.performance.span backgroundDurationMs=0 buildCommitSha=2e782921399a788a842b74ee1944a2e1e6e003a1 buildNumber=11645 clientPlatform=win32 durationMs=121058.3 hostStartupPhaseDurationsMs={"bootstrap handoff complete":163,"main app.whenReady resolved":0,"registered app protocol":0,"local data migrations completed":0,"registered deep link protocol":0,"startup window revealed":330,"local app-server sqlite initialized":92,"window context initialized":93,"application menu refreshed":5,"bundled plugins reconcile checked":1} hostType=electron initialSurface=home marksMs={"renderer_entry_evaluated":1055.3,"host_services_ready":1073.5,"renderer_ready":1212.6,"host_startup_ready":1217.8,"settings_ready":1563.1} name=app_start outcome=failure processToPreloadDurationMs=3345.137939453125 reason=timeout rendererWebContentsId=1 rendererWindowAppearance=primary rendererWindowFocused=false rendererWindowId=1 rendererWindowVisible=true samplingReason=Bootstrap:Recognized samplingRuleId=1kYHoU5I4stzVcHY9M7LZK:100.00:4 spanId=undefined timingQuality=foreground traceId=undefined wallDurationMs=121057.3
Additional network observations
Unauthenticated curl requests to these endpoints return 403 Forbidden with Cf-Mitigated: challenge:
https://chatgpt.com/https://auth.openai.com/https://chatgpt.com/backend-api/me
However, the same curl behavior occurs on both the home WAN and the mobile hotspot, so those curl results do not distinguish the failing and working network cases.
Also:
ws.chatgpt.com:443 is reachable.- A WebSocket upgrade attempt to
wss://ws.chatgpt.com/ reaches the server and receives HTTP 404 for / rather than timing out.
- The application log shows
chatgpt_pubsub_transport_opened and chatgpt_pubsub_topic_subscribed.
Expected behavior
The desktop application should finish bootstrap and display the normal home/composer UI.
Actual behavior
The application remains on the loading spinner and records name=app_start outcome=failure reason=timeout after approximately 120 seconds.
Notes
This began immediately after the desktop app update.
In-app / feedback cannot be submitted because the app never gets far enough to display the composer.
I can provide additional desktop logs or timestamps if needed.
Description
After updating the Windows desktop app, the application gets stuck indefinitely on the loading screen.
The browser version of ChatGPT works normally on the same PC.
The issue is reproducible on both my normal home WAN and a mobile hotspot.
Environment
OpenAI.Codex 26.924.2738.0116452e782921399a788a842b74ee1944a2e1e6e003a10.158.0-alpha.2.110.0.26200Reproduction
Already tried:
The browser version continues to work normally.
Latest reproduction timestamp
2026-09-27 00:15:07 +09:00Relevant desktop log
The local app-server initializes successfully, authentication succeeds, and ChatGPT pub/sub opens/subscribes. The home/bootstrap request is issued, but startup eventually times out.
ext 2026-09-26T15:15:08.208Z info [AppServerConnection] initialize_handshake_result durationMs=211 initializeRequestId=__codex_initialize__ outcome=success transportKind=stdio 2026-09-26T15:15:08.208Z info [AppServerConnection] Codex CLI initialized 2026-09-26T15:15:09.834Z info [electron-message-handler] [chatgpt-account-lookup] completed accountInfoHttpStatus=undefined accountsHttpStatus=undefined authenticatedAccountPresent=true authMethod=chatgpt failureType=undefined hasEverErrored=false rendererWebContentsId=1 rendererWindowAppearance=primary rendererWindowFocused=true rendererWindowId=1 rendererWindowVisible=true result=succeeded windowType=electron 2026-09-26T15:15:10.321Z info [electron-fetch-handler] codex-home request hostId=undefined 2026-09-26T15:15:12.186Z info [electron-message-handler] chatgpt_pubsub_transport_opened rendererWebContentsId=1 rendererWindowAppearance=primary rendererWindowFocused=true rendererWindowId=1 rendererWindowVisible=true topicCount=1 windowFocused=true 2026-09-26T15:15:12.286Z info [electron-message-handler] chatgpt_pubsub_topic_subscribed catchupCount=0 hadPreviousOffset=false recovered=false rendererWebContentsId=1 rendererWindowAppearance=primary rendererWindowFocused=true rendererWindowId=1 rendererWindowVisible=true topicId=resource-updates 2026-09-26T15:17:08.958Z info [electron-message-handler] client.performance.span backgroundDurationMs=0 buildCommitSha=2e782921399a788a842b74ee1944a2e1e6e003a1 buildNumber=11645 clientPlatform=win32 durationMs=121058.3 hostStartupPhaseDurationsMs={"bootstrap handoff complete":163,"main app.whenReady resolved":0,"registered app protocol":0,"local data migrations completed":0,"registered deep link protocol":0,"startup window revealed":330,"local app-server sqlite initialized":92,"window context initialized":93,"application menu refreshed":5,"bundled plugins reconcile checked":1} hostType=electron initialSurface=home marksMs={"renderer_entry_evaluated":1055.3,"host_services_ready":1073.5,"renderer_ready":1212.6,"host_startup_ready":1217.8,"settings_ready":1563.1} name=app_start outcome=failure processToPreloadDurationMs=3345.137939453125 reason=timeout rendererWebContentsId=1 rendererWindowAppearance=primary rendererWindowFocused=false rendererWindowId=1 rendererWindowVisible=true samplingReason=Bootstrap:Recognized samplingRuleId=1kYHoU5I4stzVcHY9M7LZK:100.00:4 spanId=undefined timingQuality=foreground traceId=undefined wallDurationMs=121057.3Additional network observations
Unauthenticated curl requests to these endpoints return
403 ForbiddenwithCf-Mitigated: challenge:https://chatgpt.com/https://auth.openai.com/https://chatgpt.com/backend-api/meHowever, the same curl behavior occurs on both the home WAN and the mobile hotspot, so those curl results do not distinguish the failing and working network cases.
Also:
ws.chatgpt.com:443is reachable.wss://ws.chatgpt.com/reaches the server and receives HTTP 404 for/rather than timing out.chatgpt_pubsub_transport_openedandchatgpt_pubsub_topic_subscribed.Expected behavior
The desktop application should finish bootstrap and display the normal home/composer UI.
Actual behavior
The application remains on the loading spinner and records
name=app_start outcome=failure reason=timeoutafter approximately 120 seconds.Notes
This began immediately after the desktop app update.
In-app
/feedback cannot be submitted because the app never gets far enough to display the composer.I can provide additional desktop logs or timestamps if needed.