Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Windows app (Microsoft Store) crashes on first screen with: code=3221225477, signal=null [1 comments, 2 participants]

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…
GitHub stats
openai/codex#17485•Fetched 2026-04-12 13:27:51
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
enjoycod1ngenjoycod1ng
Participants
enjoycod1ngenjoycod1nggithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1

Error Message

Full error shown by the app: An error has occurred Codex crashed with the following error: Most recent error: None

Root Cause

No session ID is available because the app crashes before a usable session starts.

RAW_BUFFERClick to expand / collapse

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

Latest from Microsoft Store

What subscription do you have?

Pro

What platform is your computer?

Windows 10 Pro, x64 Version 2009 OS Build 26200

What issue are you seeing?

The Codex Windows app from the Microsoft Store crashes immediately on the first screen before the UI becomes usable.

Full error shown by the app:

An error has occurred Codex crashed with the following error:

(code=3221225477, signal=null). Most recent error: None

Some things to try:

Check your config.toml for invalid settings Check your settings to disable running in WSL if you are seeing compatibility issues Try downloading a different version of the extension Click reload to restart the Codex extension, or visit our documentation for additional help.

This happens before I can use the app normally, so there is no session ID, token usage, or context window info available.

What steps can reproduce the bug?

  1. Install Codex from the Microsoft Store on Windows 10 Pro.
  2. Launch the Codex desktop app.
  3. The app crashes on the first screen before the main UI becomes usable.
  4. The same crash happens every time.

Things I already tried:

  • Used config.toml with: [windows] sandbox = "elevated"

  • Changed it to: [windows] sandbox = "unelevated"

  • Renamed config.toml to config.toml.bak so the app starts with no config file.

  • Confirmed CODEX_HOME is not set.

  • Checked Microsoft Store / winget and there is no newer version available.

Result: The crash is the same in all cases: (code=3221225477, signal=null)

No session ID is available because the app crashes before a usable session starts.

What is the expected behavior?

The Codex Windows desktop app should launch normally and open to the main UI instead of crashing on the first screen.

Additional information

No response

extent analysis

TL;DR

The Codex Windows app crash may be related to compatibility issues, and trying a different configuration or disabling WSL might resolve the issue.

Guidance

  • Check the system's configuration and settings to ensure compatibility with the Codex app, as suggested in the error message.
  • Try disabling WSL (Windows Subsystem for Linux) to see if it resolves the compatibility issues, as the error message hints at potential WSL-related problems.
  • Consider resetting the app's settings to their default values or reinstalling the app from the Microsoft Store to start with a clean configuration.
  • If the issue persists, try searching for similar issues or reaching out to the Codex support team for further assistance, as the provided troubleshooting steps have already been attempted.

Notes

The error code (3221225477) is a generic Windows error code that doesn't provide specific information about the cause of the crash. The lack of a session ID or more detailed error information limits the ability to provide a more targeted solution.

Recommendation

Apply workaround: Try disabling WSL or changing the app's configuration to see if it resolves the issue, as these are the most direct suggestions provided in the error message and have not been explicitly tried in combination.

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…
#training loop#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

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

Back to top recommendations

TRENDING