Skip to content

Windows app (26.924.2738.0) hangs on startup spinner after sign-in; worked earlier on the same version #49265

Open

Description

@andrewbushek-blip

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

26.924.2738.0 (package OpenAI.Codex, internal AppVersion 26.924.22138)

What subscription do you have?

ChatGPT Business / Team

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64 (Windows 11 Pro)

What issue are you seeing?

The Windows app opens to the loading spinner and never gets past it. When signed out, the sign-in screen renders normally. Right after signing in, it goes back to the spinner indefinitely. ChatGPT web and the Codex CLI work normally on the same machine and account.

The app loaded normally at 2026-09-29 04:14 UTC on this same version. After that, the log showed Codex app-server process is not available, a thread/resume timeout (mcp_request_timeout), and a scheduled primary-runtime update to bundle 26.904.11930. Every launch since 04:15 UTC hangs.

In the hung launches, the renderer logs [statsig-refresh-diagnostics] React root render requested, but never [startup][renderer] app routes mounted. It never calls model/list, thread/list, or plugin/list. [sparkle] in_app_updates_policy_wait_started is never followed by in_app_updates_policy_latch. The app-server answers every request it gets with no errors (account/read, getAuthStatus, config/read, configRequirements/read, skills/list, windowsSandbox/readiness), and ChatGPT pubsub connects and subscribes.

What steps can reproduce the bug?

  1. Launch the ChatGPT desktop app while signed in to a Business workspace account.
  2. The spinner shows indefinitely.

None of these fixed the hang:

  • Stopped all app processes and CodexSandboxService, then ran Windows App Repair.
  • Cleared the renderer caches (Cache, Code Cache, GPUCache, shader caches, Session Storage).
  • Reset .codex-global-state.json.
  • Removed the entire web profile folder (LocalCache\Roaming\Codex\web).
  • Uninstalled and reinstalled from the Microsoft Store.
  • Launched with an empty CODEX_HOME.
  • Removed ~/.cache/codex-runtimes so it re-downloaded.
  • Removed auth.json and signed in again. The sign-in screen rendered, then it hung right after sign-in.

Network check: chatgpt.com, ab.chatgpt.com, statsigcdn.openai.com, persistent.oaistatic.com, and api.openai.com all resolve and respond. No proxy is set.

What is the expected behavior?

After sign-in, the app loads the main UI as it did earlier the same day on the same version.

Additional information

The hang survives a full reinstall and a clean local state, and it happens only once signed in. That points to something server-side for this account or workspace, such as a feature gate or workspace policy, that stops the renderer from mounting routes. This may be related to #48701 and #49070.

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    on Sep 29, 2026
  2. delamis commented on Sep 29, 2026

    @delamis

    Additional report of similar Windows desktop startup symptoms, observed on 2026-09-29. The exact installed app version and Windows build have not yet been collected, so I cannot confirm that this is the same regression or root cause.

    The app frequently remains on a dark, otherwise empty window with a centered loading spinner and no visible error message. It occasionally reaches the main interface, but the approximate experience is one successful launch for ten failed attempts; this is an estimate, not a measured failure rate. The behavior makes closing or updating the app disruptive because reopening it is unreliable.

    While attempting to troubleshoot the recurring problem, conversation history was accidentally lost. The precise action that caused the loss is not established; I am not claiming that the startup hang itself deleted the history.

    Please investigate this additional intermittent-startup case and provide a recovery/workaround path that preserves remaining local conversations and settings. Please specify which Windows desktop logs are useful to collect while the main UI cannot load, and where they are located. A solution should not depend on deleting the .codex directory or resetting app data without a verified backup.

    A screenshot of the blank startup window and spinner is available. No raw logs or conversation contents are included in this public report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions