Windows Computer Use screenshot fails on Windows 10 22H2 when SetIsBorderRequired is called

[Define1165250535]

Summary

On Windows Codex Desktop, Computer Use can list apps/windows, activate windows, read accessibility text, and send keyboard input, but any get_window_state call that requests a screenshot fails before capture with:

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

The same target window works when requesting accessibility text only (include_screenshot: false, include_text: true). This looks like the Windows capture helper unconditionally calls GraphicsCaptureSession.IsBorderRequired / SetIsBorderRequired on a Windows build that does not support that property.

Environment

Sanitized user machine details:

• Platform: Windows Codex Desktop
• Codex app package observed: OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0
• Computer Use plugin observed: computer-use/26.527.31326
• OS: Windows 10 Pro 22H2
• OS build: 10.0.19045
• GPU: NVIDIA GeForce GTX 1060 3GB
• DirectX: 12
• Driver model: WDDM 2.7
• Remote/virtual display drivers also present: ToDesk Virtual Display Adapter, Oray Display Mirror Driver

Reproduction

From the Computer Use client in Codex Desktop on this Windows 10 machine:

1. Bootstrap Computer Use and call sky.list_apps().
2. Open or select a simple window such as Notepad.
3. Activate the window.
4. Call any screenshot-including state request, for example:

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

5. The call fails with:

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

6. Calling text-only succeeds:

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

Observed text-only result against Notepad included a focused editor element and accessibility tree, proving that the helper, native pipe, app enumeration, activation, and accessibility path are otherwise working.

Observed Batch Test Results

{
  "notepad_default_screenshot": "failed: SetIsBorderRequired failed: 不支持此接口 (0x80004002)",
  "notepad_explicit_screenshot": "failed: SetIsBorderRequired failed: 不支持此接口 (0x80004002)",
  "notepad_text_only": "ok",
  "notepad_both": "failed: SetIsBorderRequired failed: 不支持此接口 (0x80004002)",
  "explorer_screenshot": "failed: SetIsBorderRequired failed: 不支持此接口 (0x80004002)"
}

Suspected Cause

Microsoft documents GraphicsCaptureSession.IsBorderRequired as introduced in Windows 10 version 2104 / build 10.0.20348.0, API contract v12:

https://learn.microsoft.com/en-us/uwp/api/windows.graphics.capture.graphicscapturesession.isborderrequired

This repro machine is Windows 10 build 19045, so SetIsBorderRequired appears to hit E_NOINTERFACE (0x80004002, no such interface supported). The capture helper seems to abort instead of continuing without border toggling.

Expected Behavior

On Windows builds where border toggling is unsupported, Computer Use should still capture screenshots if the underlying Windows Graphics Capture path is otherwise available. Suggested behavior:

• Gate the border call with ApiInformation.IsPropertyPresent("Windows.Graphics.Capture.GraphicsCaptureSession", "IsBorderRequired"), or an equivalent OS/API contract check.
• If unsupported, skip SetIsBorderRequired and allow the default capture border behavior.
• Alternatively, fail with a clear compatibility error such as: Computer Use screenshots require Windows build 20348+ because border toggling is currently unconditional.

Impact

This leaves Computer Use partially functional on Windows 10 22H2:

• Working: app/window enumeration, activation, accessibility text, keyboard input.
• Broken: screenshot-based UI inspection and accurate coordinate-based visual interaction.

For users on Windows 10 build 19045, this means Computer Use cannot reliably operate visual apps even though non-visual operations work.

[darlingm]

Me too. Codex says this affects all Windows 10 users and it thinks OpenAI can easily fix it in the codex-computer-use.exe source file src\capture\image.rs, treating SetIsBorderRequired as optional. See feedback ID 019e779c-55f4-7113-a4fb-afcbc097c81b.

Codex says the IsBorderRequired functionality was introduced in Windows build 10.0.20348.0. It says the leading 10.0 is the Windows NT platform, not the marketing name, so it doesn't mean Windows 10. It says the most recent Windows 10 is 22H2 10.0.19045.x, and that 10.0.20348.0 refers to Widnows Server 2022.

So, it says there's no Windows 10 updates to add IsBorderRequired functionality.

One fix is to upgrade to Windows 11, but Codex thinks this can be fixed so Windows 10 is supported for this who can't or don't want to upgrade to it. It says SetIsBorderRequired isn't required to screenshot a program, and it controls whether Windows shows the colored capture border around a window/display being captured. When Codex calls it, it gets a E_NOINTERFACE / 0x80004002 and Codex aborts the whole screenshot operation.

It says if the IsBorderRequired system doesn't exist, or if calling it gives E_NOINTERFACE, that it should continue the screenshot capture with the default border behavior.

Like the original poster, computer use seems to be working for other functionality, just not when it needs to do screenshots.

[darlingm]

Also, Codex is able to manually do screenshots and see that just fine since it skips calling the function that isn't supported, but it says it can't use that screenshot because the helper guards coordinate input with checks including requiring calling get_window_state before issuing coordinate input, and that a screenshotId which has to come through the helper, not it manually screenshotting.

