[BUG] Dispatch — "Session couldn't be created" persists after reinstall, WSL2 update, Docker closed, VM Platform + virtualization confirmed enabled

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Claude Cowork's Dispatch feature fails to start a session on Windows. Clicking Dispatch immediately shows "Session couldn't be created" with a Retry button, no error code or further detail anywhere in the UI.

What Should Happen?

Dispatch should successfully spin up a session, as it does for Mac/other users.

Error Messages/Logs

Environment: Windows 11 (build 10.0.26200.9457), Claude Desktop v2.110.0, AMD Ryzen 7 5700U, 15.4GB RAM

Troubleshooting already completed, none resolved it:
- Confirmed CPU virtualization enabled (Task Manager) and Virtual Machine Platform enabled in Windows Features
- Ran `wsl --update` -> updated to 2.7.14, rebooted
- Fully quit Docker Desktop (also uses WSL2) before retrying
- Confirmed cowork-svc.exe process is running in Task Manager
- Fully reinstalled Claude Desktop (latest installer from claude.ai/download)
- Windows fully updated, including the KB5129195 fix for the unrelated Sept 8 Cowork file-access bug

No error code or details are exposed anywhere in the Dispatch UI - just "Session couldn't be created" and a Retry button.

Steps to Reproduce

1. Open Claude Desktop on Windows. 2. Click Dispatch in the sidebar. 3. Error 'Session couldn't be created' appears immediately with a Retry button

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

This was working through September 14, 2026, and broke on September 15 — the same day Claude Desktop updated to v2.110.0. Strongly suspect this update caused the regression rather than anything environmental on this machine.

Claude Code Version

N/A

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

I cleared my entire dispatch session because it wasn't working, it was a large session over months of chats.