Codex Desktop shows workspace dependency repair on Windows 10, but install fails because Windows 10 is unsupported

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

• #19570
• #19770
• #19415
• #18998
• #18861

Powered by Codex Action

Additional affected user report from Windows 10.

I also submitted in-app feedback and received this feedback/session ID:

019ddd99-d8c1-7ad2-a270-6eaa97d8e8ee

Environment:

• OS: Microsoft Windows 10 Home, version 10.0.19045, x64
• Codex app: Microsoft Store build
• winget list --name Codex: Codex, ID 9PLM9XGG6VKS, version 26.422.9565.0, source msstore
• Runtime log reports: app_version=26.422.71525, release=codex@26.422.71525, build_type=windows-store, app_arch=x64
• Electron: 41.2.0
• Embedded Node in Codex app: 24.14.0
• Bundled Codex binary: codex-cli 0.126.0-alpha.8
• Global Codex CLI: codex-cli 0.125.0
• System Node.js: v24.15.0
• npm: 11.7.0
• Python: 3.14.4
• Git: 2.54.0.windows.1
• VC++ runtime DLLs are present: VCRUNTIME140.dll, MSVCP140.dll, VCRUNTIME140_1.dll

Observed behavior:

• The Codex Desktop Settings/Configuration UI exposes Workspace Dependencies diagnostics and reinstall controls.
• Diagnostics reports bundled workspace runtime dependencies are not installed/configured.
• Reinstall fails with a generic user-facing error.
• Logs show both a feature-gating mismatch and a Windows 10 support error.

Relevant sanitized log excerpts:

2026-04-30T08:52:33.289Z info [electron-message-handler] Features enabled enabledFeatures="..., workspace_dependencies, ..."

2026-04-30T08:52:37.083Z error [electron-message-handler] Request failed conversationId=none durationMs=3750 error={"code":-32600,"message":"unsupported feature enablement `workspace_dependencies`: currently supported features are apps, memories, plugins, tool_search, tool_suggest, tool_call_mcp_elicitation"} method=experimentalFeature/enablement/set

2026-04-30T08:53:13.527Z info [install-primary-runtime] primary_runtime_dependencies_diagnose_finished bundleVersion=null installed=false problemCount=1

2026-04-30T08:55:41.712Z error [electron-message-handler] Primary runtime install failed before first turn errorMessage="Codex Workspace dependencies are not supported on Windows 10." errorName=Error errorStack="Error: Codex Workspace dependencies are not supported on Windows 10.\n    at async beforeFirstTurn (app://-/assets/index-BZIMtjdh.js:316:173729)\n    at async sm (app://-/assets/app-server-manager-signals-w7HK0qNP.js:83:15353)\n    at async ie (app://-/assets/app-server-manager-signals-w7HK0qNP.js:85:1817)"

2026-04-30T08:56:21.317Z info [electron-message-handler] Sending server response id=0 response={"contentItems":[{"type":"inputText","text":"No bundled workspace runtime dependencies are configured yet. Call install_workspace_dependencies() to install them."}],"success":false}

2026-04-30T09:10:45.683Z error [electron-message-handler] Failed to install workspace dependencies errorMessage="Codex Workspace dependencies are not supported on Windows 10." errorName=Error errorStack="Error: Codex Workspace dependencies are not supported on Windows 10.\n    at async _be (app://-/assets/index-BZIMtjdh.js:451:166113)" tool=install_workspace_dependencies

2026-04-30T09:10:45.683Z info [electron-message-handler] Sending server response id=1 response={"contentItems":[{"type":"inputText","text":"Failed to install workspace dependency runtime."}],"success":false}

This appears to be a feature/UI gating bug: the app exposes the workspace dependency repair path on Windows 10 even though the runtime reports this feature as unsupported on Windows 10.

我通过管理员权限运行解决了依赖安装不了的问题

我通过管理员权限运行解决了依赖安装不了的问题

