[Windows Desktop 26.810.7004.0] Codex Immediately Crashes with error code 1 unless you delete your existing .codex folder
Resolved 💬 2 comments Opened Aug 18, 2026 by Jediweirdo Closed Aug 19, 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)?
26.810.7004.0
What subscription do you have?
Plus/Education
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
(code=1, signal=null).
Most recent error: Stack backtrace:
0: <unknown>
1: <unknown>
2: aws_lc_0_39_0_jent_entropy_switch_notime_impl
3: <unknown>
4: <unknown>
5: <unknown>
6: <unknown>
7: <unknown>
8: <unknown>
9: <unknown>
10: BaseThreadlnitThunk
11: RtlUserThreadStart
What steps can reproduce the bug?
- Replace your .codex folder with the one in this bug report
- Download ChatGPT from the Microsoft Store or use the installer available at https://chatgpt.com/codex
- Attempt to open the app
- Wait for a second for the error to pop up
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Saw
aws_lc_0_39_0_jent_entropy_switch_notime_implin your crash frame. That's the known aws-lc-rs jitter-entropy panic, #38230 has the full root cause, it's a Windows build gap, they only disable that path for musl builds. Before deleting the whole folder, try renaming%USERPROFILE%\.codexto.codex.bakand launching, then move auth.json back first so you keep your login, then config.toml, then sessions/ one at a time to isolate the trigger, themcp_serversblock in config.toml is the likely culprit since the panic fires through the TLS/MCP path. Oh btw, I built a portable Hermes OTG and run it from a USB stick as my rescue agent for exactly these broken-after-update Windows installs, https://github.com/MilkyWay008/Hermes-OTG, handy when you need a working agent to diagnose from. Rolling back to the previous MSIX works too while they fix the build flag.