Errow spawn EFType on trying to launch

[Draass]

What version of Codex is running?

No response

Which model were you using?

No response

What platform is your computer?

No response

What steps can reproduce the bug?

Install it via npm install -g @just-every/code

What is the expected behavior?

App launches

What do you see instead?

node:internal/child_process:420
throw new ErrnoException(err, 'spawn');
^

Error: spawn EFTYPE
at ChildProcess.spawn (node:internal/child_process:420:11)
at spawn (node:child_process:753:9)
at file:///C:/Users/Professional/AppData/Roaming/npm/node_modules/@just-every/code/bin/coder.js:135:15 {
errno: -4028,
code: 'EFTYPE',
syscall: 'spawn'
}

Additional information

Method with uninstalling, installing, cleaning cache, running npx, etc. don't seem to help
Also if you try to use code-x86_64-pc-windows-msvc.exe manually, it is also not working. Looks like binary is corrupted in some way

[Draass]

Did some testing, worked after turning vpn off. Maybe it has something to do with download speed
ps. but does not work from wsl :) binary not found

[zemaj]

Thank you: Thanks for the report and extra detail - super helpful.
Likely cause: The Windows binary download was truncated by VPN/proxy/slow link, so Node tried to spawn a corrupt .exe (EFTYPE). We hardened installs to detect this and retry.

Try latest (fresh run):

npm uninstall -g @just-every/code
npm cache clean --force

Temporarily disable VPN/AV or whitelist release-assets.githubusercontent.com
npx -y @just-every/code@latest --version
If that works, you can then do: npm install -g @just-every/code@latest

If using WSL: Install and run inside WSL (Windows globals won’t work from WSL).
· In WSL: npx -y @just-every/code@latest --version
· If you want to run from Windows, use PowerShell/CMD instead of WSL.

If it still fails: Please paste the exact output plus:
· node -v and npm -v
· where code and where coder
· Size of the binary: dir
"%APPDATA%\npm\node_modules@just-every\code\bin\code-x86_64-pc-windows-msvc.exe"

Notes: We now verify downloads (retries, timeouts, Content-Length) and validate the binary header before running; failures should show clearer guidance instead of EFTYPE.