611c10176a27.Quick answer
Restore first and confirm the official Store-installed Codex app works. For the ordinary path, repair with the current original v1.3.3 Setup.exe—no global Node.js or manual PowerShell—then verify the staged active theme, Home plus a normal Task, and keep graphical Restore available.
Identify the installation path before diagnosing it
The ordinary v1.3.3 Setup.exe bundles its runtime and does not require global Node.js or manual PowerShell. Ask for a script name, Node.js version, or PowerShell exit code only when the user deliberately installed from source. In either path, record the first meaningful error without publishing private paths or account data.
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 matching documented lifecycle
For the app path, run the current original Setup.exe over the installed version, launch from Start, and verify Home plus a normal Task. For a deliberate source install, use the matching source verifier. If any native element is missing or unclickable, restore rather than calling the visual result complete.
Completion checklist
- Install path is identified
- Store package is official
- Port identity is unambiguous
- Active theme, Home, Task, and Restore pass
Frequently asked questions
How do I fix Codex Dream Skin on Windows?
Confirm stock Codex works, identify whether you used the v1.3.3 Setup.exe or a source install, repair through that matching path, then verify the staged active theme, Home, a normal Task, native controls, and Restore.
What if port 9335 is already in use?
The normal upstream launcher scans for a free port. If you explicitly request an occupied port, the workflow should fail closed rather than attach to an ambiguous process.
Should I modify WindowsApps to repair the theme?
No. The reviewed workflow discovers the current Store package dynamically and is designed not to replace, take ownership of, or patch files in WindowsApps.