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_
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
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
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)
Notes
What steps can reproduce the bug?
Environment
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)
Notes
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 -->
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 unexpectedlywindows sandbox failed: runner error: CreateProcessAsUserW failed: 5This 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:
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:
correct: true)@chromefails before it can list or access current Chrome tabsObserved error:
Additional local signal: running
codex --versionfrom 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.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:
correct: true)@chromefails before it can list or access current Chrome tabsObserved error:
Additional local signal: running
codex --versionfrom 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.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:
correct: true)@chromefails before it can list or access current Chrome tabsObserved error:
Additional local signal: running
codex --versionfrom 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.