›_ Codex Issues
Codex Issues / #40746

Finish Windows setup

Open 💬 2 comments Opened Aug 26, 2026 by Mike-Feng
💡 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)?

latest

What subscription do you have?

Pro max

What platform is your computer?

x64

What issue are you seeing?

I cannot launch this application.
It stucks here:

<img width="1090" height="760" alt="Image" src="https://github.com/user-attachments/assets/5e3785f0-56f5-46e7-b0e4-c55b7e9a90ce" />

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a03b72-666e-7ba3-bf95-47e99721ac32

What is the expected behavior?

normally start chatgpt

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #40550
  • #40346
  • #40102

Powered by Codex Action

cpl366 · 1 day ago

If you're still stuck on Finish Windows setup, I would avoid repeatedly clicking setup / reinstalling until you separate the setup helper from the CLI/config layers. We recovered a similar Windows machine where the UI stayed on the setup screen but the actual blockers were elsewhere.

A safe first pass is:

where.exe codex
[Environment]::GetEnvironmentVariable("CODEX_CLI_PATH","User")
powershell.exe -NoLogo -NoProfile -NonInteractive -Command "Write-Output NO_PROFILE_OK"
powershell.exe -NoLogo -NonInteractive -Command "Write-Output PROFILE_OK"

If where codex finds an npm install, locate the native codex.exe (not codex.cmd) and verify it with --version. Current Windows npm installs typically have it under a path ending in:

@openai\codex\node_modules\@openai\codex-win32-x64\vendor\x86_64-pc-windows-msvc\bin\codex.exe

Then, if that native CLI runs, try:

& <native-codex.exe> mcp list

If that command fails with a config parse error, fix/back up the active config first; if it succeeds, the remaining failure is more likely in the Desktop/setup helper path.

Also compare normal PowerShell vs -NoProfile: a broken Conda/Python profile can independently break Desktop initialization while making the UI look like a generic setup failure.

Please don't delete .codex / session data while diagnosing this. If you post the four command outputs above (redacting tokens), it should narrow the failure considerably.