[Windows] Computer Use capture and elevated sandbox spawn fail in app 26.803.5235.0

Open 💬 3 comments Opened Aug 8, 2026 by TwistedAether

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

26.803.5235.0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

After the ChatGPT/Codex Windows app updated to version 26.803.5235.0, Windows Computer Use and ordinary elevated-sandbox process startup became partially unusable.

Computer Use can enumerate windows with list_windows(), but state collection fails. Before the clean reinstall, pixel capture consistently failed with:

IGraphicsCaptureItemInterop.CreateForMonitor failed: De opgegeven service is geen geïnstalleerde service. (0x80070424)

After a complete Microsoft Store uninstall/reinstall and a freshly rebuilt local runtime, get_window_state() with text or screenshot collection now consistently fails with:

Error: node_repl exec context not found

A separate ordinary sandboxed PowerShell command fails before execution with:

CreateProcessAsUserW failed: 5 (Toegang geweigerd / Access denied)

There is also a bundled skill/runtime API mismatch: the Computer Use skill requires await sky.documentation("guidance"), but the freshly loaded @oai/sky sky object has no documentation function.

What steps can reproduce the bug?

Feedback ID: 019fddec-7e4d-7c11-bd61-b957b2d554a5

What is the expected behavior?

The supported elevated Windows sandbox should be able to start an approved basic command without CreateProcessAsUserW failing. Computer Use should collect the approved window's accessibility text and screenshot, then allow normal UI interaction while preserving the sandbox boundary.

Additional information

Versions:

ChatGPT/Codex Windows app: 26.803.5235.0
Computer Use plugin: 26.803.41515
@oai/sky: 0.6.2
Platform: Microsoft Windows NT 10.0.26200.0 x64 (Windows 11 Pro build 26200.8973)

Troubleshooting already completed:

Computer Use permission reset and multiple app/Windows restarts.
In-app workspace bundle reset/reinstall.
Full Microsoft Store uninstall/reinstall.
Fresh local runtime rebuild without restoring old runtime data.
SFC /scannow (repaired a Windows issue), DISM RestoreHealth, and restart.
Windows CaptureService template and interactive-user instance verified.
Supported temporary unelevated fallback tested; helper startup failed with spawn EPERM, so elevated was restored.
sandbox_private_desktop = false was already active.

The Microsoft Edge ChatGPT extension can still capture and control browser tabs normally. No security boundary was disabled and no workaround requiring weakened sandbox permissions remains enabled.

The attached diagnostic package contains a redacted README, system information, version metadata, and the clean-reinstall result. It excludes credentials, tokens, browser data, router/network configuration, .sandbox-secrets, full logs, and the full config.toml.

Diagnostic ZIP SHA-256: 2CF3B73B936D29CAB99F8E94C74FB12F7A9FB9EF6EBFB0582F1472D98F062B3B

OpenAI-Computer-Use-diagnose-2026-08-09.zip

Because this reproducible product defect consumed substantial ChatGPT Plus/Codex usage during repeated failed runs, reinstalls, restarts, and diagnostic attempts, I also request that OpenAI audit the usage associated with Feedback ID 019fddec-7e4d-7c11-bd61-b957b2d554a5 and restore or credit all billable tokens attributable to this defect. I understand that cached input, regular input, output, and reasoning tokens may be accounted for differently; please calculate the appropriate credit from the server-side usage record rather than treating every token category as having the same rate. Please provide or associate a support case number and confirm any credit applied.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 19 days ago

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

#37509
#37281
#37592
#37201

Powered by Codex Action

FreeFallingSnow · 19 days ago

Confirmed on the same Windows build.

Environment:

Codex Desktop: 26.803.5235.0
Computer Use plugin: 26.803.41515
@oai/sky: 0.6.2

Observed:

Importing @oai/sky succeeds.
sky.list_windows() succeeds and returns 8 windows.
typeof sky.documentation is "undefined".
The bundled Computer Use SKILL.md requires:

await sky.documentation("guidance")

This confirms that the bundled skill instructions and runtime API are mismatched.

Temporary workaround:
I changed SKILL.md to read the bundled guidance.md, api.md, and confirmations.md files directly.

36362589 · 19 days ago

Additional reproduction on the same Windows/Codex build, with a distinct window-ownership failure.

Environment:

ChatGPT/Codex Desktop: 26.803.5235.0
Computer Use plugin: 26.803.41515
@oai/sky: 0.6.2
Windows 11 x64
sandbox_private_desktop = false (target apps visible on the active desktop)

Observed:

node_repl runs.
Importing @oai/sky succeeds.
sky.list_apps() and sky.list_windows() succeed and return Notepad and Blender.
nodeRepl.requestMeta is populated.
sky.documentation is still undefined, although the bundled skill requires it.
get_window_state() for Notepad fails with:

``Error: node_repl exec context not found``

Rehydrating the exact Blender window returned by discovery succeeds, but state capture then fails with:

``window id <id> no longer belongs to blender.4.5; current owner is blender.4.5``

The Blender message is self-contradictory: the expected and reported current owner identifiers are identical. This suggests a Windows helper window-owner validation/identity comparison defect in addition to the lost node_repl execution-context problem.

Integrity/recovery checks:

Plugin cache files hash-match the copies bundled with the installed Store package.
Full app/Windows restarts and plugin reinstall did not resolve the failures.
The Microsoft Store currently offers no newer build on this machine.
No security boundary was bypassed.

No project content, user paths, credentials, tokens, or session identifiers are included in this public comment.