›_ Codex Issues
Codex Issues / #25411

Windows 10 Computer Use screenshot fails: SetIsBorderRequired failed (0x80004002)

Resolved 💬 5 comments Opened May 31, 2026 by ShawnXanz Closed May 31, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

On Windows 10 Pro 22H2, Codex Desktop Computer Use can connect to the Windows Computer Use helper and perform non-screenshot operations such as listing windows/apps, reading accessibility text, activating a window, and sending keyboard input. However, any Computer Use path that requests a screenshot fails with:

SetIsBorderRequired failed: 不支持此接口 (0x80004002)

This appears to be a Windows 10 compatibility issue: the helper calls GraphicsCaptureSession.IsBorderRequired / SetIsBorderRequired, but this API is documented as introduced in 10.0.20348.0, while current Windows 10 client 22H2 is build 19045.

Environment

  • Codex Desktop install source: Microsoft Store
  • Codex Desktop version: 26.527.3686.0
  • Computer Use plugin/cache version observed: 26.527.31326
  • OS: Windows 10 Pro 22H2
  • OS build: 19045.6466
  • Get-ComputerInfo: WindowsProductName=Windows 10 Pro, OsBuildNumber=19045
  • HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion: DisplayVersion=22H2, CurrentBuild=19045, UBR=6466

What works

After connecting to the existing Computer Use named pipe, the following operations work:

  • sky.list_apps() succeeds and returns applications.
  • sky.list_windows() succeeds and returns active windows.
  • sky.get_window_state({ include_screenshot: false, include_text: true }) succeeds for at least Microsoft Paint and returns an accessibility tree.
  • sky.activate_window(...) succeeds.
  • sky.press_key(...) succeeds.

Example window enumeration included a Weixin/WeChat window:

{
  "app": "process:K:\\Applications\\Weixin\\Weixin.exe",
  "id": 854470,
  "title": "微信"
}

What fails

Requesting a screenshot through Computer Use fails. Example call:

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

Observed error:

SetIsBorderRequired failed: 不支持此接口 (0x80004002)

This blocks Computer Use screenshot-based workflows and coordinate input that depends on a fresh screenshot. Accessibility-only reads still work when the app exposes useful UIA text, but apps such as Weixin/WeChat expose only a render container (MMUIRenderSubWindow), so screenshot support is required for practical use.

Expected behavior

On Windows 10 build 19045, Computer Use should either:

  1. avoid calling SetIsBorderRequired / IsBorderRequired when that interface is unavailable, and continue capture with the default capture border behavior; or
  2. clearly report that screenshot capture requires a newer Windows build, while keeping non-screenshot Computer Use operations available.

Actual behavior

Computer Use screenshot capture fails with SetIsBorderRequired failed: 不支持此接口 (0x80004002), even though the helper pipe and non-screenshot operations are otherwise usable.

Suspected cause

Microsoft documents GraphicsCaptureSession.IsBorderRequired as introduced in device family version 10.0.20348.0 / UniversalApiContract v12. Windows 10 Pro 22H2 client is currently build 19045, so calling this property appears to return E_NOINTERFACE (0x80004002).

The helper likely needs a runtime API/contract check and fallback path that skips SetIsBorderRequired on older Windows 10 client builds.

Related issues

These look related to Windows Computer Use helper/native-pipe availability, but this issue is specifically about the second-stage screenshot failure after the helper is reachable:

  • #25220
  • #25301
  • #25216
  • #25194

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 2 months ago

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

  • #25178

Powered by Codex Action

ShawnXanz · 2 months ago

I reviewed the suggested duplicate (#25178). It appears to cover the same underlying Windows 10 Computer Use screenshot failure: SetIsBorderRequired failed: 不支持此接口 (0x80004002) on Windows 10 22H2 / build 19045. This issue is likely a duplicate of #25178.

The extra detail in this issue is that non-screenshot Computer Use operations can still work (window/app enumeration, accessibility-only state, activation, keyboard input), while screenshot capture fails at the Windows Graphics Capture SetIsBorderRequired call.

zengfanfan · 1 month ago

anyone fix this ???

info2sunv-commits · 25 days ago

This still reproduces with a newer Codex Desktop version:

  • Codex Desktop (Microsoft Store): 26.727.6591.0
  • Computer Use plugin: 26.727.51351
  • OS: Windows 10 Pro 22H2, build 19045.6466

Errors:

  • Screenshot capture: SetIsBorderRequired failed: 不支持此接口 (0x80004002)
  • Element click: coordinate input geometry is unavailable

Working operations:

  • App/window enumeration
  • Accessibility-only window-state inspection
  • Window activation
  • Keyboard input / type_text

Failing operation:

  • click({element_index: ...}) consistently fails across multiple applications, including Notepad and Microsoft Sysinternals Autoruns.

I fully restarted Codex Desktop, reloaded the Computer Use plugin, and ran the Windows “Repair” action for the app. The problem remains. Microsoft Store currently offers no newer update.

This suggests that screenshot/coordinate geometry initialization is failing on Windows 10, while accessibility and keyboard operations remain functional. Could you point to the canonical issue and clarify whether a Windows 10 runtime guard or fallback is planned?

rusjrw · 25 days ago

Request: full Computer Use support for Windows 10

This issue is still reproducible on the current Codex Desktop release:

  • Codex Desktop: 26.721.11231.0 (Microsoft Store)
  • Computer Use plugin: 26.721.81911
  • Windows 10 Pro 22H2: 19045.6466

Screenshot capture fails even for standard Windows applications such as Notepad with:

SetIsBorderRequired failed: Interface not supported (0x80004002)

Accessibility-only operations still work, including:

  • listing applications and windows;
  • activating windows;
  • reading available UI Automation text;
  • keyboard input.

However, without screenshot capture, Computer Use cannot reliably:

  • understand visually rendered interfaces;
  • interact with controls that are not exposed through UI Automation;
  • use visual coordinates safely;
  • inspect graphs, canvases, animations, 3D views, or custom-rendered controls;
  • verify the visible result of an action.

Please add full Windows 10 support for Computer Use rather than leaving it in an accessibility-only degraded mode.

Expected behavior on Windows 10:

  1. Window and screen capture works reliably.
  2. Visual state can be retrieved and analyzed.
  3. Coordinate-based mouse interaction works using a fresh screenshot.
  4. Accessibility and visual interaction can be used together.
  5. Standard desktop applications and custom-rendered interfaces are supported.
  6. Unsupported newer Windows APIs are handled through compatible Windows 10 code paths without disabling screenshot-based Computer Use.
  7. Windows 10 compatibility is covered by release testing so the problem does not return in later updates.

The internal implementation is up to the Codex team, but the user-facing result should be a functional Computer Use experience on Windows 10, not only partial accessibility-tree control.