codex - 💡(How to fix) Fix Windows Desktop update relaunch does not restore maximized window state

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

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

Codex Desktop on Windows, current package observed after the update/relaunch:

  • OpenAI.Codex_26.602.3474.0_x64__2p2nqsd0c76g0

The exact version before the update was not captured.

What subscription do you have?

Unknown / not relevant to the window-state restore behavior.

What platform is your computer?

Windows desktop app.

Environment observed on this machine:

  • Windows Education, display version 25H2
  • OS build 26200.8457, 64-bit

What issue are you seeing?

When Codex Desktop is maximized and I start an update from inside the application, Codex installs the update and restarts/relaunches, but the window state is not restored correctly.

Before starting the update, the Codex window is maximized. After the update flow restarts the app, Codex opens in a smaller restored window instead of returning to the maximized state it had before the update.

This appears to be specifically tied to the in-app update/restart path. The app does come back after the update, but the persisted window placement/state is incomplete: the normal window size is restored, while the maximized state is lost.

What steps can reproduce the bug?

  1. Run Codex Desktop on Windows.
  2. Maximize the Codex window.
  3. Start an available update from inside Codex.
  4. Wait for the update to install and for Codex to restart/relaunch.
  5. Observe the window state after Codex comes back.

Observed result:

  • Codex relaunches after the update.
  • The window opens at a smaller restored size.
  • The pre-update maximized state is not remembered.

Expected result:

  • If Codex was maximized before starting the in-app update, it should reopen maximized after the update relaunch.

What is the expected behavior?

The in-app update/relaunch flow should preserve the same window state that normal app restarts preserve.

If the window was maximized before the update, the post-update instance should restore as maximized rather than falling back to the last non-maximized bounds.

Additional information

I searched existing openai/codex issues before filing. I did not find an exact duplicate for losing the maximized state after an update relaunch.

Closest related issues found:

  • #24047: Windows Desktop update installs but Codex does not relaunch afterward. That issue is about a failed relaunch; in this case Codex relaunches, but loses the maximized window state.
  • #25513, #25217, #25754, #25806, #25249, #25998: Windows maximized rendering/transparency/visual-corruption issues. Those are about rendering while maximized, not the post-update window state being restored as non-maximized.
  • #23947: Windows light theme becomes mixed dark/light after resizing or reopening a smaller window. That includes reopening/resizing symptoms, but not the update relaunch path losing a maximized state.

This report is scoped to the updater restart path preserving the maximized/restored window-state flag.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING