[BUG] Claude Desktop Shows Persistent White/Blank Screen on Windows 10 After Running for a Period of Time

Resolved 💬 1 comment Opened May 25, 2026 by zIv-AlT Closed May 28, 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?

After the Claude Desktop app has been running for a period of time, the entire content area goes completely blank/white. The window frame (minimize, maximize, close buttons) remains visible, but no UI content is rendered inside it. The app becomes fully unresponsive and cannot be recovered without force-killing all Claude processes via Task Manager.
This occurs after the app has been open for a while — it does not happen immediately on launch.

What Should Happen?

The Claude Desktop app should remain stable and render normally throughout the entire session, regardless of how long it has been running or whether it has been minimized or placed in the background.

Error Messages/Logs

No error dialog or crash message is shown. The app window remains open with a blank white content area and no visible error output.
(Optional: If you can find logs, check %APPDATA%\Claude\logs\ and attach relevant entries)

Steps to Reproduce

1.Launch Claude Desktop on Windows 10
2.Use the app normally for a period of time (or minimize/background the window)
3.After some time, the content area turns completely white/blank
4.Clicking, resizing, or waiting does not restore the UI
5.The only recovery is to open Task Manager, end all claude.exe processes, and relaunch the app

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Version 1.8555.2 (a476c3)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