Windows desktop app repeatedly fails with "timeout waiting for child process to exit" due to sandbox ACL failure in WindowsApps

Open 💬 6 comments Opened Apr 13, 2026 by Ori-Laphicet
💡 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)?

26.409.1734.0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 Home China, version 10.0.26200, x64

What issue are you seeing?

The Codex Windows desktop app frequently fails even in a blank conversation with:

timeout waiting for child process to exit

This happens after repeated reconnect attempts, and sometimes only works after several retries.

I investigated locally and found that the failure appears to happen during Windows sandbox setup. Codex repeatedly tries to grant a read ACL / ACE to its install resources under:

C:\Program Files\WindowsApps\OpenAI.Codex_...\app\resources

The local sandbox log shows:

SetNamedSecurityInfoW failed: 5

and:

read ACL run had errors

This reproduces even in a blank conversation and also after rebooting the computer.

What steps can reproduce the bug?

  1. Launch the Codex desktop app on Windows.
  2. Start a blank conversation.
  3. Send a simple message such as "你好".
  4. The app shows repeated reconnect attempts.
  5. It eventually reports: "timeout waiting for child process to exit".

This can also happen after restarting the computer.

<img width="1218" height="492" alt="Image" src="https://github.com/user-attachments/assets/6603100f-37ba-46f8-95a0-e2bfc53a7db3" />

What is the expected behavior?

Codex should respond normally in a blank conversation without reconnect loops, and sandbox initialization should not fail when starting the app or sending a simple message.

Additional information

Additional local findings:

The issue appears related to Windows sandbox initialization, not to any child process I manually started.

Relevant local files:
C:\Users\10793\.codex\.sandbox\setup_error.json
C:\Users\10793\.codex\.sandbox\sandbox.log

The setup error file contains:
{
"code": "helper_unknown_error",
"message": "read ACL run had errors"
}

Relevant sandbox log lines include:
granting read ACE to C:\Program Files\WindowsApps\OpenAI.Codex_...\app\resources for sandbox users
grant read ACE failed on C:\Program Files\WindowsApps\OpenAI.Codex_...\app\resources for sandbox_group: SetNamedSecurityInfoW failed: 5
read ACL run completed with errors
setup error: read ACL run had errors

Additional notes:

  • The ACL write succeeds only when performed from a truly elevated PowerShell process.
  • However, launching the Microsoft Store version of Codex "as administrator" does not appear to reliably make the actual sandbox helper run with the effective privilege needed for this ACL step.
  • Codex requires sandbox mode, so disabling sandbox is not a usable workaround.

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 3 months ago

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

  • ##17610
  • ##16502
  • ##17137
  • ##16676

Powered by Codex Action

steven42121 · 3 months ago

It‘s useful to rename the config.toml and let codex create a new file itself when setting up sandbox.
However,you could not edit config.toml.
I'm waiting for the repair!

ForceofwiII · 2 months ago

你解决了吗

lalala8462 · 2 months ago

重装 codex + 开启 TUN 可以避免这个问题
老版本codex.exe在 .sandbox-bin 目录下,但是只是更新版本似乎不会改变codex.exe版本号, 最新125版本 codex.exe已经换了布局方式可以干脆卸载重装试试

steven42121 · 2 months ago
你解决了吗

我解决了
tun模式那些我都不行,但是我从一个codex正常的电脑上把.codex文件夹完全复制过来就行了😂

Ori-Laphicet · 2 months ago
你解决了吗

我试了重装codex + 开启TUN ,确实可以了。另外还观察到如果用api登录就不会遇到这个问题。猜测是账号登录时会话开始前加载了什么服务,但这个服务没有走代理,导致一直连接失败,开启tun模式强制走代理就可以连接成功。
至于我的问题描述,是 Codex 自己写的,他说是由于权限问题,但现在看来应该不是这个原因