Windows 10: Computer Use window capture times out while Appshots work

Finding: On Windows 10 (22H2 build 19045), Codex desktop Computer Use window screenshot capture via get_window_state with include_screenshot reportedly times out on visible, local windows, while window enumeration succeeds. It was reported on app/plugin 26.930.61225 and again on app 26.1007.21434. The cause is unconfirmed and no fix is identified. Reported symptom: The original reporter says Computer Use can enumerate windows and read accessibility text, but capture fails with a FrameArrived timeout and a window capture timeout, both ending 'timed out waiting on channel' (https://github.com/openai/codex/issues/51358). It reproduces in classic Notepad and CapCut. Appshots and normal Windows screenshots reportedly work. The window is visible on the active local desktop, the apps are not elevated, and no RDP, AnyDesk or VM is involved. The reporter says it persisted after app restarts, toggling Computer Use, a Windows reboot, a laptop-display-only test and a full reinstall. Newer report: A 2026-10-09 comment describes a reproduction on Windows 10 Enterprise 10.0.19045 with Codex app 26.1007.21434, which the commenter says the update checker reported as up to date (https://github.com/openai/codex/issues/51358#issuecomment-6086884743). Using the supported @oai/sky client, they launched a test app, listed windows, activated the window and called get_window_state with a screenshot. The first capture failed with the FrameArrived timeout. After refreshing window discovery and retrying once, it failed with the window capture timeout. Launching, enumeration and keyboard-based closing worked. The commenter says local shell and Node REPL worked, and that no ACL changes, process termination or runtime patching were performed. What is not established: Appshots were not tested in the newer run. The commenter says they cannot confirm the deadlock described in #35446 as their root cause, and the original reporter likewise says the same root cause is unconfirmed. The commenter separates this from an ACL/sharing-violation problem tracked elsewhere and addressed by PR #51822, so that PR should not be treated as a fix here. The only other reply is an automated duplicate-detection note listing possible duplicates (https://github.com/openai/codex/issues/51358#issuecomment-6016549663). No maintainer has diagnosed the issue or named a fixed build. Diagnosis and mitigation: None supported. The attempted steps (restart, reboot, reinstall, toggle Computer Use, single display, window refresh and re-activation) did not help in these reports. Limitation: This is an external-report summary only. KFA has not reproduced it, and the two reports may not be fully independent.