Windows Computer Use Cannot Enumerate Any Application Windows
Open 💬 8 comments Opened Aug 6, 2026 by halvorsondonna53-alt
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
标题:Windows Computer Use 无法枚举任何应用窗口
Computer Use 无法控制任何 Windows 应用,包括记事本、微信、钉钉和网易云音乐。
稳定复现错误:
EnumWindows failed: 系统找不到指定的路径。 (0x80070003)
已经完成以下排查:
- ChatGPT Desktop 已是 Microsoft Store 提供的最新版
- 已执行覆盖修复安装
- 已卸载并重新安装 Computer Use 插件
- Computer Use Server 和 Skill 均已启用
- 已重建 cua_node 运行时缓存
- Windows 桌面处于活动、已解锁状态
- 重启 ChatGPT Desktop 后仍然复现
- sky.list_apps() 和 sky.list_windows() 均失败
系统:Windows,Asia/Shanghai
故障日期:2026-08-06
请协助检查 Windows Computer Use 运行时的 EnumWindows 路径解析或窗口枚举问题。
8 Comments
English translation:
Title: Windows Computer Use Cannot Enumerate Any Application Windows
Computer Use cannot control any Windows applications, including Notepad, WeChat, DingTalk, and NetEase Cloud Music.
Consistently reproducible error:
EnumWindows failed: The system cannot find the path specified. (0x80070003)
The following troubleshooting steps have already been completed:
System: Windows, Asia/Shanghai
Date of issue: 2026-08-06
Please help investigate the EnumWindows path resolution or window enumeration issue in the Windows Computer Use runtime.
<!-- codex-issue-translator -->
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I can provide a related same-build observation from another Windows task: attempting to open NetEase Cloud Music failed before any reliable desktop app interaction, and retries plus a Computer Use reset did not make
sky.list_apps()orsky.list_windows()usable. The error in that task wasspawn EPERM, not 0x80070003, so I am not claiming an identical failure mode; it may be an earlier-stage failure in the same Windows helper/enumeration path. Environment: Codex Desktop 26.730.8199.0, Computer Use plugin 26.730.61639, @oai/sky 0.6.2, Windows x64.我和你遇到的问题一摸一样,请问你解决了吗?
这个已经在 #37043 里定位得比较清楚了:不是某个文件夹没建,也不是重装能解决。helper 跑在
CodexSandboxOffline的 private desktop 里,EnumWindows看到的是隔离桌面,不是你正在用的桌面;外层又把残留的GetLastError包成了0x80070003。有人临时设了:
完全退出再启动后,
list_windows()能恢复,但截图接着会报0x80070424,而且关 private desktop 会削弱隔离,所以这只能用来验证根因,不算真正修好。BitFun 的 Windows Computer Use 这块正好可以给上游当个实现对照:桌面宿主直接
EnumWindows,先拿 hwnd/pid/title,再 best-effort 解析 exe;解析失败就回退窗口标题,不让一次路径失败把整个list_apps带崩。代码就这一小段:https://github.com/GCWing/BitFun/blob/e640aa402023792a5fd6568f445ece1a81013085/src/apps/desktop/src/computer_use/windows_list_apps.rs#L51-L75长期修法还是把窗口枚举和截图放到可信的交互桌面 broker,模型写的 shell 继续留在 private desktop。
I can reproduce the same Windows Computer Use failure on a newer build, and it is still present after a clean reinstall.
Environment
26.803.5235.026.803.4151526200.8875History / behavior
EnumWindows failed ... (0x80070003), matching this issue.EnumWindows failed / Access denied (0x80070005).Troubleshooting already performed
cua_noderuntime.The issue still reproduces with app
26.803.5235.0and Computer Use26.803.41515.The recent discussion about the Computer Use helper running on a private desktop looks consistent with what I observed: changing WinSta0/Default ACLs alone did not resolve enumeration. I have stopped making further Windows permission changes and can provide additional diagnostics if useful.
Confirming the same issue on a second Windows installation. This is fully reproducible and blocks all Computer Use functionality.
Environment:
26.803.5235.026.803.41515@oai/sky:0.6.225H2, build26200.8655, x64OpenAI.Codex_26.803.5235.0_x64__2p2nqsd0c76g0OkExact failures:
A fresh Node REPL followed by a direct launch attempt also fails:
Additional API mismatch:
sky.documentation("guidance" | "api" | "confirmations").skyobject has nodocumentationmethod.Recovery attempts already completed without improvement:
cua_noderuntime cache reset and regeneration attemptopenai-bundledmarketplace from the official MSIX package instead of the temporary.codex\.tmpsourcecomputer-use@openai-bundledis installed and enabledNot completed because the native helper fails first:
Please escalate this urgently to the Windows Computer Use/runtime owners. The public API instructions and shipped runtime are also out of sync, and the issue remains after all supported repair paths.
Same issue, feedback ID - 019fe2c0-f468-73b3-b3bf-bccf44f2d8af