Repository navigation
[Windows] ChatGPT Desktop stuck on “Unable to load sign-in requirements” after reset/reinstall #46613
Description
Activity
Hey ! Same issue here.
Same issue here. In my case was missconfiguration in config.toml due to third party stuff I installed. Try starting codex in terminal, if something is wrong with your config it will tell you.
Reacted by Alek’Saï, bastionlin, Andre Kampmann, Dan Frenette, Xavier Mañana, Archer, Zane Perry and DipankarSame issue here. In my case was missconfiguration in config.toml due to third party stuff I installed. Try starting codex in terminal, if something is wrong with your config it will tell you.
Yep it's works thanks dude ;)
Additional diagnostics from the affected machine:
- Windows 11 x64
- Codex Desktop package:
26.915.4065.0 - Codex CLI/runtime:
0.155.1 codex login statusreturns:Logged in using ChatGPTcodex doctorreports:- config loaded successfully
config.toml parse: ok- auth configured with stored ChatGPT tokens
- install consistent
- active OpenAI provider endpoints reachable over HTTP
- 0 fail / degraded overall
Desktop logs repeatedly show:
[electron-message-handler] sa_server_request_failed attachAuth=true attachIntegrityState=true errorMessage="Workspace routing is unavailable" routePattern=/wham/tasks/list status=432The same startup session also shows
/wham/usagefailing with the sameWorkspace routing is unavailable/ status 432 error.This appears closely related to #46382, where multiple Windows users report the same workspace-routing failure while the CLI and web app continue to work. One commenter there reports a controlled rollback from runtime/app-server
0.155.0to0.154.0restoring Desktop functionality on the same Desktop build. I have NOT attempted a rollback on this machine, so I cannot confirm the same workaround here.There are also separate WSL/plugin-marketplace warnings in the logs:
failed to reload config: No such file or directory (os error 2) primary_runtime_restore_failed Failed to sync primary runtime bundled plugin marketplaceand the Desktop is configured to spawn some processes inside WSL. These may be secondary, because the CLI configuration itself parses correctly and authentication is healthy.
Current observed state:
ChatGPT web OK Codex CLI OK Codex login OK config.toml OK Codex Desktop FAIL Workspace routing FAIL (status 432)This narrows the issue from a generic sign-in failure to a Desktop workspace/account routing problem.
I also have this problem. I just got it fixed, but its annoying that i get the pro plan and i cant even use it in the way i was intended, because the app wasn't opening.
Same Issue here!
[features.context_management] experimental_mode = trueI think it's this config that went viral last week on socials after astra release, I also add it, it work fine for a few days until I encounter this issue this morning, remove it from my config.toml and everything work like normal again.
This happened to me after he told to add something to the bottom of the Codex config.toml, in order to get permission to edit some files I had gave him to work on
worked again after i went into config.toml and removed the added block
Error loading configuration: 系统找不到指定的文件。 (os error 2) 显示 这个
I can reproduce this issue on a newer Windows desktop build, and I was able to capture the underlying failure in the desktop logs.
Environment
Windows: 10.0.26200 x64 OpenAI.Codex package: 26.917.9434.0 Reported app-server: 0.155.0-alpha.16.4 CODEX_CLI_PATH: not setSymptoms
The ChatGPT desktop app was working normally previously. After a later Windows restart, the app became stuck at:
Loading sign-in requirements...and eventually reports:
Unable to load sign-in requirements.Retrying does not resolve it.
The same ChatGPT account continues to work normally in the web browser.
Troubleshooting performed
The problem persists after all of the following:
- Completely exiting and restarting the desktop app
- Windows Repair
- Windows Reset
- Completely uninstalling and reinstalling the current Microsoft Store version
- Disabling Tailscale
- Testing on the normal network
- Moving the computer to a cellular phone hotspot
- Confirming ChatGPT web works normally with the same account
Changing networks made no difference.
CODEX_CLI_PATH is not involved
Because
CODEX_CLI_PATHwas identified as the cause for the original reporter in #46382, I specifically checked it:Get-ChildItem Env:CODEX_CLI_PATHResult:
Cannot find path 'CODEX_CLI_PATH' because it does not exist.So this reproduction does not involve a user-configured
CODEX_CLI_PATHoverride.App-server version
The desktop log reports:
Current reported app-server version: currentVersion=0.155.0-alpha.16.4 hostId=localThe runtime selection also shows:
architecture=x64 buildFlavor=prod frameworkEnabled=false osRelease=10.0.26200 runtimeRoot=...\codex-primary-runtime runtimeSource=archiveWorkspace-routing failure
The same desktop log repeatedly records:
errorMessage="Workspace routing is unavailable" status=432 attachAuth=true attachIntegrityState=trueConfirmed affected requests include:
/wham/tasks/list /wham/usageFor example:
sa_server_request_failed attachAuth=true attachIntegrityState=true errorMessage="Workspace routing is unavailable" method=get routePattern=/wham/tasks/list status=432and:
sa_server_request_failed attachAuth=true attachIntegrityState=true errorMessage="Workspace routing is unavailable" method=get routePattern=/wham/usage status=432This appears consistent with the workspace-routing failures being tracked in #46812.
Other startup errors
The same startup sequence also contains repeated configuration errors:
failed to resolve feature override precedence: No such file or directory (os error 2)and:
failed to reload config: No such file or directory (os error 2)as well as:
Failed to refresh ambient suggestions errorMessage="failed to load workspace requirements"Package history
Windows AppX deployment logs show the machine transitioned from:
OpenAI.Codex_26.915.4065.0to:
OpenAI.Codex_26.917.9434.0on September 24.
The app was reported to have worked previously and the failure was first noticed after a subsequent Windows restart, so I cannot conclusively say the package update itself caused the failure.
Current state
ChatGPT web PASS Normal network FAIL Cellular hotspot FAIL Tailscale disabled FAIL Windows Repair/Reset FAIL Complete reinstall FAIL CODEX_CLI_PATH NOT SET Desktop workspace routing FAIL Desktop sign-in requirements FAILThis appears to be a desktop workspace-routing/account-bootstrap problem rather than a general account, browser, VPN, DNS, or local-network connectivity issue.
It also reproduces on
26.917.9434.0with app-server0.155.0-alpha.16.4, which is newer than several of the versions discussed in #46382 and #46812.I can provide additional sanitized desktop logs if useful.
No account identifiers, authentication tokens, cookies, credentials, passcodes, or private conversation data are included here.
Update — 2026-09-26
The issue is still reproducible on my Windows machine and has now progressed to a more explicit blocking dialog in Codex Desktop:
Impossible de charger les paramètres de l’organisation
(“Unable to load organization settings”)The dialog says the application is paused until the organization settings can be loaded safely. It offers Retry, Sign out, and Quit.
Current behavior:
- Retry does not resolve the error.
- The Desktop app remains blocked/unusable, so I cannot use Codex Desktop for coding.
- ChatGPT in the browser still works.
- This happened again after restarting/retesting the app.
- I also updated WSL to 2.7.14.0, but this did not resolve this Desktop account/workspace-loading failure.
- A screenshot of the new dialog is available.
This looks related to the workspace/account routing failures reported by other Windows users, especially #46812, where requests fail with
Workspace routing is unavailable/ status432. Another reproduction already posted in this issue also reported the same routing failure on a newer Desktop build.So the user-visible symptom has changed from “Unable to load sign-in requirements” to “Unable to load organization settings”, but the result is still the same: Codex Desktop cannot complete account/workspace initialization and is completely blocked.
Please let me know if fresh sanitized logs from this occurrence would help narrow down the regression.
What version of the Codex / ChatGPT Desktop app are you using?
Exact version unavailable because the app cannot get past the sign-in requirements screen. It was freshly reinstalled from the Microsoft Store on 2026-09-19.
What subscription do you have?
Paid ChatGPT plan.
What platform is your computer?
Windows 11 x64.
What issue are you seeing?
The ChatGPT Desktop app opens, but it is unusable because the window remains stuck on:
with only a Retry button.
Retry does not resolve the problem.
ChatGPT works normally in the web browser with the same account, so the account itself is accessible. The failure appears specific to the Windows desktop app / desktop sign-in flow.
The issue began before the SSO incident shown on the OpenAI status page on 2026-09-18 and is still present after that incident was marked resolved.
What steps can reproduce the bug?
Troubleshooting already attempted
None of these steps changed the behavior.
What is the expected behavior?
The desktop app should load the ChatGPT sign-in requirements/authentication flow and allow the user to sign in normally.
Additional information
A screenshot of the error is available and can be added if needed.
Because the app never reaches the main UI, the exact app version cannot currently be read from the About dialog.