Rank, 14 days: 46 on the Codex sheet
4 people reported
All time, since Nov 11, including 3 thumbs-up on GitHub.
WSL startup policy check fails
“Desktop startup policy read failed attempt=1 phase=policy-read reason=protocol retrying=false”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/28072/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Desktop app blocked at startup with WSL selected on Windows. Shows "Organization settings could not be loaded"; the startup policy check launches the non-executable WindowsApps binary instead of relocating the CLI.
Is this your bug?
File my report- Where
- Windows desktop app
- Error text
Desktop startup policy read failed attempt=1 phase=policy-read reason=protocol retrying=false- Platforms
- Windows
- How bad
- Stops work: a core feature can't be used.
Not quite your bug?
- Startup fails on policy read4 people
- WSL agent commands fail to spawn70 people
- Startup rename_staging EPERM5 people
Original reports1, newest first
- [Windows][WSL] Startup policy check skips CLI relocation and executes non-executable WindowsApps binaryOn GitHub#60974