[BUG] indows 11 Pro: Cowork, Connectors, and Claude Code all broken after latest auto-update — ERR_CONNECTION_RESET + OAuthError

Status Closed — not planned
Maintainer reply None cached
Activity 15 comments · opened Apr 12, 2026 · closed Jul 3, 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?

What's Wrong?
After the latest Claude Desktop auto-update, all three premium features stopped working simultaneously on Windows 11 Pro. Only basic Chat still functions.
Error 1 — Cowork:
Failed to start Claude's workspace
Request error: net::ERR_CONNECTION_RESET
Sometimes alternates with net::ERR_CONNECTION_ABORTED.
Error 2 — Connectors:
Could not load connectors directory
Could not attach to MCP server Kapture Browser Automation
Error 3 — Claude Code (in Desktop):
Error invoking remote method '$eipc_message$_45a8c035-be9c-4c52-b315-81a10e384931_$_claude.web_$_LocalSessions_$_start':
OAuthError: Unable to start session. Check your internet connection and try again.
Important context: Everything was working perfectly before the last auto-update. The update broke all three features simultaneously.
Environment

OS: Windows 11 Pro (latest)
Claude Desktop: Latest version (auto-updated)
Plan: Max ($100/month)
Internet: Working perfectly — Chat mode works fine
Antivirus: Kaspersky (tested with it completely disabled — same errors)
No VPN active

Everything I've tried (all failed):

Restarting Claude Desktop multiple times
Reinstalling workspace from in-app prompt
Full uninstall + reinstall of Claude Desktop (got 0x80073CF6 AddPackage failed during reinstall due to residual packages)
Restarting PC and router
Enabling Hyper-V (vmms service now running)
Manually starting CoworkVMService via PowerShell (service shows as Running)
Manually creating WinNAT rule: New-NetNat -Name "cowork-vm-nat" -InternalIPInterfaceAddressPrefix "172.16.0.0/24" (created successfully, Active: True)
Disabling Kaspersky antivirus entirely
Cleaning residual files from %APPDATA%\Claude, %LOCALAPPDATA%\Claude
Deleting CoworkVMService from registry and reinstalling

Diagnostic output:
powershellPS> Get-Service vmms
Status: Running

PS> Get-Service CoworkVMService
Status: Running

PS> hcsdiag list
(empty — no VM running)

PS> Get-HnsNetwork | Format-List Name, Id, Subnets
Name: Default Switch only (no cowork-vm-nat network)
Logs show repeated TypeError: Failed to fetch against assets-proxy.anthropic.com and api.anthropic.com, plus [MCP Registry] fetch failed with diagnostics.
Impact: 3+ working days of lost productivity. I run a digital marketing agency and rely on Cowork and Claude Code daily. I am paying $100/month for what is currently a $20 Chat-only experience.
Expected behavior: Cowork workspace starts, Connectors load, Claude Code authenticates — as they did before the update.
Related issues: #24918, #25136, #27801, #42591, #27010

What Should Happen?

Cowork workspace should start successfully, Connectors Directory should load, and Claude Code should authenticate — as they all did before the latest auto-update.

Error Messages/Logs

Error 1 — Cowork:
Failed to start Claude's workspace
Request error: net::ERR_CONNECTION_RESET
Sometimes alternates with net::ERR_CONNECTION_ABORTED.
Error 2 — Connectors:
Could not load connectors directory
Could not attach to MCP server Kapture Browser Automation
Error 3 — Claude Code (in Desktop):
Error invoking remote method '$eipc_message$_45a8c035-be9c-4c52-b315-81a10e384931_$_claude.web_$_LocalSessions_$_start':
OAuthError: Unable to start session. Check your internet connection and try again.

Steps to Reproduce

  1. Have a working Claude Desktop installation on Windows 11 Pro with Cowork, Connectors, and Claude Code all functioning normally
  2. Receive the latest Claude Desktop auto-update
  3. Open Claude Desktop → switch to Cowork tab
  4. Observe: "Failed to start Claude's workspace — Request error: net::ERR_CONNECTION_RESET"
  5. Observe: "Could not load connectors directory" banner
  6. Open Claude Code in Desktop → Observe: "OAuthError: Unable to start session"
  7. Regular Chat mode works perfectly — only premium features are broken

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

N/A — using Claude Code through Desktop app, CLI not installed

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

15 Comments

github-actions[bot] · 4 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/46818
  2. https://github.com/anthropics/claude-code/issues/46123
  3. https://github.com/anthropics/claude-code/issues/39225

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

lionglan624-blip · 4 months ago

