6 people reported
All time, since Sep 19, including 4 thumbs-up on GitHub.
Update fails on Get-FileHash
“codex update always shells out to powershell.exe (Windows PowerShell 5.1) internally, regardless of which shell the user is actually running codex from.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/15882/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Windows update fails because Get-FileHash is not recognized. codex update shells out to powershell.exe (Windows PowerShell 5.1) internally, even when run from PowerShell 7, after checksum download fails.
Is this your bug?
File my report- Where
- installer
- Error text
iex : The term 'Get-FileHash' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correctError: `powershell -ExecutionPolicy Bypass -c '$env:CODEX_NON_INTERACTIVE=1; irm https://chatgpt.com/codex/install.ps1 | iex'` failed with status exit code: 1Pasted in 2 reports- Versions
- 0.147.0 to 0.154.0
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Daemon access denied on Windows7 people
- Code-mode host not found3 people
Original reports2, newest first
- Error:
powershell -ExecutionPolicy Bypass -c '$env:CODEX_NON_INTERACTIVE=1; irm https://chatgpt.com/codex/install.ps1 | iex'failed with status exit code: 1On GitHub#47488 - codex update fails on Windows when Windows PowerShell 5.1's Get-FileHash is unavailable (even when invoked from PowerShell 7)On GitHub#46684