Claude Desktop - Unknown Error on startup after computer restart (Windows)
Status Fixed / completed
Maintainer reply None cached
Activity 4 comments · opened Jun 8, 2026 · closed Jun 9, 2026
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?
Issue: "Couldn't connect to Claude > Unknown Error" appears every time after restarting computer
Product: Claude Desktop app (version 1.11187.4.0)
OS: Windows with WSL enabled
Steps to reproduce:
a. Restart computer
b. Open Claude Desktop
c. Error appears immediately
Already tried:
Clear Cache and Restart
Reset App Data
Running as administrator
Disabled VPN
Implemented PowerShell fix from previous support session
Checked /etc/resolv.conf in WSL
What Should Happen?
Claude desktop should open
Error Messages/Logs
Steps to Reproduce
a. Restart computer
b. Open Claude Desktop
c. Error appears immediately
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
version 1.11187.4.0
Claude Code Version
version 1.11187.4.0
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
_No response_
4 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Issue resolved > AVG was the cause
Claude_AVG_WhiteScreen_FixPathway.docx
For anyone finding this issue because Claude Desktop on Windows shows "Couldn't connect to Claude" / "Unknown Error" after restart or update: I packaged a small unofficial launcher that may help in the narrower case where the browser can open Claude but the Desktop app cannot initialize/connect/render correctly.
Repo:
https://github.com/king-sheol/claude-desktop-windows-proxy-launcher
Latest release ZIP:
https://github.com/king-sheol/claude-desktop-windows-proxy-launcher/releases/latest
What it does: resolves the installed Claude path, launches Claude with explicit Chromium/Electron flags (
--disable-quicand GPU-stability flags), optionally injects the current Windows/env proxy, and checks for a visible Claude window after startup.Caveats: unofficial, not affiliated with Anthropic, does not modify or redistribute Anthropic software, and not a universal fix for WSL/Cowork VM/network issues.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.