Computer Use screenshot capture fails on Windows 10 with SetIsBorderRequired failed

Summary

Codex Computer Use can list/target Windows apps and read some accessibility text, but screenshot capture fails for every tested desktop app on Windows 10. Because get_window_state({ include_screenshot: true }) fails, Computer Use cannot reliably click or operate apps visually.

Environment

• Codex app: OpenAI.Codex version 26.623.13972.0
• Computer Use plugin bundle: computer-use@openai-bundled version 26.623.101652
• Runtime path seen in config: C:\Users\pc\AppData\Local\OpenAI\Codex\runtimes\cua_node\1b23c930bdf84ed6
• OS: Windows 10 Pro 22H2
• Windows build: 19045.6466
• Architecture: 64-bit
• Locale: ko-KR

Reproduction

1. Start Codex Desktop on Windows 10.
2. Enable/install the bundled Computer Use plugin.
3. Ask Codex to use Computer Use with an open desktop app, for example Obsidian or Notepad.
4. In the Computer Use runtime, list apps and select a window successfully.
5. Call get_window_state({ window, include_screenshot: true, include_text: false }).

Expected behavior

Computer Use captures the target app window, returns a screenshot, and can proceed with visual mouse/keyboard automation.

Actual behavior

App discovery and window targeting work, but screenshot capture fails with:

SetIsBorderRequired failed: [Korean Windows message: interface not supported] (0x80004002)

The same failure was observed for:

• Obsidian 1.12.7
• Notepad

Accessibility-only capture can partially work:

await sky.get_window_state({ window: targetWindow, include_screenshot: false, include_text: true })

But screenshot capture fails:

await sky.get_window_state({ window: targetWindow, include_screenshot: true, include_text: false })

Notes

The error name suggests the Windows Graphics Capture code path may be calling GraphicsCaptureSession.IsBorderRequired / SetIsBorderRequired on a Windows 10 build where that property is unavailable or not usable. Codex docs say Windows 11 is recommended and Windows 10 support is best-effort, but the current behavior is a hard failure for screenshot capture rather than a graceful fallback.

Suggested fix

Before calling SetIsBorderRequired, check whether Windows.Graphics.Capture.GraphicsCaptureSession.IsBorderRequired is present/supported on the current OS/API contract. If it is not supported, skip setting that property and continue with ordinary bordered capture, or return a clearer actionable error.

Diagnostics already tried

• Restarted Codex Desktop.
• Computer Use plugin cache updated from an older bundle path to 26.623.101652.
• Reinitialized the Computer Use runtime.
• Tested multiple target apps.
• Confirmed app discovery still works.
• Confirmed screenshot capture fails independent of the target app.