›_ Codex Issues
Codex Issues / #6479

Codex process errored: Codex process is not available

Resolved 💬 7 comments Opened Nov 10, 2025 by ofirgaash1 Closed Nov 11, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the VS Code extension are you using?

0.4.38
Last Updated 1 day ago

What subscription do you have?

standard

Which IDE are you using?

VS code

What platform is your computer?

Microsoft Windows NT 10.0.27982.0 x64

What issue are you seeing?

An error has occurred
Codex crashed with the following error:

Codex process errored: Codex process is not available
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.

Open Config.toml
Reload

<img width="774" height="1498" alt="Image" src="https://github.com/user-attachments/assets/568f68a2-1cf7-41e8-9c28-5ad0c2cbca1e" />

What steps can reproduce the bug?

I clicked "run in WSL", then this happened, and that's the situation for the last couple of days.

The config file is empty.

What is the expected behavior?

_No response_

Additional information

Reloading doesn't solve it.

Re-installing the extension doesn't solve it.

Reboot doesnt help either.

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 8 months ago

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

  • #6435
  • #6304
  • #6192
  • #6062

Powered by Codex Action

etraut-openai contributor · 8 months ago

Thanks for the bug report. It looks like this is already being tracked in #6435. Closing to reduce duplication.

guarasoft · 8 months ago

Same issue here on Windows 11 Pro.
Clean install, no extensions, no WSL, fully updated VSCode.

Codex fails to start its local binary and instantly returns:
“Codex process errored: Codex process is not available”.

Worked fine until last update.

<img width="468" height="923" alt="Image" src="https://github.com/user-attachments/assets/1011847c-8f5f-48b7-8f4c-3efa82f3f1c8" />

OakerO · 8 months ago

It works for me when I enable WSL option but I get this error if I DISABLE wsl.

Okay, found the issue. This stuff seems really poorly tested. I tried to execute the codex.exe manually and got DLL error. I installed the runtimes and it works now. See here https://learn.microsoft.com/en-us/answers/questions/4269238/vcruntime140-dll-and-msvcp140-dll-missing-in-windo

armilancode · 7 months ago

Try this:
Open an old ( or a fresh/new ) conversation.
Does that work?
If yes: Your previous conversation crashed ( happend with me, it even crashed my windows 11 trying to run some powershell scripts ).
This conversation can't be opened anymore for some reason and you have to start a new one.
I hope they fix these untested situations in the future. I've just lost so much progress in that conversation.

Cr4nkSt4r · 7 months ago
Your previous conversation crashed ( happend with me, it even crashed my windows 11 trying to run some powershell scripts ). This conversation can't be opened anymore for some reason and you have to start a new one. I hope they fix these untested situations in the future. I've just lost so much progress in that conversation.

1) Go into your .codex folder
2) Go into the sessions folder
3) Look for that chats rollout .jsonl file (rollout-<year>-<month>-<day>T<hour>-<minute>-<second>-<codex_session_hash>.jsonl)
4) Remove some lines at the end of the file but it should still be valid json.

  • like delete such a whole block or some more blocks (depending on if it's working after only one block delete or not):
{"timestamp":"<redacted>","type":"turn_context","payload":{"cwd":"<redacted>","approval_policy":"on-request","sandbox_policy":{"type":"workspace-write","writable_roots":"<redacted>"},"model":"gpt-5.1","effort":"high","summary":"auto"}}

5) Restart your codex instance if still one open (restart VS Code for example)
6) Continue with your conversation, just a few messages back in.

Nguyenhieploi · 29 days ago

I was able to fix this issue by downgrading the Codex VS Code extension to version 26.609.30741.

After installing that version and restarting VS Code, Codex worked again without the Codex process is not available / state db discrepancy error.