›_ Codex Issues
Codex Issues / #39216

Windows ARM64: Workspace Dependencies remain "Not installed", preventing custom pet creation and import

Open 💬 3 comments Opened Aug 18, 2026 by giuliarizzi-code
💡 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.715.10079.0 (Microsoft Store)

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 ARM64

What issue are you seeing?

Workspace Dependencies always remains "Not installed", even after a complete clean reinstall of the application.

This prevents local pet workflows that require the bundled Workspace runtime.

The issue is not limited to the hatch-pet skill.

It also affects:

  • creating new custom pets;
  • importing pets previously created in the web version;
  • continuing existing pet projects locally;
  • validating pet assets.

The application reports that the bundled workspace runtime is unavailable.

Example:

The bundled workspace Python/Pillow runtime is unavailable.

The workflow requires the bundled Python/Pillow runtime
and does not allow system Python as a substitute.

Another symptom is that only the cua_node runtime is installed, while the primary workspace runtime is never provisioned.

Workspace Dependencies always returns to:

Not installed

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a01576-5270-7832-bd18-a717a403b2a1

What is the expected behavior?

Workspace Dependencies should successfully install the bundled workspace runtime and display an installed runtime version.

After that, Codex should be able to:

  • create custom pets;
  • import pets created in the web version;
  • continue existing pet projects;
  • execute workflows that require the bundled workspace runtime.

Additional information

  1. Install Codex from the Microsoft Store on Windows 11 ARM64.
  2. Sign in.
  3. Open Settings → Configuration → Workspace Dependencies.
  4. Click Reinstall.
  5. Wait for the installation to finish.
  6. Workspace Dependencies immediately returns to "Not installed".
  7. Attempt to create a custom pet or import a pet created in the web version.
  8. The workflow stops because the bundled workspace runtime is unavailable.

I also tried:

  • completely uninstalling Codex;
  • deleting every OpenAI/Codex local folder;
  • deleting .codex;
  • deleting runtime caches;
  • reinstalling from Microsoft Store;
  • logging in again;
  • installing WSL;
  • rebooting;
  • running Codex as Administrator.

The behavior never changes.

Device architecture is ARM64.

The application installs the Computer Use runtime (cua_node) successfully, but never provisions the bundled workspace runtime required by these workflows.

The problem persists after:

  • clean uninstall;
  • deleting all local OpenAI/Codex data;
  • reinstalling from Microsoft Store;
  • installing WSL;
  • rebooting.

This appears to be a Workspace Dependencies provisioning issue rather than a problem with any individual pet skill.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 9 days ago

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

  • #38999
  • #37820

Powered by Codex Action

Rinferin · 6 days ago

I have the same issue. It keeps encountering a HTTP 404:

warning [install-primary-runtime] primary_runtime_update_poll_failed errorMessage="Failed to download primary runtime manifest (404 )." errorName=Error errorStack="Error: Failed to download primary runtime manifest (404 ).\n at xR (C:\\Program Files\\WindowsApps\\OpenAI.Codex_26.818.2872.0_arm64__2p2nqsd0c76g0\\app\\resources\\app.asar\\.vite\\build\\src-PzwkD6WC.js:650:11353)\n at async lR (C:\\Program Files\\WindowsApps\\OpenAI.Codex_26.818.2872.0_arm64__2p2nqsd0c76g0\\app\\resources\\app.asar\\.vite\\build\\src-PzwkD6WC.js:650:9311)\n at async Object.iR (C:\\Program Files\\WindowsApps\\OpenAI.Codex_26.818.2872.0_arm64__2p2nqsd0c76g0\\app\\resources\\app.asar\\.vite\\build\\src-PzwkD6WC.js:650:1741)\n at async mbe.pollIfDue (C:\\Program Files\\WindowsApps\\OpenAI.Codex_26.818.2872.0_arm64__2p2nqsd0c76g0\\app\\resources\\app.asar\\.vite\\build\\main-CY2oJTwH.js:1236:31791)"

nos1609 · 2 days ago

The Windows ARM64 primary-runtime failure is still present in the current Store package.

Environment:

  • Microsoft Store package: 26.818.8289.0
  • Desktop release: 26.818.61809
  • Windows 11 ARM64

The active Desktop process polls:

https://persistent.oaistatic.com/codex-primary-runtime/latest/win32-arm64/LATEST.json

approximately every 30 seconds. Every observed request returns HTTP 404 and produces:

primary_runtime_update_poll_failed
Failed to download primary runtime manifest (404 Not Found)

The Desktop app itself remains open, and generic connector tools such as GitHub MCP still work. However, primary-runtime-dependent workspace tools remain unavailable or can fail opaquely. This confirms that the missing ARM64 runtime manifest is still a current packaging/provisioning defect rather than a one-time installation failure.

Expected behavior: publish a valid ARM64 manifest, stop repeated polling after a definitive unsupported-platform response, and expose a clear user-facing dependency status.

Privacy: no local paths, account data, hostnames, repository names, or private logs are included.