[Windows] Computer Use fails with `spawn EPERM` after Codex update

Start with the Computer Use controller entry points used by sky.list_windows() and sky.launch_app(), comparing app version 26.730.8199.0 with runtime 26.730.61639. Inspect the bundled cua_node runtime and the spawn path, then reproduce on Windows 10 with normal and elevated Codex processes. Done means Computer Use can enumerate windows and launch an allowed application without spawn EPERM.

Summary

Computer Use worked on Codex app version 26.727.6591.0, but after the Microsoft Store updated the app to 26.730.8199.0, every Computer Use action fails immediately with spawn EPERM, before windows can be enumerated or any application can be controlled.

The failure reproduces both in an existing task and in a newly created Work task.

Environment

• Windows 10 Enterprise 22H2 (build 19045.6456)
• Codex app: 26.730.8199.0
• Computer Use plugin/runtime: 26.730.61639
• Same result when Codex is started normally or elevated

Steps to reproduce

1. Install and enable the Computer Use plugin and skill.
2. Click Try now or create a new Work task.
3. Ask Computer Use to inspect the visible desktop/RDP window or launch an allowed Windows application.
4. The first controller action fails immediately.

Examples that fail:

• sky.list_windows()
• sky.launch_app({ app: "winword.exe" })

Actual behavior

The local Computer Use controller returns spawn EPERM before listing windows. No mouse, keyboard, application, or RDP interaction occurs.

Expected behavior

Computer Use should enumerate visible windows and control an allowed Windows application, as it did before the app update.

Troubleshooting already performed

• Repaired the Codex app through Windows Settings.
• Uninstalled and reinstalled the Computer Use plugin.
• Restarted Codex and reproduced in a new task.
• Regenerated the bundled cua_node runtime from scratch.
• Verified that the bundled controller executable exists and has Read/Execute permission.
• Verified that the native controller pipe is created.
• Tested both normal and elevated Codex processes.
• Checked Microsoft Defender, AppLocker, and Code Integrity logs; no corresponding block or quarantine event was found.

The issue began immediately after the automatic Codex update, so this appears to be a regression or a version mismatch between Codex 26.730.8199.0 and the Computer Use runtime 26.730.61639.