Same repro on Windows 11 + latest Claude Desktop auto-update.

  • Connector: custom remote MCP server (OAuth 2.1 + PKCE, stateless HMAC tokens, deployed as a Cloudflare Worker).
  • UI error: "Couldn't reach the MCP server" — reference ofid_6520722aaff2b914.
  • Console: TypeError: Failed to fetch originating from assets-proxy.anthropic.com/claude-ai/v2/... (same asset-proxy fetch failure you listed), plus the unrelated No handler registered for ...BuddyBleTransport_$_reportState noise.

Server is confirmed healthy and reachable:

  • Direct curl against /health, /.well-known/oauth-protected-resource, and POST /mcp return 200 / 200 / 401 (expected OAuth challenge) from the same machine that's running the broken Claude Desktop.
  • wrangler tail on the Worker sees zero requests from Claude Desktop during reconnect attempts, while the same wrangler tail does see a manual curl from the same machine.

So the request never reaches Cloudflare's edge — the failure is in the Desktop → Anthropic backend hop before the MCP server is contacted at all. This matches the pattern reported in anthropics/claude-ai-mcp#143.

Only change on this machine between "working" yesterday evening and "broken" this morning: the Claude Desktop auto-update (and a concurrent Windows 11 cumulative update). Pre-existing HTTP proxy / AV / DNS setup did not change, and disabling the proxy made no difference.

DeeBeeJason · 4 months ago

