Windows: background daemon still fails with "Access is denied (os error 5)" on Codex CLI 0.160.1 #51339

What version of Codex CLI is running?

codex-cli 0.160.1

What subscription do you have?

Plus

Which model were you using?

GPT-6.1-Sol

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

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

PowerShell

Codex doctor report

What issue are you seeing?

The background daemon still fails to start on Windows with:

Error: Access is denied. (os error 5)
To work without the background server, rerun the same command with --no-daemon (including resume or fork and its arguments).

This issue has persisted across several Codex CLI releases and is still reproducible on 0.160.1.

Codex itself works normally when the background daemon is disabled using --no-daemon, which suggests that the issue is specifically related to the background daemon rather than the CLI itself.

What steps can reproduce the bug?

1. Install/update Codex CLI globally through npm.

2. Confirm the installed version:
   codex --version
   Output:
   codex-cli 0.160.1

3. Run Codex normally:
   codex

4. Codex immediately fails with:

Error: Access is denied. (os error 5)
To work without the background server, rerun the same command with --no-daemon (including resume or fork and its arguments).

5. Run Codex again with the daemon disabled:
   codex --no-daemon

6. Codex starts and works normally.

What is the expected behavior?

Running:

codex

should start Codex normally with the background daemon enabled.

The daemon should not fail with a Windows Access is denied (os error 5) error.

Additional information

Node.js: v24.19.0
npm: 11.17.0