codex-5.1 or 5.1 max keep failing when using powershell

Resolved 💬 4 comments Opened Nov 20, 2025 by rockyicer Closed Nov 20, 2025
💡 Likely answer: A maintainer (dylan-hurd-oai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.4.46

What subscription do you have?

gpt pro

Which model were you using?

codex-5.1 + 5.1 max

What platform is your computer?

window

What issue are you seeing?

I use the codex inside vscode. after I get some update to 5.1 from yestoday, i keep meet the fails to using the powershell in windows.

<img width="1761" height="1147" alt="Image" src="https://github.com/user-attachments/assets/78339abc-3a30-4aed-85c3-cc8336f3eb65" />

also when I copy the text from the answer, the chinese letter will shows ????. -> the issue i met it before and it is been fix already long time, but with 5.1 or 5.1 max, it pop up again.

and the sad thing is : i WANT TO GO BACK TO codex-5 and I do not have that option...

What steps can reproduce the bug?

$ 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' -Command 'rg -n "SYST:CONF:EDEV" -S D:\Documents\measurements'

$ 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' -Command 'rg -n "SYST:CONF:EDEV" -S -g"*.m" D:\Documents'
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='cp1252'>
OSError: [Errno 22] Invalid argument

$ 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe' -Command 'Get-ChildItem -Path D:\Documents -Filter ExternalDevices.m -Recurse -ErrorAction SilentlyContinue'

Directory: D:\Documents\measurements\+n5247b
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 9/22/2025 7:39 PM 5173 ExternalDevices.m

Directory: D:\Documents\measurements\+n5247b
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 9/22/2025 7:39 PM 5173 ExternalDevices.m

What is the expected behavior?

gpt codex previous is quite smooth to do the job....

Additional information

_No response_

View original on GitHub ↗

4 Comments

nos1609 · 9 months ago

But looks like cosmetical issue

rockyicer · 9 months ago

ah, it is my stupid, fail means the running the python is failed, not means the powershell failed.

dylan-hurd-oai contributor · 9 months ago
fail means the running the python is failed

@rockyicer can you explain what you mean by this?

rockyicer · 9 months ago
> fail means the running the python is failed > @rockyicer can you explain what you mean by this?

so when the codex show fails, means that the python that i wrote is not working, not means that the powershell send the wrong command.
previous, i though the powershell is not sending the right command from codex
so inshort, the codex works nicely. but the way codex shows inthe IDE is a bit confusing for me for a day.