不知道咱是不是一个问题，我试了没用。这个帖子是我让GPT自己写的

<img width="1180" height="1219" alt="Image" src="https://github.com/user-attachments/assets/3ff57be8-1779-4c22-8e01-37fb3e1ab0d6" />

Possible Windows fix: enable Developer Mode for runtime extraction failures

I ran into a similar Codex Desktop runtime installation failure on Windows.

The logs showed repeated primary runtime install failures like:

[primary-runtime-installer] Error installing primary runtime
Failed to extract primary runtime archive:
codex-primary-runtime/dependencies/node/node_modules/.pnpm/@napi-rs+canvas@0.1.100/node_modules/@napi-rs/canvas-win32-x64-msvc:
Can't create ... Invalid argument

[install-primary-runtime] primary_runtime_dependencies_diagnose_finished
bundleVersion=null installed=false problemCount=1

win10系统怎么解决？

<img width="1565" height="999" alt="Image" src="https://github.com/user-attachments/assets/9ace6e6c-d2e9-4c1d-b30d-2ec3f4ad0dc7" />

english man @Rvanshy do you enable developer mode ?

最后解决了吗？我的也是不能用

<img width="1427" height="672" alt="Image" src="https://github.com/user-attachments/assets/54a6e29c-ca79-493b-9e04-79bab3671483" />

@pekxie 解决不了，就是专属于Windows的bug，我的Mac就没有这个问题🙂‍↔️

+1我也出现了这个情况，但是在CLI下就没问题

I found a partial workaround for those experiencing unavailability in the Workspace dependencies (or with an empty C:\Users\<user>\.cache\codex-runtimes\ folder).

Environment:

• Codex Desktop: 26.519.81530
• Appx package: 26.519.11010.0
• Windows reports:
• ProductName: Windows 10 Pro
• DisplayVersion: 25H2
• CurrentBuild: 26200
• WSL enabled, Codex running with WSL integration.

The Reinstall button under:

Settings > Configuration > Workspace Dependencies > Reset and install Workspace

still fails with:

Couldn't reinstall Codex dependencies

Running Codex as Administrator did not fix it.

However, I noticed that during Codex startup / reinstall attempt, Codex briefly creates a temporary folder like:

(I had to refresh the codex-runtimes folder (which was empty) several times to see this temporary folder when opening the Codex.)

C:\Users\<user>\.cache\codex-runtimes\codex-runtime-install-DFVxD9

The random suffix changes each time. After a few seconds, Codex deletes this folder.

Inside that temp folder there was a node-runtime.tar.xz. I manually extracted it before Codex deleted the temp folder. The extracted structure was:

node-runtime/
  codex-primary-runtime/
    dependencies/
    plugins/
    runtime.json

The runtime.json looked valid:

{
  "bundleFormatVersion": 2,
  "bundleVersion": "26.521.10419",
  "bundledPlugins": [
    "plugins/openai-primary-runtime"
  ],
  "bundledSkills": [],
  "nodeVersion": "v24.14.0",
  "pythonVersion": "3.12.13",
  "targetArch": "x64",
  "targetPlatform": "win32"
}

I then manually moved:

C:\Users\<user>\.cache\codex-runtimes\codex-runtime-install-DFVxD9\node-runtime\codex-primary-runtime

to the final path that Codex already had in config.toml:

C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime

After that, Codex was able to detect the workspace dependencies. The internal load_workspace_dependencies check returned:

Workspace dependencies are available
Bundle version: 26.521.10419
Node.js executable: C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime\dependencies\node\bin\node.exe
Python executable: C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime\dependencies\python\python.exe

So the runtime archive itself appears valid. The failure seems to happen after download/extraction, during the final install/promotion/validation step.

This is only a workaround. Pressing Reinstall again still fails, and I had to repeat the manual extraction/move process.

