-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Open
Labels
CLIIssues related to the Codex CLIIssues related to the Codex CLIbugSomething isn't workingSomething isn't workingwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems
Description
What version of Codex is running?
0.66.0
What subscription do you have?
ChatGPT Plus
Which model were you using?
Not applicable (Codex fails before model selection).
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What issue are you seeing?
Codex CLI fails to start on Windows. Running any command like:
codex
codex --version
codex --sandbox none
results in:
node:internal/child_process:421
throw new ErrnoException(err, 'spawn');
^
Error: spawn EPERM
at ChildProcess.spawn (node:internal/child_process:421:11)
at spawn (node:child_process:796:9)
at file:///C:/Tools/Dev/nvm/v24.11.0/node_modules/@openai/codex/bin/codex.js:115:15
at ModuleJob.run (node:internal/modules/esm/module_job:377:25)
at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:691:26)
at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5) {
errno: -4048,
code: 'EPERM',
syscall: 'spawn'
}
Node.js v24.11.0
There is no output when running: where codex
What steps can reproduce the bug?
- Install Node via NVM (Node v24.11.0)
- Run:
npm uninstall -g @openai/codex
npm cache clean --force - Verify folder removed:
npm ls -g | Select-String codex - Fresh install:
npm install -g @openai/codex - Try launching:
codex --version
codex --sandbox none - Result: always returns
spawn EPERMand aborts.
What is the expected behavior?
Codex CLI should start normally and print the version.
It should not fail with EPERM spawn errors on a clean Windows installation.
Additional information
- I performed a full clean reinstall using NVM and npm.
- No antivirus alerts and Controlled Folder Access is off.
- The CLI does not create a visible binary or Windows blocks spawning it.
- Running
where codexreturns nothing. - Running inside WSL2 works, so this seems Windows-specific.
Powershell Version: 7.5.4
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
CLIIssues related to the Codex CLIIssues related to the Codex CLIbugSomething isn't workingSomething isn't workingwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems