`elevated_windows_sandbox` causing all agent commands to fail with `(no output)` (logs show `CreateProcessAsUserW failed: 5`)

[i4TsU]

What version of Codex is running?

codex-cli 0.92.0

What subscription do you have?

Business

Which model were you using?

gpt-5.2-codex

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What terminal emulator and version are you using (if applicable)?

WezTerm (version 20240203-110809-5046fc22) running PowerShell-7.5.4

What issue are you seeing?

Here is an example from ~\.codex\.sandbox\sandbox.log - it seems like every occurrence follows this same pattern, terminating with CreateProcessAsUserW failed: 5 (even including some extremely similar errors from 1-2 weeks ago)

[2026-01-28 23:52:44.536 codex.exe] START: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command [Console]::OutputEncoding=[System.Text.Encoding]::UTF8;
Get-ChildItem -Force
[2026-01-28 23:52:44.542 codex.exe] sandbox setup required: sandbox setup marker missing or incompatible
[2026-01-28T13:52:50.266862700+00:00] ensuring sandbox users offline=CodexSandboxOffline online=CodexSandboxOnline
[2026-01-28T13:52:50.679248100+00:00] firewall rule configured name=codex_sandbox_offline_block_outbound protocol=256 LocalUserAuthorizedList=O:LSD:(A;;CC;;;S-1-5-21-xxxxx)
[2026-01-28T13:52:50.690563400+00:00] granting write ACE to D:\repo\subdir for sandbox group and capability SID
[2026-01-28T13:52:50.719824400+00:00] read-acl-only mode: applying read ACLs
[2026-01-28T13:52:50.721659100+00:00] read ACL run completed
[2026-01-28 23:52:50.962 codex-windows-sandbox-setup.exe] setup binary completed
[2026-01-28 23:52:50.975 codex.exe] setup refresh: spawning X:\scoop\persist\nodejs\bin\node_modules\@openai\codex\vendor\x86_64-pc-windows-msvc\codex\codex-windows-sandbox-setup.exe (cwd=D:\repo\subdir, payload_len=668)
[2026-01-28T13:52:51.005385400+00:00] setup refresh: processed 3 write roots (read roots delegated); errors=[]
[2026-01-28 23:52:51.005 codex-windows-sandbox-setup.exe] setup binary completed
[2026-01-28T13:52:51.029863800+00:00] read-acl-only mode: applying read ACLs
[2026-01-28T13:52:51.032045+00:00] read ACL run completed
[2026-01-28 23:52:51.615 codex-command-runner.exe] runner start cwd=D:\repo\subdir cmd=["C:\\Program Files\\WindowsApps\\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\\pwsh.exe", "-Command", "[Console]::OutputEncoding=[System.Text.Encoding]::UTF8;\nGet-ChildItem -Force"] real_codex_home=C:\Users\username\.codex
[2026-01-28 23:52:51.618 codex-command-runner.exe] runner: effective cwd=D:\repo\subdir (requested D:\repo\subdir)
[2026-01-28 23:52:51.628 codex-command-runner.exe] runner: spawn failed: CreateProcessAsUserW failed: 5
[2026-01-28 23:52:51.633 codex.exe] FAILURE: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command [Console]::OutputEncoding=[System.Text.Encoding]::UTF8;
Get-ChildItem -Force (exit code 1)
[2026-01-28 23:52:55.612 codex.exe] START: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command [Console]::OutputEncoding=[System.Text.Encoding]::UTF8;
Get-Location
[2026-01-28 23:52:55.623 codex.exe] setup refresh: spawning X:\scoop\persist\nodejs\bin\node_modules\@openai\codex\vendor\x86_64-pc-windows-msvc\codex\codex-windows-sandbox-setup.exe (cwd=D:\repo\subdir, payload_len=668)
[2026-01-28T13:52:55.651159600+00:00] setup refresh: processed 3 write roots (read roots delegated); errors=[]
[2026-01-28 23:52:55.651 codex-windows-sandbox-setup.exe] setup binary completed
[2026-01-28T13:52:55.676336500+00:00] read-acl-only mode: applying read ACLs
[2026-01-28T13:52:55.679250100+00:00] read ACL run completed
[2026-01-28 23:52:55.734 codex-command-runner.exe] runner start cwd=D:\repo\subdir cmd=["C:\\Program Files\\WindowsApps\\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\\pwsh.exe", "-Command", "[Console]::OutputEncoding=[System.Text.Encoding]::UTF8;\nGet-Location"] real_codex_home=C:\Users\username\.codex
[2026-01-28 23:52:55.736 codex-command-runner.exe] runner: effective cwd=D:\repo\subdir (requested D:\repo\subdir)
[2026-01-28 23:52:55.745 codex-command-runner.exe] runner: spawn failed: CreateProcessAsUserW failed: 5
[2026-01-28 23:52:55.749 codex.exe] FAILURE: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command [Console]::OutputEncoding=[System.Text.Encoding]::UTF8;
Get-Location (exit code 1)
[2026-01-28 23:53:00.397 codex.exe] START: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command [Console]::OutputEncoding=[System.Text.Encoding]::UTF8;
Get-Location
[2026-01-28 23:53:00.407 codex.exe] setup refresh: spawning X:\scoop\persist\nodejs\bin\node_modules\@openai\codex\vendor\x86_64-pc-windows-msvc\codex\codex-windows-sandbox-setup.exe (cwd=D:\repo\subdir, payload_len=668)
[2026-01-28T13:53:00.434565+00:00] setup refresh: processed 3 write roots (read roots delegated); errors=[]
[2026-01-28 23:53:00.434 codex-windows-sandbox-setup.exe] setup binary completed
[2026-01-28T13:53:00.460019700+00:00] read-acl-only mode: applying read ACLs
[2026-01-28T13:53:00.462272800+00:00] read ACL run completed
[2026-01-28 23:53:00.514 codex-command-runner.exe] runner start cwd=D:\repo\subdir cmd=["C:\\Program Files\\WindowsApps\\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\\pwsh.exe", "-Command", "[Console]::OutputEncoding=[System.Text.Encoding]::UTF8;\nGet-Location"] real_codex_home=C:\Users\username\.codex
[2026-01-28 23:53:00.516 codex-command-runner.exe] runner: effective cwd=D:\repo\subdir (requested D:\repo\subdir)
[2026-01-28 23:53:00.526 codex-command-runner.exe] runner: spawn failed: CreateProcessAsUserW failed: 5
[2026-01-28 23:53:00.530 codex.exe] FAILURE: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command [Console]::OutputEncoding=[System.Text.Encoding]::UTF8;
Get-Location (exit code 1)
[2026-01-28 23:53:05.709 codex.exe] START: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command [Console]::OutputEncoding=[System.Text.Encoding]::UTF8;
pwd
[2026-01-28 23:53:05.719 codex.exe] setup refresh: spawning X:\scoop\persist\nodejs\bin\node_modules\@openai\codex\vendor\x86_64-pc-windows-msvc\codex\codex-windows-sandbox-setup.exe (cwd=D:\repo\subdir, payload_len=668)
[2026-01-28T13:53:05.753275800+00:00] setup refresh: processed 3 write roots (read roots delegated); errors=[]
[2026-01-28 23:53:05.753 codex-windows-sandbox-setup.exe] setup binary completed
[2026-01-28T13:53:05.777629900+00:00] read-acl-only mode: applying read ACLs
[2026-01-28T13:53:05.779460600+00:00] read ACL run completed
[2026-01-28 23:53:05.825 codex-command-runner.exe] runner start cwd=D:\repo\subdir cmd=["C:\\Program Files\\WindowsApps\\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\\pwsh.exe", "-Command", "[Console]::OutputEncoding=[System.Text.Encoding]::UTF8;\npwd"] real_codex_home=C:\Users\username\.codex
[2026-01-28 23:53:05.827 codex-command-runner.exe] runner: effective cwd=D:\repo\subdir (requested D:\repo\subdir)
[2026-01-28 23:53:05.836 codex-command-runner.exe] runner: spawn failed: CreateProcessAsUserW failed: 5
[2026-01-28 23:53:05.840 codex.exe] FAILURE: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command [Console]::OutputEncoding=[System.Text.Encoding]::UTF8;
pwd (exit code 1)
[2026-01-28 23:53:10.704 codex.exe] START: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command [Console]::OutputEncoding=[System.Text.Encoding]::UTF8;
cmd /c dir
[2026-01-28 23:53:10.714 codex.exe] setup refresh: spawning X:\scoop\persist\nodejs\bin\node_modules\@openai\codex\vendor\x86_64-pc-windows-msvc\codex\codex-windows-sandbox-setup.exe (cwd=D:\repo\subdir, payload_len=668)
[2026-01-28T13:53:10.741790300+00:00] setup refresh: processed 3 write roots (read roots delegated); errors=[]
[2026-01-28 23:53:10.741 codex-windows-sandbox-setup.exe] setup binary completed
[2026-01-28T13:53:10.767054+00:00] read-acl-only mode: applying read ACLs
[2026-01-28T13:53:10.769115900+00:00] read ACL run completed
[2026-01-28 23:53:10.819 codex-command-runner.exe] runner start cwd=D:\repo\subdir cmd=["C:\\Program Files\\WindowsApps\\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\\pwsh.exe", "-Command", "[Console]::OutputEncoding=[System.Text.Encoding]::UTF8;\ncmd /c dir"] real_codex_home=C:\Users\username\.codex
[2026-01-28 23:53:10.821 codex-command-runner.exe] runner: effective cwd=D:\repo\subdir (requested D:\repo\subdir)
[2026-01-28 23:53:10.832 codex-command-runner.exe] runner: spawn failed: CreateProcessAsUserW failed: 5
[2026-01-28 23:53:10.837 codex.exe] FAILURE: C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe -Command [Console]::OutputEncoding=[System.Text.Encoding]::UTF8;
cmd /c dir (exit code 1)