I found a partial workaround. Environment: - Codex Desktop: 26.519.81530 - Appx package: 26.519.11010.0 - Windows reports: - ProductName: Windows 10 Pro - DisplayVersion: 25H2 - CurrentBuild: 26200 - WSL enabled, Codex running with WSL integration. The Reinstall button under: ``text Settings > Configuration > Workspace Dependencies > Reset and install Workspace ` still fails with: `text Couldn't reinstall Codex dependencies ` Running Codex as Administrator did not fix it. However, I noticed that during Codex startup / reinstall attempt, Codex briefly creates a temporary folder like: (I had to refresh the codex-runtimes folder (which was empty) several times to see this temporary folder when opening the Codex.) `text C:\Users\<user>\.cache\codex-runtimes\codex-runtime-install-DFVxD9 ` The random suffix changes each time. After a few seconds, Codex deletes this folder. Inside that temp folder there was a node-runtime.tar.xz. I manually extracted it before Codex deleted the temp folder. The extracted structure was: `text node-runtime/ codex-primary-runtime/ dependencies/ plugins/ runtime.json ` The runtime.json looked valid: `json { "bundleFormatVersion": 2, "bundleVersion": "26.521.10419", "bundledPlugins": [ "plugins/openai-primary-runtime" ], "bundledSkills": [], "nodeVersion": "v24.14.0", "pythonVersion": "3.12.13", "targetArch": "x64", "targetPlatform": "win32" } ` I then manually moved: `text C:\Users\<user>\.cache\codex-runtimes\codex-runtime-install-DFVxD9\node-runtime\codex-primary-runtime ` to the final path that Codex already had in config.toml: `text C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime ` After that, Codex was able to detect the workspace dependencies. The internal load_workspace_dependencies check returned: `text Workspace dependencies are available Bundle version: 26.521.10419 Node.js executable: C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime\dependencies\node\bin\node.exe Python executable: C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime\dependencies\python\python.exe ` So the runtime archive itself appears valid. The failure seems to happen after download/extraction, during the final install/promotion/validation step. This is only a workaround. Pressing Reinstall` again still fails, and I had to repeat the manual extraction/move process.

oops！There will be no content related to "codex" in my .cache folder.

@qykj0580 Did you try updating the C:\Users\<user>\.cache folder while opening the Codex?

You can also check if your global config.toml file contains the runtime path, as in the example below:

C:\Users\<user>\.codex\config.toml:

[marketplaces.openai-primary-runtime]
last_updated = "2026-04-25T14:13:07Z"
source_type = "local"
source = '\\?\C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime\plugins\openai-primary-runtime'

@qykj0580 Did you try updating the C:\Users\<user>\.cache folder while opening the Codex? You can also check if your global config.toml file contains the runtime path, as in the example below: C:\Users\<user>\.codex\config.toml: ``toml [marketplaces.openai-primary-runtime] last_updated = "2026-04-25T14:13:07Z" source_type = "local" source = '\\?\C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime\plugins\openai-primary-runtime' ``

There are no codex-related files in the C:\Users\<user>\.cache directory, whether during startup or restart. I also noticed that there is no content related to codex-runtimes in the config.toml file.

> @qykj0580 Did you try updating the C:\Users\<user>\.cache folder while opening the Codex? > You can also check if your global config.toml file contains the runtime path, as in the example below: > C:\Users\<user>\.codex\config.toml: > [marketplaces.openai-primary-runtime] > last_updated = "2026-04-25T14:13:07Z" > source_type = "local" > source = '\\?\C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime\plugins\openai-primary-runtime' There are no codex-related files in the C:\Users<user>.cache directory, whether during startup or restart. I also noticed that there is no content related to codex-runtimes in the config.toml file.

