Windows desktop app elevated sandbox setup resolves codex-windows-sandbox-setup.exe to package root instead of app\resources

What issue are you seeing?

On Windows, the Codex desktop app can show a native Windows error dialog when elevated sandbox setup is triggered. The dialog attempts to launch:

C:\Program Files\WindowsApps\OpenAI.Codex_<version>_x64__2p2nqsd0c76g0\codex-windows-sandbox-setup.exe

This root-level path does not exist in the MSIX package. On the affected install, the actual executable exists at:

C:\Program Files\WindowsApps\OpenAI.Codex_<version>_x64__2p2nqsd0c76g0\app\resources\codex-windows-sandbox-setup.exe

The Windows dialog message is localized Chinese:

找不到指定的模块。

Equivalent English meaning: "The specified module could not be found."

Environment

• OS: Windows 11 x64, zh-CN locale
• Codex desktop app package observed: OpenAI.Codex_26.623.19656.0_x64__2p2nqsd0c76g0
• Codex CLI/runtime observed: 0.142.5
• Microsoft Store / WindowsApps install layout

Reproduction conditions observed

1. Use Codex desktop app on Windows.
2. Have the following config present in ~/.codex/config.toml:

[windows]
sandbox = "elevated"

1. Start an action that triggers Windows sandbox setup / setup helper.
2. A native Windows error dialog appears pointing to the package root path for codex-windows-sandbox-setup.exe.

Actual behavior

The desktop app / elevated setup helper appears to resolve the setup executable as if it were in the package install root:

...\OpenAI.Codex_<version>_x64__2p2nqsd0c76g0\codex-windows-sandbox-setup.exe

That path is missing, so Windows displays "找不到指定的模块。"

Expected behavior

The setup helper should resolve and launch the executable under:

...\OpenAI.Codex_<version>_x64__2p2nqsd0c76g0\app\resources\codex-windows-sandbox-setup.exe

or otherwise dynamically resolve the current package install location and append app\resources\codex-windows-sandbox-setup.exe.

Additional notes

• Local sandbox logs from codex.exe show successful setup refreshes when using the correct app\resources\codex-windows-sandbox-setup.exe path.
• Removing [windows] sandbox = "elevated" avoids the native error dialog, but the desktop app/settings flow can later recreate that config, which makes the issue recur.
• This looks like a path resolution bug in the Windows desktop app / elevated sandbox setup path, not a missing file in the package.