What steps can reproduce the bug?

See uploaded thread: 019c04d8-9c59-7222-

I believe I first encountered this error immediately after updating to the version where the elevated_windows_sandbox feature was shipped 1-2 weeks ago. Since then, I have noticed it occur in/with multiple different:

• repos/locations
• models
• sandbox/approval settings
• various other config.toml keys/values

The only thing that has consistently worked as a temporary fix has been disabling the elevated_windows_sandbox feature using command line flag/config.toml, and relying on the previous experimental_windows_sandbox feature instead.

What is the expected behavior?

Commands executed by the agent should follow whatever sandbox/policy settings are configured, i.e. read-only commands within the workspace should proceed without first requiring explicit approval and/or failing with (no output).

Additional information

I thought I would mention that, when I was doing some testing to try to find the root cause, I had this interaction with the model - and I am almost certain that I remember something very similar occurring a week or two ago, when I was troubleshooting the exact same sandbox issues:

╭───────────────────────────────────────────────────╮
│ >_ OpenAI Codex (v0.92.0)                         │
│                                                   │
│ model:     gpt-5.2-codex xhigh   /model to change │
│ directory: D:\repo\subdir                         │
╰───────────────────────────────────────────────────╯

› try running a simple cmd like get-childitem


• *Preparing to run shell command*

