Windows: internal PowerShell tool fails with 8009001d while user PowerShell works

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

<Fill from About Codex dialog>

What subscription do you have?

ChatGPT Pro

What platform is your computer?

"$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })"

What issue are you seeing?

Codex App on Windows cannot execute internal PowerShell commands via the Codex tool layer.

User PowerShell works normally in the same workspace, but Codex internal tool execution fails before even simple commands run.

Codex environment_context:

• cwd: D:\codex
• shell: powershell
• timezone: Asia/Seoul

User PowerShell works:

• Get-Date works
• Get-Location shows D:\codex\.codex-tasks\design-md-analysis\packages\cli
• Test-Path D:\codex returns True

Codex internal tool fails:

• Get-Date
• Get-Location
• Test-Path D:\codex
• Test-Path D:\codex\.codex-tasks\design-md-analysis
• bun --version
• node --version
• npm --version

All commands fail with:

• Exit code: -65536
• Output includes: 8009001d
• The output appears garbled/mojibake, but consistently contains Windows PowerShell and 8009001d.

This still happens after:

• restarting the Codex app
• running Codex as administrator
• updating/reinstalling the Codex app

Earlier there was also suspicion of a bad cwd mapping such as C:\mnt\d\codex, but in the current session environment_context reports D:\codex. However, Codex cannot confirm Get-Location because internal PowerShell execution fails first.

What steps can reproduce the bug?

Uploaded thread: 181a4917-b0ac-4581-8c77-5c51c136d27e

1. Open Codex App on Windows.
2. Open workspace D:\codex.
3. Confirm environment_context shows:

• cwd: D:\codex
• shell: powershell

1. Ask Codex to run any internal PowerShell command, for example:

```powershell
Get-Date

1. Observe that the command fails before execution with 8009001d.

Get-Location
Test-Path D:\codex
bun --version
node --version
npm --version

What is the expected behavior?

_No response_

Additional information

This does not appear to be a project/repository issue.

No package files were modified.
No install/build/test command was intentionally run.
The failure happens even with Get-Date, so it occurs before runtime PATH or project tooling becomes relevant.