Node REPL kernel fails to start: CreateProcessAsUserW failed: 5

Open 💬 6 comments Opened Jun 10, 2026 by weixuefeng1244-alt
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Codex 版本: 0.138.0-alpha.7

What subscription do you have?

What platform is your computer?

win11

What issue are you seeing?

环境

  • OS: Windows 11 26200 (zh-CN)
  • Codex 版本: 0.138.0-alpha.7

问题

Codex 的 Node REPL 内核始终无法启动,导致无法控制 Chrome 浏览器和应用内浏览器。错误信息:

windows sandbox failed: runner error: CreateProcessAsUserW failed: 5

已尝试的修复(均无效)

  • 以管理员身份运行 Codex
  • 关闭 Windows Defender 实时保护
  • 关闭内存完整性(内核隔离)
  • 重启 Codex / 重启电脑
  • Chrome 扩展已安装且启用(v1.1.5)
  • 本地通信桥接配置正确

备注

  • codex doctor 显示网络也无法连接
  • 普通 Shell 命令正常运行
  • 仅 MCP / Node REPL 内核启动失败

What steps can reproduce the bug?

环境

  • OS: Windows 11 26200 (zh-CN)
  • Codex 版本: 0.138.0-alpha.7

问题

Codex 的 Node REPL 内核始终无法启动,导致无法控制 Chrome 浏览器和应用内浏览器。错误信息:

windows sandbox failed: runner error: CreateProcessAsUserW failed: 5

已尝试的修复(均无效)

  • 以管理员身份运行 Codex
  • 关闭 Windows Defender 实时保护
  • 关闭内存完整性(内核隔离)
  • 重启 Codex / 重启电脑
  • Chrome 扩展已安装且启用(v1.1.5)
  • 本地通信桥接配置正确

备注

  • codex doctor 显示网络也无法连接
  • 普通 Shell 命令正常运行
  • 仅 MCP / Node REPL 内核启动失败

What is the expected behavior?

可以正常操控我的浏览器进行其他动作

Additional information

_No response_

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #26803
  • #26186
  • #26896
  • #26644
  • #26266

Powered by Codex Action

etraut-openai contributor · 1 month ago

English translation:

What version of the Codex App are you using (From “About Codex” dialog)?

Codex version: 0.138.0-alpha.7

What subscription do you have?

None

What platform is your computer?

win11

What issue are you seeing?

Environment

  • OS: Windows 11 26200 (zh-CN)
  • Codex version: 0.138.0-alpha.7

Issue

Codex's Node REPL kernel consistently fails to start, preventing control of the Chrome browser and the in-app browser. Error message:

windows sandbox failed: runner error: CreateProcessAsUserW failed: 5

Attempted fixes (none worked)

  • Ran Codex as administrator
  • Disabled Windows Defender real-time protection
  • Disabled Memory Integrity (Core Isolation)
  • Restarted Codex / restarted the computer
  • Chrome extension is installed and enabled (v1.1.5)
  • Local communication bridge is configured correctly

Notes

  • codex doctor shows that the network also cannot connect
  • Regular Shell commands run normally
  • Only the MCP / Node REPL kernel fails to start

What steps can reproduce the bug?

Environment

  • OS: Windows 11 26200 (zh-CN)
  • Codex version: 0.138.0-alpha.7

Issue

Codex's Node REPL kernel consistently fails to start, preventing control of the Chrome browser and the in-app browser. Error message:

windows sandbox failed: runner error: CreateProcessAsUserW failed: 5

Attempted fixes (none worked)

  • Ran Codex as administrator
  • Disabled Windows Defender real-time protection
  • Disabled Memory Integrity (Core Isolation)
  • Restarted Codex / restarted the computer
  • Chrome extension is installed and enabled (v1.1.5)
  • Local communication bridge is configured correctly

Notes

  • codex doctor shows that the network also cannot connect
  • Regular Shell commands run normally
  • Only the MCP / Node REPL kernel fails to start

What is the expected behavior?

I should be able to control my browser normally to perform other actions

Additional information

_No response_

<!-- codex-issue-translator -->

buckaroo54 · 1 month ago

I’m seeing what appears to be the same issue on Windows Codex Desktop.

Chrome plugin and Computer Use are installed/enabled, and the Chrome extension reports as connected, but both Chrome control and Computer Use fail before startup with this error:

node_repl kernel exited unexpectedly
windows sandbox failed: runner error: CreateProcessAsUserW failed: 5

This happens when trying to initialize the Chrome extension runtime and also when trying to initialize Computer Use. Normal shell/file operations in Codex work, and OneDrive write escalation now works, so this seems specific to the Node/browser/Computer Use helper startup path rather than general local command execution.

Environment:

  • Windows: Windows 11 Home, Version 25H2, OS Build 26200.8457, Windows Feature Experience Pack 1000.26100.304.0
  • Codex Desktop: 26.609.30741
  • Chrome extension: installed and connected
  • Plugins: Chrome and Computer Use installed/enabled
old4693000-byte · 1 month ago

I am seeing the same failure pattern on Windows Codex Desktop and filed a related report here: https://github.com/openai/codex/issues/27792

My case is specifically the Chrome plugin path:

  • Chrome plugin / Codex Chrome Extension installed and enabled
  • Chrome extension version: 1.1.5_0
  • Selected Chrome profile: Default
  • Native Messaging Host manifest and registry checks pass (correct: true)
  • Chrome itself is installed and running
  • @chrome fails before it can list or access current Chrome tabs

Observed error:

node_repl kernel exited unexpectedly
windows sandbox failed: runner error: CreateProcessAsUserW failed: 5

Additional local signal: running codex --version from the Codex workspace PowerShell also failed with Access denied, so this looks like the same Windows sandbox / Node helper startup path rather than a Chrome extension installation problem.

old4693000-byte · 1 month ago

I am seeing the same failure pattern on Windows Codex Desktop and filed a related report here: https://github.com/openai/codex/issues/27792

My case is specifically the Chrome plugin path:

  • Chrome plugin / Codex Chrome Extension installed and enabled
  • Chrome extension version: 1.1.5_0
  • Selected Chrome profile: Default
  • Native Messaging Host manifest and registry checks pass (correct: true)
  • Chrome itself is installed and running
  • @chrome fails before it can list or access current Chrome tabs

Observed error:

node_repl kernel exited unexpectedly
windows sandbox failed: runner error: CreateProcessAsUserW failed: 5

Additional local signal: running codex --version from the Codex workspace PowerShell also failed with Access denied, so this looks like the same Windows sandbox / Node helper startup path rather than a Chrome extension installation problem.

old4693000-byte · 1 month ago

I am seeing the same failure pattern on Windows Codex Desktop and filed a related report here: https://github.com/openai/codex/issues/27792

My case is specifically the Chrome plugin path:

  • Chrome plugin / Codex Chrome Extension installed and enabled
  • Chrome extension version: 1.1.5_0
  • Selected Chrome profile: Default
  • Native Messaging Host manifest and registry checks pass (correct: true)
  • Chrome itself is installed and running
  • @chrome fails before it can list or access current Chrome tabs

Observed error:

node_repl kernel exited unexpectedly
windows sandbox failed: runner error: CreateProcessAsUserW failed: 5

Additional local signal: running codex --version from the Codex workspace PowerShell also failed with Access denied, so this looks like the same Windows sandbox / Node helper startup path rather than a Chrome extension installation problem.