$ Get-ChildItem -Force
✗ (1) • 655ms

• *Preparing to rerun with escalated privileges*

$ Get-ChildItem -Force

    Directory: D:\repo\subdir

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d----          28/01/2026  5:19 AM                .ruff_cache
...
...

✓ • 1.21s

─ Worked for 16s ───────────────────────────────────────────────────────────────────────

• Ran Get-ChildItem -Force successfully. I can proceed with whatever you want next.


› why did the first attempt fail


• *The sandbox required escalation and produced no output with exit code 1, indicating a likely failure or blocked
  execution to address next.*

• The first run was blocked by sandbox permissions. It needed escalated access to list the workspace, so it exited with
  code 1 and no output. I re-ran it with escalated permissions and it succeeded.

Very much makes me wonder if perhaps the issue is with the model itself, or at least how it interacts with the harness/sandbox.... Though, judging by the system prompt's description of the on-request option for approval_policy, maybe there actually is an issue with the sandbox, as it doesn't sound like simple read-only commands, e.g. gci, should require escalation ? specifically wrt to below (apologies if I am looking at some unrelated piece of the framework lol):

... Here are scenarios where you'll need to request approval:\r\n- You need to run a command that writes to a directory that requires it (e.g. running tests that write to /var)\r\n- You need to run a GUI app (e.g., open/xdg-open/osascript) to open browsers or files.\r\n- You are running sandboxed and need to run a command that requires network access (e.g. installing packages)\r\n- If you run a command that is important to solving the user's query, but it fails because of sandboxing, rerun the command with approval. ALWAYS proceed to use the `sandbox_permissions` and `justification` parameters - do not message the user before requesting approval for the command.\r\n- You are about to take a potentially destructive action such as an `rm` or `git reset` that the user did not explicitly ask for. ...

