Windows · 10 min · Upstream checked July 17, 2026

Troubleshoot a Codex theme on Windows

Diagnose PowerShell execution, Store-package discovery, port ownership, config encoding, and verification failures.

Platform behavior can change. Compare this guide with the original repository at commit 26c6c410e0e0.
01Restore and confirm stock Codex
02Run the documented tests
03Check package and port identity
04Reinstall, launch, and verify

Start with the exact PowerShell failure

Copy the script name, exit code, and first meaningful error without publishing private paths or account data. Confirm Node.js 22+ and the official Store-installed Codex package. Do not bypass an execution error by taking ownership of WindowsApps or replacing the official executable.

Check state and identity before deleting anything

An explicitly occupied debug port should fail closed; the normal launcher can scan for a free port. Verify that recorded PIDs, executable paths, package identity, Browser ID, and start times still describe the current session. Config changes must preserve strict UTF-8 and stop if the file changed after reading.

Repair through the documented lifecycle

Run the upstream tests, reinstall once, launch, and use verify-dream-skin.ps1 with an absolute screenshot path. Inspect Home and a normal Task. If any native element is missing or unclickable, restore rather than calling the visual result complete.

Do not use -ExecutionPolicy Bypass as permission to run an unknown script. It is only acceptable for the reviewed original file you intentionally selected.

Completion checklist

Related guides