codex - 💡(How to fix) Fix Windows: `shell_command` fails during PowerShell initialization with `InitialSessionState` / `GetSaferPolicy` / `Win32Exception (126)`, while manual PowerShell works [9 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#20152Fetched 2026-04-30 06:33:06
View on GitHub
Comments
9
Participants
2
Timeline
14
Reactions
0
Timeline (top)
commented ×9labeled ×4renamed ×1
RAW_BUFFERClick to expand / collapse

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

codex app 26.426.12240

What subscription do you have?

plus

What platform is your computer?

x64

What issue are you seeing?

codex-shell-command-windows-bug-report.md

What steps can reproduce the bug?

codex-shell-command-windows-bug-report.md

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

Review the provided bug reports to identify and potentially fix the issue with the Codex App's shell command on Windows.

Guidance

  • Examine the contents of the codex-shell-command-windows-bug-report.md files to understand the nature of the bug and its reproduction steps.
  • Check if there are any known issues or fixes related to the Codex App version 26.426.12240 that might address the problem.
  • Consider reaching out to the Codex App support or community for further assistance, given the lack of detailed information about the expected behavior and additional context.
  • Look for any platform-specific (x64 Windows) considerations that might be contributing to the issue.

Notes

The provided information lacks specific details about the expected behavior and additional context, making it challenging to offer a precise fix. The guidance provided is based on the assumption that the bug reports contain crucial information about the issue.

Recommendation

Apply workaround: Given the lack of information about a fixed version or a direct solution, applying a workaround based on the insights gained from the bug reports and potential community or support feedback seems to be the most viable approach.

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 Windows: `shell_command` fails during PowerShell initialization with `InitialSessionState` / `GetSaferPolicy` / `Win32Exception (126)`, while manual PowerShell works [9 comments, 2 participants]