[iceweasel-oai]

Hi there @i4TsU - thanks for the detailed report and I'm sorry you're running into issues with the elevated sandbox. It appears that the sandbox is unable to execute your version of powershell. Can you run the following commands and let me know their output? That will help further diagnose the issue and lead me towards an appropriate fix:

* where.exe pwsh
* where.exe powershell
* Get-Command pwsh, powershell | Select-Object Name, Source, Path
* Get-AppxPackage -Name Microsoft.PowerShell -AllUsers | Select-Object Name, PackageFullName, InstallLocation
* icacls "C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe"
* C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -Command "$PSVersionTable.PSVersion"

[i4TsU]

No worries! :)

> where.exe pwsh
C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\pwsh.exe



> where.exe powershell
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe



> Get-Command pwsh, powershell | Select-Object Name, Source, Path

Name           Source                                                                                Path
----           ------                                                                                ----
pwsh.exe       C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe
powershell.exe C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe                             C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe



> Get-AppxPackage -Name Microsoft.PowerShell -AllUsers | Select-Object Name, PackageFullName, InstallLocation

Name                 PackageFullName                                 InstallLocation
----                 ---------------                                 ---------------
Microsoft.PowerShell Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe



> icacls "C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe"
C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe BUILTIN\Users:(I)(Rc,S,RD,REA,X,RA)
                                                                                      S-1-15-3-3474344596-1361774275-169937050-1715369765-655753896-4292765343-1302149271:(I)(RX)
                                                                                      BUILTIN\Users:(I)(R)
                                                                                      NT SERVICE\TrustedInstaller:(I)(F)
                                                                                      S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(I)(RX)
                                                                                      NT AUTHORITY\SYSTEM:(I)(F)
                                                                                      NT AUTHORITY\LOCAL SERVICE:(I)(RX)
                                                                                      NT AUTHORITY\NETWORK SERVICE:(I)(RX)
                                                                                      NT AUTHORITY\RESTRICTED:(I)(RX)
                                                                                      S-1-19-512-4096:(RX,D,WDAC,WO,WA)

Successfully processed 1 files; Failed processing 0 files



> C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -Command '$PSVersionTable.PSVersion'

Major  Minor  Build  Revision
-----  -----  -----  --------
5      1      26100  7462

[iceweasel-oai]

thank you for the quick reply. I'm still working to reproduce/diagnose the issue. In the meantime, I think you have two options

1. continue to use the experimental_windows_sandbox feature instead of the elevated one. For nearly all use cases, it is just as good
2. One thing you could try is removing the pwsh that was installed via the Windows Store, and re-installing using winget. Totally optional, but if you go this route let me know if it works. It will provide some useful debugging information:

Get-AppxPackage -Name Microsoft.PowerShell | Remove-AppxPackage
winget install Microsoft.PowerShell

[i4TsU]

