›_ Codex Issues
Codex Issues / #26661

Computer Use unavailable on Windows Store Codex 26.602.4764.0

Open 💬 4 comments Opened Jun 5, 2026 by zren46877-lgtm
💡 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)?

Codex 26.602.4764.0

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 Pro, 64-bit

What issue are you seeing?

Summary

Computer Use is unavailable on Codex Desktop for Windows after updating to version 26.602.4764.0.

Environment

  • Codex Desktop (Windows Store version)
  • Version: 26.602.4764.0
  • Windows 11 x64

Problem

Computer Use cannot initialize.

Diagnostics reported:

  • bundled_executable_relocation_failed
  • reason=node-repl-missing

Computer Use native pipe appears to start, but desktop control functionality remains unavailable.

The following actions do not work:

  • get_window_state()
  • mouse click
  • keyboard input
  • screenshot capture

Investigation

I verified:

  • computer-use@openai-bundled is installed
  • plugin sync completes successfully
  • Codex Store package path:

C:\Program Files\WindowsApps\OpenAI.Codex_26.602.4764.0_x64__2p2nqsd0c76g0

I also noticed that node_repl.exe cannot be located after installation.

Expected behavior

Computer Use should initialize normally and expose desktop control APIs.

Actual behavior

Computer Use remains unavailable.

What steps can reproduce the bug?

  1. Install Codex Desktop from Microsoft Store.
  2. Update to version 26.602.4764.0.
  3. Enable / use Computer Use.
  4. Launch Codex Desktop.
  5. Computer Use fails to initialize.

Diagnostics report:

  • bundled_executable_relocation_failed
  • reason=node-repl-missing

Desktop control APIs become unavailable:

  • get_window_state()
  • screenshot capture
  • mouse click
  • keyboard input

What is the expected behavior?

Computer Use should initialize successfully and expose desktop control APIs.

Expected functionality:

  • get_window_state()
  • screenshot capture
  • mouse click
  • keyboard input

Computer Use should remain available after updating Codex Desktop.

Additional information

Computer Use remains unavailable.

Diagnostics report:

  • bundled_executable_relocation_failed
  • reason=node-repl-missing

The bundled computer-use plugin appears installed, but desktop control functionality cannot be used.This issue appeared after upgrading to Codex Desktop 26.602.4764.0 from Microsoft Store.

View original on GitHub ↗

4 Comments

zren46877-lgtm · 2 months ago

Additional information:

The issue started immediately after updating Codex Desktop to 26.602.4764.0 from Microsoft Store.

Previous diagnostics reported:

  • bundled_executable_relocation_failed
  • reason=node-repl-missing

I have already tried:

  • reinstalling Codex
  • repatching computer-use
  • restoring .codex configuration

The issue persists.

github-actions[bot] contributor · 2 months ago

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

  • #26011
  • #26501
  • #26587

Powered by Codex Action

dmk75perm · 2 months ago

I am seeing a related but different failure on Windows Store Codex 26.602.4764.0.

In my case node_repl.exe is present at:
C:\Users\<user>\AppData\Local\OpenAI\Codex\bin\34ab3e1324cc55b5\node_repl.exe

Official Computer Use path fails because the app-provided node_repl kernel exits with:
windows sandbox failed: spawn setup refresh

node_repl.exe is present and the Computer Use native pipe responds, so this is not simply node_repl-missing.

Potential workaround: node_repl.exe documents --disable-sandbox as “Start the Node kernel directly even when CODEX_CLI_PATH is set”, but the app-generated node_repl MCP config uses args: [], so users cannot test or apply that workaround through config.

zemeng5208 · 16 days ago

I maintain WinBridge Recovery, an independent Windows Codex Desktop local recovery/diagnostic tool: https://github.com/zemeng5208/winbridge-recovery

The original failure described here — bundled_executable_relocation_failed followed by reason=node-repl-missing, with node_repl.exe not available in the expected user runtime after a Store update — is directly in the local state layer WinBridge targets.

WinBridge v3.1.1 resolves the currently installed OpenAI.Codex AppX/package version, reads the bundled CUA manifest, verifies the official node.exe / node_repl.exe / Computer Use helper resources and then checks the user-side CUA runtime, NODE_REPL_NODE_PATH, CODEX_CLI_PATH, bundled marketplace and Computer Use cache together. If the current official source is present but the per-user runtime is missing, stale, or split across package versions, it can rebuild that user-owned state through verified staging, source/destination SHA-256 checks, backups and rollback.

The later sandbox failure mentioned by another commenter is a separate case: if node_repl.exe is present/current and the kernel instead exits at windows sandbox failed: spawn setup refresh, WinBridge should not treat that as a relocation repair. That is a sandbox/runtime failure and needs to remain an upstream product issue.

The project does not modify WindowsApps ownership/ACLs, decrypt or patch the Store package, or bypass sandbox/product policy.