Windows setup cannot complete (UAC never appears)
Resolved 💬 6 comments Opened Jul 14, 2026 by aimayu Closed Jul 17, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
ChatGPT Desktop 26.707.9564.0
What subscription do you have?
Plus
What platform is your computer?
Windows 11 Pro
What issue are you seeing?
ChatGPT Desktop 26.707.9564.0
After installing ChatGPT Desktop, the application always shows:
"Complete Windows setup"
Clicking "Retry Windows Setup" does nothing.
No UAC prompt is ever displayed.
<img width="1112" height="822" alt="Image" src="https://github.com/user-attachments/assets/1d12df4a-a9fd-42a6-8998-64b4bd2312c0" />
Things already tested:
reinstall from OpenAI website
reinstall from Microsoft Store
reboot
UAC set to maximum
Kaspersky completely removed
running as Administrator
helper executable exists
codex-windows-sandbox-setup.exe cannot be run manually because it expects a payload
log.txt
What steps can reproduce the bug?
- Install the latest ChatGPT Desktop app on Windows 11 Pro (also reproduced with both Microsoft Store and the installer from openai.com).
- Launch ChatGPT.
- The app displays "Complete Windows setup".
- Click "Retry Windows Setup".
- Nothing happens. No UAC prompt is displayed, and the app remains on the same screen.
What is the expected behavior?
_No response_
Additional information
_No response_
6 Comments
Additional investigation:
I collected some diagnostics while troubleshooting.
Environment:
Already tested:
Results:
I also found that the application installs:
%LOCALAPPDATA%\OpenAI\Codex\bin\<version>\codex-windows-sandbox-setup.exe
Running it manually returns:
Error: helper_request_args_failed: expected payload argument
which suggests the helper itself exists and expects to be launched by ChatGPT with an internal payload.
Desktop logs are attached.
The logs also consistently contain:
Failed to load desktop settings from config.toml
Invalid TOML document
The config.toml appears to contain only null bytes.
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
thks
I've discovered another critical root cause for the "Finish Windows setup" hang (where the UAC prompt never triggers) that is related to authentication rather than Windows privileges or system features.
The Underlying Issue
If your user session has expired or the OAuth refresh token has been revoked, the desktop app fails to fetch the cloud configuration bundle (
cloudConfigBundle) during startup:This causes the backend
windowsSandbox/setupStartcall to fail with a401 Unauthorized/Autherror. Instead of displaying a prompt to log out and log in again, the Desktop UI incorrectly routes this error to the "Finish Windows setup" gate, making it appear as a permissions/sandbox setup failure.The Fix / Workaround
To break the loop and force the app to show the login screen:
%USERPROFILE%\.codex(usuallyC:\Users\<username>\.codex).auth.json.auth.jsontoauth.json.bak(or delete it).The app will now detect that no login session exists, skip the sandboxing gate, and successfully route you to the Sign In screen. Once you log back in, a fresh OAuth session will be established, and the app will open normally.
Tried it, I het a new auth session, and after the config it ;amds on teh last step UAC and fails the same way.
<img width="1152" height="1044" alt="Image" src="https://github.com/user-attachments/assets/8f153458-3d09-4a4a-aeff-6d28a3904d15" />
THe solution to delete config.toml worke for me (https://github.com/openai/codex/issues/32492) - the file was corrupted.
How do I recover my previous sessions now? My new ChatGPT desktop app is empty. Did I lost all my work in progress?
Confirmed, this resolved the issue for me.
The root cause was a corrupted config.toml.
Renaming:
config.toml
→
config.toml.bak
forced the app to recreate the configuration on startup. After that, the "Finish Windows setup" screen disappeared and the application started normally.
In my logs, every launch contained:
Failed to load desktop settings from config.toml
Invalid TOML document
The file appears to have become corrupted (filled with null bytes), so the desktop app was unable to parse it and incorrectly ended up on the "Finish Windows setup" flow.
Thanks for pointing me to issue #32492.