Reinstalling pwsh seems to have solved the issues with the sandbox :) I was able to do a little testing between other things - I just uploaded a "post-fix" session (Thread ID: 019c0d0d-f58f-7160-bbbe-9a0bf0364ce8), and linked this GitHub Issue in the feedback notes too, but I will try to summarise what I observed below, along with some additional info from before reinstalling pwsh:

---

• Further to your first message yesterday, I was able to confirm that - at the very least - attempting to run my main pwsh.exe as CodexSandboxOffline user via PsExec resulted in a similar failure:

  > psexec64 -u CodexSandboxOffline -p codex cmd /c "C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe" -Command "Get-ChildItem -Force"
  
  PsExec v2.43 - Execute processes remotely
  Copyright (C) 2001-2023 Mark Russinovich
  Sysinternals - www.sysinternals.com
  
  cmd exited with error code 1.

• After your most recent message, I installed pwsh using the native installer via scoop (scoop install pwsh --global).

• I then ran Get-AppxPackage -Name Microsoft.PowerShell | Remove-AppxPackage as suggested.

• Final state:

  > where.exe pwsh
  X:\ProgramData\scoop\apps\pwsh\current\pwsh.exe
  X:\ProgramData\scoop\shims\pwsh.exe
  
  
  > where.exe powershell
  C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
  
  
  > Get-Command pwsh, powershell | Select-Object Name, Source, Path
  
  Name           Source                                                    Path
  ----           ------                                                    ----
  pwsh.exe       X:\ProgramData\scoop\apps\pwsh\current\pwsh.exe           X:\ProgramData\scoop\apps\pwsh\current\pwsh.exe
  powershell.exe C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
  
  
  
  > Get-AppxPackage -Name Microsoft.PowerShell -AllUsers | Select-Object Name, PackageFullName, InstallLocation
  
  
  > icacls 'X:\ProgramData\scoop\apps\pwsh\current\pwsh.exe'
  X:\ProgramData\scoop\apps\pwsh\current\pwsh.exe BUILTIN\Administrators:(I)(F)
                                                  NT AUTHORITY\SYSTEM:(I)(F)
                                                  NT AUTHORITY\Authenticated Users:(I)(M)
                                                  BUILTIN\Users:(I)(RX)
  
  Successfully processed 1 files; Failed processing 0 files
  
  
  > X:\ProgramData\scoop\apps\pwsh\current\pwsh.exe -NoProfile -Command '$PSVersionTable.PSVersion'
  
  Major  Minor  Patch  PreReleaseLabel BuildLabel
  -----  -----  -----  --------------- ----------
  7      5      4
  
  
  > scoop info pwsh
  
  Name        : pwsh
  Description : Cross-platform automation and configuration tool/framework, known as Powershell Core, that works well with existing tools and is optimized for dealing with structured data.
  Version     : 7.5.4
  Source      : main
  Website     : https://github.com/PowerShell/PowerShell
  License     : MIT
  Updated at  : 21/10/2025 6:29:25 AM
  Updated by  : github-actions[bot]
  Installed   : 7.5.4 *global*
  Binaries    : pwsh.exe
  Shortcuts   : PowerShell Core
  Notes       : Since Scoop uses pwsh.exe internally, to update PowerShell Core itself,
                run `scoop update pwsh` from Windows PowerShell, i.e. powershell.exe.
  
                Add PowerShell Core as a explorer context menu by running: '<root>\install-explorer-context.reg'
                For file context menu, run '<root>\install-file-context.reg'

---

This morning, I then tried running the same tests in a new codex session, using the same location + config as before:

• Initially sandboxed commands were failing with error 1326 as I forgot about changing the password of the sandbox local user for the earlier PsExec tests
• After removing both elevated_windows_sandbox = true and experimental_windows_sandbox = true from my config.toml and launching a new session + reenabling the elevated sandbox when prompted, everything worked as expected with no further issues (except for an "Access denied" error related to the oh-my-posh init in my $PROFILE)
  • This final session, where I confirmed everything worked, is the only one I remembered to submit via /feedback unfortunately, but hopefully you have enough info from everything else to determine whether or not any further action is warranted :)
