Windows Desktop: failed to resolve rollout path / Error submitting message on every new conversation

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

OS: Windows 10 Pro 22H2 (Build 19045.6466) Codex Desktop Installer (latest) Codex CLI 0.142.5 Also tested Microsoft Store version with the same result.

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 10 Pro 22H2 x64 Build 19045.6466

What issue are you seeing?

Every new conversation fails immediately.

Desktop launches normally, but every message returns:

• Error submitting message

Sometimes it also shows:

• Codex app-server is not available

and

failed to resolve rollout path

C:\Users\<username>\.codex\sessions\2026\07\02\rollout-xxxxxxxx.jsonl

file does not exist

The CLI works normally.

The issue only occurs in the Desktop application.

What steps can reproduce the bug?

1. Install Codex Desktop on Windows.
2. Launch the Desktop application.
3. Create a new conversation.
4. Type any message.
5. Click Send.

Every conversation fails immediately.

What is the expected behavior?

The Desktop app should create the rollout/session file and submit the message successfully.

Instead it immediately reports:

Error submitting message

and sometimes

failed to resolve rollout path

Additional information

Already verified:

• Reinstalled Desktop Installer
• Previously tested Microsoft Store version
• Same issue with both versions

• Codex CLI works normally
• Authentication works
• codex app launches Desktop successfully

Windows:

Windows 10 Pro 22H2
Build 19045.6466

Verified:

• .codex is writable
• I can manually create

C:\Users\<username>\.codex\sessions\2026\07\02

and create jsonl files.

Desktop never creates rollout-xxxxxxxx.jsonl automatically.

Desktop attempts to resolve a rollout file that does not exist.

CODEX_HOME is empty.

HOME is empty.

USERPROFILE is correctly set.

This appears to be specific to the Desktop app.

The Desktop app never creates the rollout jsonl file before trying to resolve it.

It appears the rollout/session initialization fails before the first message is submitted.