Codex Desktop Windows: Workspace Dependencies remain "Not installed" and Diagnose fails even under minimal config

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

26.602.71036

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 10 Pro 10.0.19045

What issue are you seeing?

Codex Desktop on Windows cannot complete or recognize Workspace Dependencies.

In Settings > Configuration:

• Workspace Dependencies shows: Current version = Not installed
• Clicking Diagnose fails
• The exact error shown is: "Codex dependencies may need repair. Send /feedback if this keeps happening"

This still reproduces after a minimal-config isolation test, which substantially weakens custom config, plugin, MCP, project config, model, and reasoning-effort settings as the primary cause.

Additional evidence from local investigation:

• Global state indicated the Desktop runtime install was requested but not ready
• No visible Diagnose output file was produced
• Launching Codex as Administrator did not change the result

Current working hypothesis:
Desktop dependency/bootstrap failure or Desktop runtime defect.

What steps can reproduce the bug?

1. Open Codex Desktop on Windows 10 Pro.
2. Launch Codex normally or as Administrator.
3. Open Settings > Configuration.
4. Observe Workspace Dependencies shows "Current version: Not installed".
5. Click Diagnose.
6. Observe failure message: "Codex dependencies may need repair. Send /feedback if this keeps happening".

Additional reproduction/isolation notes:

• Prior reinstall attempts did not resolve the issue.
• Minimal user config + neutral project config were tested.
• Under minimal config, the same behavior persists.
• Feedback ID: 019ead07-4d42-7ec0-bcd1-4924423b77b3

What is the expected behavior?

Codex Desktop should successfully install or recognize Workspace Dependencies, show a valid current version, and Diagnose should produce usable diagnostic output or an actionable failure report instead of failing immediately.

Additional information

This issue persisted after minimal-config isolation, which weakens custom config and project-level interference as the primary cause. Local evidence suggested runtime install requested = true but runtime install ready = false. A local vendor evidence package was prepared in case maintainers request more details.