codex - 💡(How to fix) Fix Codex App disables WSL/Windows interop globally [1 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#19796Fetched 2026-04-28 06:37:01
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

Error Message

-bash: /mnt/c/WINDOWS/explorer.exe: cannot execute binary file: Exec format error

Code Example

$ explorer.exe

---

$ explorer.exe
-bash: /mnt/c/WINDOWS/explorer.exe: cannot execute binary file: Exec format error

---

$ explorer.exe
RAW_BUFFERClick to expand / collapse

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

26.422.30944

What subscription do you have?

Business

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex App disables WSL/Windows interop in all WSL terminals on startup.

What steps can reproduce the bug?

In WSL before starting Codex App:

$ explorer.exe

Result: Explorer launched.

In WSL after starting Codex App:

$ explorer.exe
-bash: /mnt/c/WINDOWS/explorer.exe: cannot execute binary file: Exec format error

Result: No Explorer started.

Uploaded thread: 39a1a0d1-159f-44bd-ad3d-ca3240eeb6ba

What is the expected behavior?

In WSL at any time:

$ explorer.exe

Result: Explorer launched.

Additional information

WSL is running Ubuntu 24.04.4 LTS.

extent analysis

TL;DR

The Codex App may be interfering with WSL/Windows interop, causing the "cannot execute binary file: Exec format error" when trying to launch Explorer from WSL.

Guidance

  • The issue seems to be related to the Codex App disabling WSL/Windows interop on startup, which prevents Explorer from launching.
  • To verify, try closing the Codex App and then launching Explorer from WSL using explorer.exe to see if it works as expected.
  • As a potential workaround, consider launching the Codex App after starting the WSL terminal or finding an alternative method to launch Explorer that doesn't rely on WSL/Windows interop.
  • Check the Codex App settings or documentation to see if there's an option to disable or configure the WSL/Windows interop disabling behavior.

Notes

The exact cause of the issue is unclear, and more information about the Codex App's configuration and settings may be needed to provide a definitive solution.

Recommendation

Apply workaround: Try launching the Codex App after starting the WSL terminal or finding an alternative method to launch Explorer, as this may help mitigate the issue until a more permanent solution is found.

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

codex - 💡(How to fix) Fix Codex App disables WSL/Windows interop globally [1 participants]