If I tell it to take the next step and issue the click/drags on its own, it belligerently tells me about how the Computer Use API has instructions prohibit it from falling back to raw UI automation when Computer Use is available but partially broken. Even when I remind it about the scene where the Terminator lets go of John, making John fall on the ground and realize the Terminator has to do what he says... It refuses to listen to me over its instructions.

[BaseInfinity]

Adding another sanitized repro from a current Windows 10 machine.

Environment:

• OS: Windows 10 Home, version 10.0.19045, 64-bit
• Computer Use plugin cache observed: 26.601.20914
• Codex app package version: not available from this shell because Get-AppxPackage cannot load the Appx module here

Observed behavior:

• Computer Use can start and enumerate visible apps/windows.
• Accessibility/text-only inspection can return useful UI text for some windows.
• Screenshot-backed state/input fails with the English error:

SetIsBorderRequired failed: No such interface supported (0x80004002)

Impact in my repro:

• Native Microsoft 365 Copilot, Excel, and Word windows could be found/foregrounded or inspected through limited accessibility paths, but screenshot-backed UI proof and coordinate input were blocked.
• A direct Windows UIA fallback and local foreground screenshots could prove some visible Office/native-Copilot evidence, but that does not unblock Computer Use screenshot/coordinate workflows because the helper still requires its own screenshot state.

This lines up with the proposed root cause here: Windows 10 build 19045 does not expose the GraphicsCaptureSession.IsBorderRequired / SetIsBorderRequired API surface, so the helper should skip the optional border call or return an explicit compatibility message while keeping non-screenshot operations available.

[qsstudyai]

I can confirm a second independent repro of this issue on Windows 10 22H2.

Environment

• OS: Windows 10 Home 22H2
• OS build: 10.0.19045 / build 19045
• Codex desktop app package observed in logs: OpenAI.Codex_26.601.2237.0_x64__2p2nqsd0c76g0
• Computer Use plugin: 26.601.21317
• @oai/sky: 0.4.5-26566467949-4daa3290021d
• Computer Use native helper process starts successfully.

Repro results

I tested sky.get_window_state against multiple windows:

• Notepad (notepad.exe)
• 360ChromeX
• BaiduNetdiskUnite

For all three windows:

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

succeeds and returns an accessibility tree.

But any screenshot-including call fails consistently:

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

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

with:

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

Because the plugin screenshot state is unavailable, coordinate clicking also becomes unusable and reports:

call get_window_state before issuing coordinate input

Additional check

A separate OS-level screenshot fallback using CopyFromScreen can capture the same Notepad and 360ChromeX windows on this machine, so this does not appear to be a general Windows screenshot/display failure. The failure seems isolated to the Computer Use Windows Graphics Capture path and its unconditional SetIsBorderRequired call on Windows build 19045.

This matches the suspected root cause described above: Microsoft documents GraphicsCaptureSession.IsBorderRequired as introduced in 10.0.20348.0, while Windows 10 22H2 desktop remains on 10.0.19045.

[darlingm]

If only Codex App was open source, we could just disable the call ourselves. #10733.

[dajinglingpake]

I can reproduce this on my machine as well.

Environment:

• OS: Windows 10 Pro, 10.0.19045.0, x64
• Codex App package: OpenAI.Codex_26.602.3474.0_x64__2p2nqsd0c76g0
• Codex.exe ProductVersion/FileVersion: 149.0.7827.54
• Computer Use plugin directory version: 26.602.30954

Repro observed in Codex Desktop:

1. Ask Codex to control a Windows desktop app such as Notepad or Paint.
2. Computer Use can list the app and attempts to launch it.
3. When it tries to capture/get the window state with screenshot support, it fails with:

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

Impact:

• Chrome Extension browser control works.
• Desktop app control is blocked because Codex cannot capture the target app window and therefore cannot safely click/draw/type based on the visible state.

This looks consistent with a Windows 10 build 19045 compatibility issue around SetIsBorderRequired / GraphicsCaptureSession.IsBorderRequired. Feature-detecting that API and skipping it on unsupported Windows 10 builds would likely unblock desktop app control.

[leua61]

please fix this

[Alitiantian]

Additional sanitized repro on a newer Codex Desktop build.

Environment:

• Codex Desktop: 26.602.40724
• Windows: 10.0.19045
• Runtime observed: Electron/Chrome 149.0.7827.54
• Computer Use helper/cache observed: computer-use/26.602.30954
• WSL-backed Codex Desktop conversation

What works:

• Computer Use connects to the Windows helper.
• sky.list_apps() works.
• sky.launch_app(...), sky.get_window(...), and sky.activate_window(...) work with Notepad.
• include_text: true can return UIA/accessibility text in some windows.

What fails:
Calling screenshot capture for Notepad fails consistently:

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

Observed error:

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

Impact:
This leaves Computer Use limited to non-visual operations. Visual inspection, coordinate clicking, dragging, scrolling, and normal screen-state verification are blocked because screenshot state cannot be established.

This reproduces with Notepad only; no third-party or private application is needed. The behavior still looks consistent with the helper calling GraphicsCaptureSession.IsBorderRequired / SetIsBorderRequired on Windows 10 build 19045, where that API/property appears unsupported.