Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude Desktop 1.3883.0 — repeated renderer crashes on Windows 11 x64 (BuddyBleTransport `No handler registered`) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52738•Fetched 2026-04-24 10:40:56
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
nBn4unBn4u
Participants
nBn4unBn4u
Timeline (top)
labeled ×3cross-referenced ×1

Error Message

[error] Uncaught (in promise) Error: Error invoking remote method '$eipc_message$<uuid>$claude.buddy$BuddyBleTransport$reportState': Error: No handler registered for '...BuddyBleTransport$_reportState'

Root Cause

The common root cause in all four: the renderer bundle calls an IPC method that the main process never registers → unhandled promise rejection → renderer process dies.

Fix Action

Fix / Workaround

Workaround (confirmed working)

Squirrel will silently auto-upgrade back to 1.3883.0 eventually, so this workaround is not permanent.

  1. Acknowledge the Windows platform scope of the BuddyBleTransport_$_reportState bug (either in this issue or by expanding #48281's labels to include platform:windows).
  2. Either register the missing IPC handler in main, or gate the renderer call-site behind a typeof handler === 'function' / feature-flag guard so a missing handler becomes a no-op instead of a crash.
  3. Document how to pin Claude Desktop to an older working version (disable Squirrel auto-upgrade for a specific installation) as a temporary mitigation for affected Windows users.

Code Example

[error] Uncaught (in promise) Error: Error invoking remote method
'$eipc_message$_<uuid>_$_claude.buddy_$_BuddyBleTransport_$_reportState':
Error: No handler registered for '...BuddyBleTransport_$_reportState'

---

2026-04-23 22:11:32
2026-04-24 00:43:56
2026-04-24 01:11:22
2026-04-24 09:23:09
2026-04-24 09:30:13

---

Get-Process -Name "claude" -ErrorAction SilentlyContinue | Stop-Process -Force
& "$env:LOCALAPPDATA\AnthropicClaude\app-1.3561.0\claude.exe"
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

What's Wrong?

Claude Desktop renderer crashes repeatedly on Windows 11 x64 with version 1.3883.0. Five crashes observed over twelve hours of active use, three of them within one single hour. Every crash correlates 1:1 with the same BuddyBleTransport_$_reportState IPC error as the existing macOS-reported issue #48281.

Filing this as a separate Windows-specific report per Anthropic Support's recommendation — #48281 is currently labeled platform:macos only, which hides Windows reports from anyone searching.

What Should Happen?

Claude Desktop should launch without the renderer taking down the UI every ~1–3 hours of use.

Error Messages/Logs

Recurring error in %APPDATA%\Claude\logs\claude.ai-web.log:

[error] Uncaught (in promise) Error: Error invoking remote method
'$eipc_message$_<uuid>_$_claude.buddy_$_BuddyBleTransport_$_reportState':
Error: No handler registered for '...BuddyBleTransport_$_reportState'

Crash timestamps (local time), each followed by a cleanupVMBundleIfUnsupported sequence in cowork_vm_node.log:

2026-04-23 22:11:32
2026-04-24 00:43:56
2026-04-24 01:11:22
2026-04-24 09:23:09
2026-04-24 09:30:13

Steps to Reproduce

  1. Install/upgrade Claude Desktop to 1.3883.0 on Windows 11 x64 (not ARM64).
  2. Sign in to a Max plan account, open Cowork / Code.
  3. Use actively (chat, file edits, MCP tools) for 30–90 minutes.
  4. Renderer crashes — UI freezes / white-screens / reloads. claude.ai-web.log receives the BuddyBleTransport_$_reportState entry at the same moment.

Reproduces consistently under normal workload. No specific user action seems to trigger it — the IPC call happens from renderer-side initialization / polling.

Diagnostic findings (Windows-specific)

CheckResult
Crashpad/reports/empty — Electron does not dump renderer crashes of this kind
Windows Application Event Logno claude.exe Application Error / WER entries in 24h — not a hard OS-level crash
Hyper-V, HypervisorPlatform, VirtualMachinePlatformall enabled — virtualization stack not the cause
yukonSilver not supported in cowork_vm_node.logunrelated — feature intentionally disabled on this config
Wall-clock vs crash correlation1:1 with each BuddyBleTransport_$_reportState log entry

Workaround (confirmed working)

Downgrading to 1.3561.0 eliminates the crashes completely. Squirrel preserves previous builds under %LOCALAPPDATA%\AnthropicClaude\app-*\:

Get-Process -Name "claude" -ErrorAction SilentlyContinue | Stop-Process -Force
& "$env:LOCALAPPDATA\AnthropicClaude\app-1.3561.0\claude.exe"

Squirrel will silently auto-upgrade back to 1.3883.0 eventually, so this workaround is not permanent.

Pattern (cross-reference)

This is the same class of bug as:

  • #48281 — primary macOS report, OPEN. I posted a Windows confirmation there before filing this separate report: #48281 (comment).
  • #48261 — same BuddyBleTransport_$_reportState error co-occurring with V8 OOM on macOS 1.2581.0. OPEN but labeled invalid.
  • #37346 — identical "No handler registered" pattern on Windows 1.1.7714.0 with a different handler (ComputerUseTcc_$_getState), closed as stale without structural fix.

The common root cause in all four: the renderer bundle calls an IPC method that the main process never registers → unhandled promise rejection → renderer process dies.

Request

  1. Acknowledge the Windows platform scope of the BuddyBleTransport_$_reportState bug (either in this issue or by expanding #48281's labels to include platform:windows).
  2. Either register the missing IPC handler in main, or gate the renderer call-site behind a typeof handler === 'function' / feature-flag guard so a missing handler becomes a no-op instead of a crash.
  3. Document how to pin Claude Desktop to an older working version (disable Squirrel auto-upgrade for a specific installation) as a temporary mitigation for affected Windows users.

Claude Model

Not applicable (Desktop binary crash, not a model issue)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

1.3561.0

Claude Code Version

Claude Desktop 1.3883.0 (Windows 11 x64 build, not ARM64)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

N/A (Desktop app, not CLI)

Additional Information

I can provide the full log bundle (claude.ai-web.log, main.log, cowork_vm_node.log — scrubbed of session-ID UUIDs) on request. Support ticket also filed via [email protected] referencing this issue and #48281.

extent analysis

TL;DR

Downgrade to version 1.3561.0 to eliminate the crashes, as this version does not exhibit the BuddyBleTransport_$_reportState IPC error.

Guidance

  • The issue is likely caused by a missing IPC handler for BuddyBleTransport_$_reportState in the main process, leading to an unhandled promise rejection and renderer crash.
  • To verify, check the claude.ai-web.log for the recurring error message and correlate it with the crash timestamps in cowork_vm_node.log.
  • As a temporary mitigation, pin Claude Desktop to version 1.3561.0 by stopping the current process and running the older version from %LOCALAPPDATA%\AnthropicClaude\app-1.3561.0\claude.exe.
  • To prevent Squirrel from auto-upgrading to the faulty version, consider disabling auto-upgrade or seeking guidance from Anthropic Support.

Example

Get-Process -Name "claude" -ErrorAction SilentlyContinue | Stop-Process -Force
& "$env:LOCALAPPDATA\AnthropicClaude\app-1.3561.0\claude.exe"

Notes

The root cause is consistent with other reported issues (#48281, #48261, #37346), suggesting a structural fix is needed to register the missing IPC handler or add a feature-flag guard.

Recommendation

Apply the workaround by downgrading to version 1.3561.0, as it has been confirmed to eliminate the crashes, until a permanent fix is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#installation#prompt issue#agent setup#task chaining

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Claude Desktop 1.3883.0 — repeated renderer crashes on Windows 11 x64 (BuddyBleTransport `No handler registered`) [1 participants]