• Final results (using identical on-request/workspace-write permissions):
  • Get-ChildItem inside workspace: now executes successfully inside of the sandbox (model no longer needs to escalate/request approval)
  • 'Set-Content' succeeded both inside and outside of the workspace, without needing approval/escalation - not sure if that is intended or not ?
  • However, the apply_patch tool behaved exactly as expected, requiring manual approval when modifying files outside of the workspace, and applying changes successfully and without approval

---

Hopefully that helps with repro/identifying the issue and whether or not it is worth safeguarding against lol - and, if not, hopefully you did not waste too much time on it :). Thanks for your help in any case, and let me know if you want me to share any other details/run any tests etc.!

[chausner]

I am experiencing the same issue here. Any PowerShell command that Codex attempts to run gives no output. It started with some of the latest codex updates. I can confirm that disabling elevated_windows_sandbox and enabling experimental_windows_sandbox fixes the issue.

What version of Codex is running?
codex-cli 0.94.0

Which model were you using?
gpt-5.2-codex

What platform is your computer?
Windows 11 25H2 10.0.26220.0 x64

What terminal emulator and version are you using (if applicable)?
Windows Terminal running PowerShell-7.5.4

Here's the output of the commands you requested above:

> where.exe pwsh
C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe
C:\Users\chris\AppData\Local\Microsoft\WindowsApps\pwsh.exe

> where.exe powershell
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

> Get-Command pwsh, powershell | Select-Object Name, Source, Path | fl

Name : pwsh.exe
Source : C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe
Path : C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe

Name : powershell.exe
Source : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Path : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

> Get-AppxPackage -Name Microsoft.PowerShell -AllUsers | Select-Object Name, PackageFullName, InstallLocation | fl

Name : Microsoft.PowerShell
PackageFullName : Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe
InstallLocation : C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe

> icacls "C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe"
C:\Program Files\WindowsApps\Microsoft.PowerShell_7.5.4.0_x64__8wekyb3d8bbwe\pwsh.exe VORDEFINIERT\Benutzer:(I)(Rc,S,RD,REA,X,RA)
S-1-15-3-3474344596-1361774275-169937050-1715369765-655753896-4292765343-1302149271:(I)(RX)
VORDEFINIERT\Benutzer:(I)(R)
NT SERVICE\TrustedInstaller:(I)(F)
S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(I)(RX)
NT-AUTORITÄT\SYSTEM:(I)(F)
NT-AUTORITÄT\Lokaler Dienst:(I)(RX)
NT-AUTORITÄT\Netzwerkdienst:(I)(RX)
NT-AUTORITÄT\EINGESCHRÄNKTER ZUGRIFF:(I)(RX)
S-1-19-512-4096:(I)(RX,D,WDAC,WO,WA)

> C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -Command "$PSVersionTable.PSVersion"

Major Minor Build Revision

---

5 1 26100 7670

[jastranlove2020]

For anyone has problem, codex run without std output, i have success case to fix it fine.
It is dll windows missing. install

https://download.visualstudio.microsoft.com/download/pr/7ebf5fdb-36dc-4145-b0a0-90d3d5990a61/CC0FF0EB1DC3F5188AE6300FAEF32BF5BEEBA4BDD6E8E445A9184072096B713B/VC_redist.x64.exe

Then restart, it should work for you.

[etraut-openai]

@jastranlove2020, thanks for sharing your solution. Much appreciated!

[chausner]

For anyone has problem, codex run without std output, i have success case to fix it fine. It is dll windows missing. install

https://download.visualstudio.microsoft.com/download/pr/7ebf5fdb-36dc-4145-b0a0-90d3d5990a61/CC0FF0EB1DC3F5188AE6300FAEF32BF5BEEBA4BDD6E8E445A9184072096B713B/VC_redist.x64.exe

Then restart, it should work for you.

Don't think this is the root cause in my case. I already had the latest version of the VC++ x64 Redistributable installed. In my case, it's probably related to PowerShell being installed via the Windows Store (see the earlier comments by @i4TsU).