I wouldn't know what might be happening in your case. But a tip I can give you is to use the AI ​​in the Codex itself (preferably GPT-5.5 High), explaining what's going wrong and asking it to try to analyze the root cause of the problem. You can mention this issue here so it can have some guidance in case your problem is related (https://github.com/openai/codex/issues/19811), and I strongly recommend using the Systematic Debugging skill from the Superpowers plugin, which is already in the Codex Desktop App plugin list.

Same issue here Win 10 Pro (Developer mode enabled)

Seems that you can also just download it and extract it to the right place, you just need the specific version string

$version = "26.521.10419"
$url = "https://persistent.oaistatic.com/codex-primary-runtime/$version/codex-primary-runtime-win32-x64-$version.tar.xz"

so:
https://persistent.oaistatic.com/codex-primary-runtime/26.521.10419/codex-primary-runtime-win32-x64-26.521.10419.tar.xz

you can find which version is latest in these logs e.g.:
C:\Users\<user>\AppData\Local\Codex\Logs\2026\05\29\codex-desktop-c631c926-1bd7-4ae5-b640-7c33515b3641-37948-t0-i1-214452-0.log
you might find "latest bundleVersion = 26.521.10419"

While I already tried having codex figure it out some time ago, but eventually it just kept pointing to app issue and doing /feedback (I sent one detailed) (I could have also tried harder)
Meanwhile vscode extension worked perfectly in Windows/WSL
What lucassena mentioned is very helpful
I pointed codex at it and it gave me powershell script to download it and put it in right place
And voila
<img width="1080" height="483" alt="Image" src="https://github.com/user-attachments/assets/1ecbaa75-e5da-4300-8ccd-66d7252892df" />

Thanks a lot lucassena
---------
---------
<details>
<summary>Full guide: Windows 10 manual Codex runtime workaround</summary>

I got the manual runtime workaround working on Windows 10 by installing the Codex primary runtime manually.

Environment:

• Windows 10 Pro 10.0.19045.7184
• Codex Desktop from Microsoft Store
• App package observed in logs: OpenAI.Codex_26.527.3378.0
• Codex app-server in WSL was launching fine
• Developer Mode was already enabled
• Reinstall still failed with Couldn't reinstall Codex dependencies

What This Does

Codex expects the workspace dependency runtime at:

C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime

This workaround puts the official codex-primary-runtime folder there manually, then points Codex to its bundled marketplace from config.toml.

You can create that runtime folder either manually with a browser + 7-Zip, or by running the PowerShell script below. Do one of those two install methods, then always continue to the config section afterward.

Requirements

Install 7-Zip first, if you dont have it:

winget install 7zip.7zip

Or use any unzip you want for the non-powershell method (A).

Close Codex Desktop before doing either install method.

Option A: Manual Download And Extract

Download this archive in a browser:

https://persistent.oaistatic.com/codex-primary-runtime/26.521.10419/codex-primary-runtime-win32-x64-26.521.10419.tar.xz

Create this folder:

C:\Users\<user>\.cache\codex-runtimes

Extract the archive twice with 7-Zip:

.tar.xz -> .tar
.tar -> extracted folders

Find the extracted codex-primary-runtime folder and move it to:

C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime

Verify this file exists:

C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime\runtime.json

Then continue to Config Step below.

Option B: PowerShell Script

$ErrorActionPreference = "Stop"

$version = "26.521.10419"
$url = "https://persistent.oaistatic.com/codex-primary-runtime/$version/codex-primary-runtime-win32-x64-$version.tar.xz"

$cache = Join-Path $env:USERPROFILE ".cache\codex-runtimes"
$archive = Join-Path $cache "codex-primary-runtime-win32-x64-$version.tar.xz"
$tmp = Join-Path $cache "manual-install-$version"
$extract = Join-Path $tmp "extracted"
$final = Join-Path $cache "codex-primary-runtime"

$sevenZip = @(
  "$env:ProgramFiles\7-Zip\7z.exe",
  "${env:ProgramFiles(x86)}\7-Zip\7z.exe"
) | Where-Object { Test-Path $_ } | Select-Object -First 1

if (-not $sevenZip) {
  throw "7-Zip not found. Install it first with: winget install 7zip.7zip"
}

New-Item -ItemType Directory -Force $cache | Out-Null

Invoke-WebRequest $url -OutFile $archive

if (Test-Path $tmp) {
  Remove-Item -Recurse -Force $tmp
}

New-Item -ItemType Directory -Force $tmp | Out-Null
New-Item -ItemType Directory -Force $extract | Out-Null

& $sevenZip x $archive "-o$tmp" -y

$tarFile = Get-ChildItem $tmp -Filter "*.tar" | Select-Object -First 1
if (-not $tarFile) {
  throw "Could not find .tar after extracting .xz"
}

& $sevenZip x $tarFile.FullName "-o$extract" -y

$runtimeJson = Get-ChildItem $extract -Recurse -Filter runtime.json |
  Where-Object { $_.FullName -like "*codex-primary-runtime*runtime.json" } |
  Select-Object -First 1

if (-not $runtimeJson) {
  throw "Could not find runtime.json after extraction"
}

$runtimeDir = $runtimeJson.Directory.FullName

if ((Split-Path $runtimeDir -Leaf) -ne "codex-primary-runtime") {
  throw "Unexpected runtime directory: $runtimeDir"
}

if (Test-Path $final) {
  Rename-Item $final "codex-primary-runtime.backup-$(Get-Date -Format yyyyMMdd-HHmmss)"
}

Move-Item $runtimeDir $final

Write-Host "Installed runtime to: $final"

Then continue to Config Step below.

Config Step

Edit:

C:\Users\<user>\.codex\config.toml

Make sure workspace dependencies are enabled:

[features]
workspace_dependencies = true

Add this block, replacing <user> with the real Windows username:

[marketplaces.openai-primary-runtime]
last_updated = "2026-05-29T00:00:00Z"
source_type = "local"
source = '\\?\C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime\plugins\openai-primary-runtime'

Restart Codex Desktop.

After this, Codex detected the workspace dependency runtime correctly.

Important Notes

• This is only a workaround.
• Pressing Reinstall again may still fail and may require repeating the workaround.
• App updates may also require repeating it.
• This does not fix the underlying Windows 10 installer/support issue; it only manually puts the runtime where Codex expects it.

</details>

EDIT: now updated to "26.601.10930"...be sure to check the logs to find the latest bundle version as described on top of the post

我通过管理员权限运行解决了依赖安装不了的问题

怎么解决的

I’m seeing the same issue on Windows 10 Pro 10.0.19045 with Codex Desktop 26.608.1337.0.

Settings > Configuration > Workspace dependencies still cannot install/repair dependencies.

Relevant log:

Primary runtime install failed before first turn
Codex Workspace dependencies are not supported on Windows 10.

Earlier in the same troubleshooting session, I also had bundled executable relocation failures because:

C:\Users\<user>\AppData\Local\OpenAI\Codex

was a Junction pointing to a missing MSIX LocalCache target:

C:\Users\<user>\AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Local\OpenAI\Codex

After recreating the target directories and restarting Codex, bundled runtime files now extract correctly:

codex.exe: OK
rg.exe: OK
node.exe: OK
node_repl.exe: OK

The app log now reports the runtime paths as valid, for example:

nodeReplPath=...\runtimes\cua_node\2f053e67fec2d258\bin\node_repl.exe
nodeVersionStatus=ok
nodeVersionValue=v24.14.0

But workspace dependency install still fails with the Windows 10 unsupported message.

So this now appears to be a product support/UI issue rather than a local runtime extraction issue: the Settings UI exposes Diagnose/Reinstall on Windows 10 even though the runtime says workspace_dependencies are unsupported.

好像是win10自带解压器的问题，可以让codex自己修复

<img width="835" height="367" alt="Image" src="https://github.com/user-attachments/assets/830eb3e4-37fc-4aae-a662-cc58d2ed795d" />