(#47104) and ask Anthropic directly for the last known good installer URL. They host installers at predictable paths like https://storage.googleapis.com/osprey-downloads-c02f6a0d-347c-492b-a752-3e0651722e97/nsis-updater/Claude-Setup-x64.exe — but the versioned URLs aren't public.

jehielrb-ai · 4 months ago

Thanks @DeeBeeJason — that's a solid suggestion.

Confirming same regression on Windows 11 Pro, Max Plan (€89/month).
All three features broken after auto-update:

  • Cowork: ERR_CONNECTION_RESET
  • Connectors: "Could not load connectors directory"
  • Claude Code in Desktop: OAuthError

I've since installed Claude Code CLI (v2.1.110) which works
perfectly from the same machine — confirming this is 100% a
Desktop-specific issue.

I've emailed support@anthropic.com twice now with zero response.
I'll ask them for the last known good installer URL as well.

@anthropics — can you please:

  1. Provide the download URL for the last stable Windows installer

before this broken release?

  1. Give us an estimated timeline for the fix?
  2. Acknowledge this is a known regression?

5+ days of broken premium features on a $100/month plan with no
support response is not acceptable.

hesilvanove · 4 months ago

Using windows 11, was working normally, once i installed Version 1.3036.0 (cf521c), cowork stopped working... Commenting just to keep track if they give us any response.

ARHAEEM · 4 months ago

Hey i just did a workaround and it worked, hope it helps: https://github.com/anthropics/claude-code/issues/49917#issuecomment-4268321062

CoderJeffrey · 4 months ago

same issue please fix

ForestIsland9014 · 4 months ago

I'm experiencing the same issue. It works fine in other sessions, but only in the affected session do I get the error: "Error invoking remote method ‘$eipc_message$_4ab9ae55-583a-4867-90be-23b2daff8899_$_claude.web_$_LocalSessions_$_sendMessage’: OAuthError: Unable to start session. Check your internet connection and try again."
Could it be because I've hit the rate limit? I'm using additional usage, though...

Translated with DeepL.com (free version)

sdi-design · 3 months ago

Adding a macOS + Starlink data point — same triple-failure pattern, still occurring as of May 12, 2026.
Environment:

macOS, Mac Mini
Claude Desktop, latest auto-updated build
ISP: Starlink
Location: Australia
Paid plan

Errors (both fire together, every session):

"Server is busy. Retrying in 1s (attempt 3 of 10)" on any Cowork action
Popup: "Could not load connectors directory"

Duration: Multiple days, persistent.
Critical diagnostic: Works perfectly on iPhone cellular hotspot, fails on Starlink. Confirmed via curl -v that api.anthropic.com and assets-proxy.anthropic.com are reachable from Starlink (clean TLSv1.3 handshake, same resolved IP 160.79.104.10 as hotspot). Underlying network is fine — only the Claude desktop app fails. So this is an app-level interaction with something Starlink-specific, not endpoint reachability.
Already tried:

Cmd+Q + relaunch (many times)
Sign out / sign in
Cleared Cache, Code Cache, GPUCache, Session Storage, Local Storage
Latest desktop build confirmed
Cloudflare DNS on Mac and Starlink router
Starlink router reboot
macOS DNS cache flush
Disabled IPv6
Lowered MTU to 1420

Status page: Cowork shows Operational.
This isn't Windows-specific (original report was Win 11) — same symptoms on macOS. Suspect MTU/path-related interaction with Starlink's network stack for long-lived WebSocket/streaming connections, but standard MTU lowering didn't resolve it. Happy to provide network logs or request IDs.
cc @anthropics team

sdi-design · 3 months ago

Update: same errors now occurring on iPhone hotspot as well as Starlink, so the issue is not network-related. Cowork tool calls to the Chrome extension (tabs_context_mcp) fail with 'Server is busy' even with Chrome open and extension enabled.

AdamJordanAlex · 3 months ago

Another Windows 11 user blocked by this — 8 days and counting.

What's broken

Settings → Desktop app → General → Browser Use shows "No browsers connected" with the message "No Chrome instances are connected. Open Chrome with the Claude extension and sign in."

The Claude in Chrome extension is installed, enabled, and signed into the same Claude account as the desktop app. It works fine inside Chrome on its own. But Cowork can't see it. Clicking Recheck does nothing.

Screenshot attached.

Timeline

  • Tuesday, May 5, 2026 (daytime): Cowork's Chrome connector working normally.
  • Tuesday, May 5, 2026 (evening): Stopped connecting. Has not reconnected since.
  • May 13, 2026: Still broken. 8 days down.

Environment

  • Windows 11
  • Latest Claude Desktop (auto-updates on)
  • Latest Google Chrome
  • Paying customer

What I've tried (none worked)

  • 5 full uninstalls and reinstalls of Claude Desktop
  • Reinstalled the Claude in Chrome extension
  • Signed out and back into both the extension and the desktop app
  • Confirmed same account on both sides
  • Restarted Chrome
  • Quit Claude Desktop from the system tray and reopened
  • Toggled the Claude in Chrome connector off and on
  • Clicked Recheck repeatedly
  • Rebooted the computer

Support experience

Multiple tickets submitted at support.claude.com over the past 8 days. Every response has been from the AI agent saying it can't help and that a human will follow up. No human has followed up.

Ask

This looks like the same regression already reported in #58172 and #48806. Can someone from Anthropic confirm whether a fix is coming, share an ETA, or give a tested way to downgrade Claude Desktop to a working version? Paying users need a workaround in the meantime.

<img width="1920" height="1200" alt="Image" src="https://github.com/user-attachments/assets/73f200b2-96db-4dd1-b810-ccb3250c76ac" />

AdamJordanAlex · 3 months ago

"Cowork extension installs and authenticates successfully but Claude Desktop never detects browser (Chrome OR Edge, fresh Windows installs, 5+ retries) — appears to be Windows native messaging or VM-level failure, not browser-specific"

Michal-111 · 3 months ago

I have the same issue. I can't use Claude Code in Desktop or Powershell.
I get these messages:

In Desktop:
Something went wrong
Try sending your message again. If it keeps happening, share feedback so we can investigate.
OAuthError: Unable to start session. Check your internet connection and try again.

In PowerShell:
Unable to connect to Anthropic services
Failed to connect to api.anthropic.com: UNABLE_TO_VERIFY_LEAF_SIGNATURE
SSL certificate error (UNABLE_TO_VERIFY_LEAF_SIGNATURE). If you are behind a
corporate proxy or TLS-intercepting firewall, set NODE_EXTRA_CA_CERTS to your CA
bundle path, or ask IT to allowlist *.anthropic.com. Run /doctor for details.

madridtelecom · 3 months ago

Same regression on Windows 11, confirming with my data.

Environment

  • OS: Windows 11
  • Install type: MSIX (package: Claude_1.9659.2.0_x64__pzs8sxrjxfjjc)
  • Claude Desktop version: 1.9659.2.0
  • Plan: Max
  • Internet: fine — regular Chat works normally

Symptom
Claude Code in Desktop fails to start a session:
OAuthError: Unable to start session. Check your internet connection and try again.
Started this morning (~May 30, 2026) immediately after a Claude Desktop auto-update.
Only the OAuth/session features are affected; plain Chat works.

Logs (main.log)
[warn] [oauth] network error on fetch, flushing connection pool and retrying: net::ERR_CONNECTION_RESET
[error] oauth authorize network error: net::ERR_CONNECTION_RESET
[info] [oauth] failed to obtain oauth token (network_error): net::ERR_CONNECTION_RESET
[error] Cannot start session: oauth failed (network_error): net::ERR_CONNECTION_RESET
[error] Session initialization failed: Unable to start session. Check your internet connection and try again.

Notes

  • Regression: yes, worked before today's auto-update.
  • MSIX install, so rolling back to a previous version isn't feasible (no published prior package; Store serves only latest) — no user-side workaround.
  • Standalone Claude Code CLI (browser OAuth) is unaffected and works — issue is specific to the Desktop app's embedded OAuth.
github-actions[bot] · 1 month ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.