Skip to content

[BUG] Claude Desktop on Windows continually crashes. #28900

Description

@BrettToney

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • 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?

This is random but occurs frequently. I will use Claude Desktop app for Windows for 2 or 3 hours straight. I go to check my email and come back and everything is gone. Just the desktop app frame is gone. No information inside the app. Usually, I go to my systems tray and just kill claude and restart it. That will work for maybe 2 or 3 times. But eventually, it won't restart properly. If I click the claude icon in the system tray, a simple large search box appears at the top of my screen. Then I have to go in and kill the application in Task Manager. Then it will restart properly. But who knows for how long. LOL... while I was over here typing this, Claude froze again and now there are 2 claude icons in the system tray. This is crazy.

What Should Happen?

It shouldn't crash at all.

Error Messages/Logs

[claude.ai-web.log](https://github.com/user-attachments/files/25569326/claude.ai-web.log)
[cowork_vm_node.log](https://github.com/user-attachments/files/25569328/cowork_vm_node.log)
[main.log](https://github.com/user-attachments/files/25569329/main.log)
[main1.log](https://github.com/user-attachments/files/25569327/main1.log)
[unknown-window.log](https://github.com/user-attachments/files/25569325/unknown-window.log)

Steps to Reproduce

There are no verifiable steps to produce it.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.59 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

Activity

  1. github-actions commented on Feb 26, 2026

    @github-actions

    Found 3 possible duplicate issues:

    1. [BUG] Claude for Desktop not exiting #15368
    2. [BUG] Claude Desktop Windows leaves orphaned renderer processes after quit, preventing restart #15423
    3. [BUG] Claude Desktop on Windows crashes repeatedly — requires reboot each time #27710

    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

  2. BrettToney commented on Feb 26, 2026

    @BrettToney
    Author

    I know what is causing it. Don't minimize claude in any way or it will freeze.

  3. SilentCogitator commented on Mar 1, 2026

    @SilentCogitator

    Yes indeed. Reproducible on Windows 11 Pro 25H2. Latest version of Claude Code.
    On relaunch after minimizing it, the application either renders a blank gray window with no visible UI components or becomes unresponsive and crashes. No visible exception or error message is displayed.

  4. nerdx86 commented on Mar 4, 2026

    @nerdx86

    Adding another data point from Windows 10 Enterprise N LTSC 2019 (build 17763) with Claude MAX account.

    On our system, Claude Desktop v1.1.4498 crashes deterministically on startup -- never reaches UI. Two processes crashed at the exact same fault offset (0x0000e892, BEX exception 0xc0000409) within 26 seconds of each other. The root cause has been fully diagnosed in #28470: a missing id field in a formatMessage() call in the Cowork/yukonSilver VM support check throws an unhandled promise rejection that kills the renderer.

    Re: the minimizing trigger mentioned by @BrettToney -- on LTSC 2019 the app never gets far enough to minimize. It crashes during initialization before any window renders. The Squirrel (non-MSIX) install path appears to be the common factor across reports.

    Environment: Dell laptop, Intel i7-10850H, 64GB RAM, NVIDIA Quadro RTX 3000 + Intel UHD hybrid GPU. Pinned to a known-good older version as workaround.

  5. karimsamca commented on Mar 8, 2026

    @karimsamca

    Adding data from another affected system. Same 0xc0000409 (STATUS_STACK_BUFFER_OVERRUN) crash, MSIX install (not Squirrel).

    Environment

    • Windows 11 Home 25H2 (Build 26200)
    • CPU: 12th Gen Intel Core i7-12700K
    • RAM: 32 GB
    • Claude Desktop versions affected: 1.1.5368 and 1.1.5749 (latest as of 2026-03-08)
    • Install method: Microsoft Store (MSIX)

    Crash details

    • Exit code: 3221226505 (0xC0000409 - STATUS_STACK_BUFFER_OVERRUN)
    • 4 crashes in main.log across 2 sessions, all mid-project with has_active_query: true
    • Crash happens during active Claude Code (cowork) sessions, not on startup
    • App auto-updated from 1.1.5368 to 1.1.5749 today -- crash persists on both versions

    Timeline from logs

    Timestamp App Version Session
    2026-03-07 4:24 PM 1.1.5368 local_80c29362
    2026-03-07 5:36 PM 1.1.5368 same session (retry)
    2026-03-08 4:06 PM 1.1.5749 local_9629dbf7
    2026-03-08 4:07 PM 1.1.5749 same session (retry)

    Stack trace (from main.log)

    Error: Claude Code process exited with code 3221226505
        at Udt.getProcessExitError (C:\Program Files\WindowsApps\Claude_1.1.5749.0_x64__pzs8sxrjxfjjc\app\resources\app.asar\.vite\build\index.js:202:6760)
        at ChildProcess._handle.onexit (node:internal/child_process:294:12)
    

    Additional error
    Signature verification also fails after the crash:

    signature verification failed: client executable is not signed: C:\Program Files\WindowsApps\Claude_1.1.5749.0_x64__pzs8sxrjxfjjc\app\claude.exe
    

    Notes

    • This is the MSIX (Store) install, not Squirrel -- so the bug is not limited to the Squirrel install path as suggested in earlier comments
    • error_category: 'process_crashed', is_startup_error: false -- confirms crash is mid-session, not on launch
    • No Crashpad dump files were generated (reports/ directory is empty)
    • Free memory at crash time: ~5.7 GB (not a memory pressure issue)
  6. github-actions commented on Apr 7, 2026

    @github-actions

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

  7. github-actions commented on Apr 14, 2026

    @github-actions

    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.

  8. locked as resolved and limited conversation to collaborators on Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:desktopbugSomething isn't workingplatform:windowsIssue specifically occurs on WindowsstaleIssue is inactive

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions