[Bug] Sandbox setup fails with "read ACL run had errors" on Windows 11 Home (Build 26200) — v26.609.9530.0

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

26.609.9530.0

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Every task fails immediately. The Codex UI shows:

"Could not verify sandbox status / You can continue in read-only mode"

Additionally:
"The 'gpt-5.5' model requires a newer version of Codex. Please upgrade to the latest app or CLI and try again."

setup_error.json:
{
"code": "helper_unknown_error",
"message": "read ACL run had errors"
}

sandbox log (sandbox.2026-06-15.log):
[2026-06-16 08:42:22.583 codex.exe] START: C:\Users\<user>\AppData\Local\OpenAI\Codex\runtimes\cua_node\789504f803e82e2b\bin\node.exe --experimental-vm-modules ...
[2026-06-16 08:43:01.523 codex.exe] START: (same line repeated, process never completes sandbox setup)

What steps can reproduce the bug?

1. Install Codex App v26.609.9530.0 on Windows 11 Home (Build 10.0.26200, x64)
2. Enable WSL mode (runCodexInWindowsSubsystemForLinux = true)
3. Open any workspace and start any task
4. Codex immediately shows sandbox error and falls back to read-only mode

What is the expected behavior?

Sandbox initializes successfully on Windows 11 Home, or a clear error message is shown explaining that Home edition is not supported.

Additional information

• Windows 11 Home does not include the Windows Sandbox optional feature

(Get-WindowsOptionalFeature returns no output for "Containers-DisposableClientVM")

• However, per OpenAI's May 13 blog post, Codex Windows sandbox uses restricted tokens/ACLs,

not Windows Sandbox — so Home should theoretically be supported

• HyperVisorPresent: True (virtualization is enabled)
• Tried setting RUNASINVOKER in HKEY_USERS\<GUI-SID>\AppCompatFlags\Layers → no effect
• App is already latest version (winget upgrade shows no available upgrades)
• WSL mode is enabled; node process starts but sandbox ACL setup fails
• Related issues: #26737, #26266, #13378