Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex VS Code extension cannot execute any local shell command on Windows (PowerShell 8009001d / CreateProcessWithLogonW 1056) [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#17094•Fetched 2026-04-09 08:02:32
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
fengxiaozi-liufengxiaozi-liu
Participants
fengxiaozi-liufengxiaozi-liugithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×1

Error Message

  • Internal Windows PowerShell error with code 8009001d
RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

openai.chatgpt-26.325.31654-win32-x64

What subscription do you have?

plus

Which IDE are you using?

vscode

What platform is your computer?

Windows_NT x64 10.0.26200

What issue are you seeing?

The Codex VS Code extension cannot execute any local shell command in my environment.

Symptoms:

  • Any command executed by Codex fails before the command actually runs
  • Even minimal commands such as Get-Location fail
  • Codex cannot read local files such as feature.md
  • Manual PowerShell works normally
  • VS Code integrated terminal works normally

Observed errors:

  • Internal Windows PowerShell error with code 8009001d
  • Sometimes CreateProcessWithLogonW failed: 1056

What I verified:

  • powershell -NoProfile works correctly when run manually
  • SystemRoot, WINDIR, and ComSpec are present in my PowerShell environment
  • VS Code terminal works
  • code --status shows pty-host, OpenConsole.exe, powershell.exe, and codex.exe app-server are running
  • Reinstalling VS Code did not fix it
  • Reinstalling the extension and deleting the extension directory did not fix it
  • The same problem happens in a new Codex conversation

Environment:

  • VS Code 1.114.0
  • Windows 10.0.26200 x64
  • Extension version: openai.chatgpt-26.325.31654-win32-x64

Minimal reproduction:

  1. Open VS Code
  2. Open a workspace
  3. Start a Codex chat
  4. Ask Codex to run a minimal local command such as Get-Location
  5. The command fails with the errors above
<img width="859" height="207" alt="Image" src="https://github.com/user-attachments/assets/8f2b82bc-b5de-4c59-ae35-dcab7b7664bf" />

What steps can reproduce the bug?

I can provide code --status output and extension logs if needed.

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue may be resolved by configuring the Codex VS Code extension to properly interact with the local PowerShell environment, potentially by adjusting settings related to process creation or authentication.

Guidance

  • Verify that the powershell.exe path is correctly configured in the VS Code settings, ensuring it matches the system's ComSpec environment variable.
  • Check the extension's configuration for any options related to process creation, such as CreateProcessWithLogonW, and adjust them according to the system's security policies.
  • Investigate the Internal Windows PowerShell error with code 8009001d and CreateProcessWithLogonW failed: 1056 errors to determine if they are related to a specific system configuration or security setting.
  • Consider providing the code --status output and extension logs to further diagnose the issue.

Example

No specific code snippet is available, as the issue is related to the interaction between the Codex extension and the local PowerShell environment.

Notes

The issue may be specific to the Windows 10 environment or the openai.chatgpt-26.325.31654-win32-x64 extension version. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Adjust the extension's configuration and system settings to properly interact with the local PowerShell environment, as the issue may be related to a specific system configuration or security setting.

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…
#GPU setup#container setup#orchestration issue#cache issue#memory leak

Still need to ship something?

×6

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

Back to top recommendations

TRENDING