›_ Claude Code Issues
Claude Code Issues / #66495

[BUG] Desktop — Progressive Renderer Degradation on Windows 11 / NVIDIA G-Sync

Status Fixed / completed
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 7 comments · opened Jun 9, 2026 · closed Jun 16, 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?

Bug Report: Claude Desktop — Progressive Renderer Degradation on Windows 11 / NVIDIA G-Sync

Reported by: David Mitchell
Date: June 2026
App Version: Claude Desktop 1.11187.4
Install type: MSIX / Windows Store package (Claude_pzs8sxrjxfjjc)

-----

Environment

|Property |Value |
|---------------------|----------------------------------------------------------------------------------|
|OS |Windows 11 (recent Windows Update applied) |
|App version |Claude Desktop 1.11187.4 |
|Install method |MSIX via Microsoft Store / WindowsApps |
|Exe path |C:\Program Files\WindowsApps\Claude_1.5354.0.0_x64__pzs8sxrjxfjjc\app\Claude.exe|
|GPU |NVIDIA GeForce GTX 1080 |
|GPU driver |581.57 (Game Ready; updated via Windows Update) |
|Monitor |ASUS ROG — G-Sync enabled, 2560×1440 |
|Connection |DisplayPort |
|Windows display scale|100% |
|G-Sync mode |Enabled for windowed and full screen |

-----

Bug Description

Claude Desktop’s Electron renderer enters a progressively degraded state during normal use. Affected regions become visually blurry/soft. The blur is a rendering artefact, not a display or cable issue.

-----

Symptoms

  • Sidebar and conversation pane progressively blur during use
  • Entry/compose pane remains sharp throughout
  • Blur is visible in Windows screenshots (confirms software/rendering issue, not hardware)
  • Blur is triggered by window movement — moving the Claude window or any other open window causes the degradation
  • Blur is intermittent but reproducible
  • Browser version (claude.ai in Chrome/Edge) is completely unaffected

-----

Temporary Workarounds (confirmed effective)

All of the following force a re-rasterisation and restore sharpness:

|Workaround |Notes |
|----------------------------|-------------------------------------------------|
|Ctrl++ then Ctrl+0 |Zoom in then reset — forces full renderer repaint|
|Maximise then restore window|Forces DWM recomposition |
|Refocus the window |Clicking back into Claude restores sharpness |

-----

Root Cause Hypothesis

Electron renderer + Windows DWM compositor + NVIDIA G-Sync interaction.

When any window is moved, Windows DWM enters a live compositing state and redraws the desktop. The Claude Electron renderer appears to drop to a lower-quality rendering surface during this process and does not recover automatically.

Specifically suspected:

  • Windows 11 “Optimisations for windowed games” presentation model
  • G-Sync VRR interaction with windowed Electron surfaces
  • Electron GPU compositing not correctly invalidating/repainting regions after DWM compositing events

Supporting evidence from GitHub issue #56805:

“Electron GPU compositing causes excessive redraws. When the mouse moves over the Claude window, the Electron renderer triggers continuous frame repaints. DWM then re-composites these frames on the NVIDIA GPU, creating a bottleneck. Launching Claude Desktop with --disable-gpu-compositing resolves the issue.”

-----

Solutions Attempted

✅ Previously effective — no longer sufficient after driver/Windows update

|Fix |Method |Outcome |
|------------------------------------------|-----------------------------------------------------------------|-----------------------------------------------------------------------------|
|Monitor Technology → Fixed Refresh |NVIDIA Control Panel → Program Settings → claude_pzs8sxrjxfjjc |Previously fixed blur on focus change; no longer sufficient |
|Disable “Optimisations for windowed games”|Windows Settings → System → Display → Graphics → Claude → Options|Previously fixed window-movement blur; still applied but no longer sufficient|

❌ Attempted — ineffective

|Fix |Method |Outcome |
|----------------------------------------------------------|----------------------------------------------------|---------------------------------------------------------------------------|
|OverlayTestMode = 5 registry key |HKLM\SOFTWARE\Microsoft\Windows\Dwm — disables MPO|No effect |
|App update to latest version |Relaunched via in-app update prompt |No effect |
|Reinstall from claude.ai/download |Uninstall + fresh MSIX install |No effect — MSIX packaging reinstalls to WindowsApps regardless of source|
|DPI compatibility override |Right-click exe → Properties → Compatibility |Blocked — WindowsApps is a protected directory |
|--disable-gpu / --disable-gpu-compositing launch flags|Not applicable |Blocked by MSIX sandboxing |
|Transparency effects disabled |Windows Settings → Accessibility → Visual effects |No effect |

🔲 Not yet attempted

|Fix |Method |
|--------------------------------|-------------------------------------------------------------------|
|Disable FXAA for Claude |NVIDIA Control Panel → Program Settings → Antialiasing - FXAA → Off|
|Disable G-Sync for windowed mode|NVIDIA Control Panel → Set up G-SYNC → Full screen only |
|Switch to NVIDIA Studio Driver |Download from nvidia.com — replaces Game Ready driver |

-----

Key Constraint: MSIX Packaging Blocks Standard Electron Fixes

Claude Desktop on Windows is distributed exclusively as an MSIX package installed to C:\Program Files\WindowsApps\. This has significant consequences:

  • DPI compatibility settings cannot be applied — the exe is in a protected directory
  • Electron GPU launch flags are blocked — --disable-gpu, --disable-gpu-compositing, ELECTRON_EXTRA_LAUNCH_ARGS are all ignored
  • Per-app GPU control panel profiles have limited effect — the sandboxed presentation path overrides some NVIDIA Control Panel settings
  • Users cannot work around this — the fix must come from Anthropic

Reference: GitHub issue #63650 — Claude Desktop blurry on high-DPI display due to MSIX packaging blocking DPI override

-----

Impact

  • Affects all Windows users running Claude Desktop on NVIDIA G-Sync setups
  • Cowork and Claude Code require the desktop app — browser workaround is not viable for these users
  • The --disable-gpu-compositing flag is confirmed to resolve the issue but is inaccessible due to MSIX packaging

-----

Suggested Engineering Actions

  1. Expose a user-configurable GPU flag mechanism that works within the MSIX sandbox — or pass --disable-gpu-compositing by default on Windows
  2. Investigate Electron renderer invalidation on DWM compositing events — the renderer should recover automatically without requiring a zoom or resize
  3. Consider offering a non-MSIX installer for Windows — this would restore all standard Electron DPI/GPU workarounds to users and reduce support burden
  4. Test against G-Sync + windowed mode configurations — this is a common setup among the professional/prosumer audience Claude targets

-----

References

What Should Happen?

No issues with display…text should not blur.

Error Messages/Logs

No error messages

Steps to Reproduce

Add this section to the report:

Steps to Reproduce

  1. Install Claude Desktop on Windows 11 via the official installer from claude.ai/download (installs as MSIX package)
  2. Open Claude Desktop
  3. Open any other application window alongside Claude
  4. Move any window (Claude or another application) around the screen
  5. Observe sidebar and conversation pane progressively blur
  6. Note that the compose/entry pane remains sharp
  7. Confirm blur is visible in a Windows Snipping Tool screenshot (rules out hardware/cable/monitor cause)

To confirm the renderer has degraded:

• Press Ctrl++ then Ctrl+0 — sharpness immediately restores
• Or maximise then restore the Claude window
• Or click away then refocus the Claude window

Expected behaviour: Renderer maintains sharpness throughoutActual behaviour: Renderer enters degraded state after window movement, requires manual forced redraw to recover

That’s precise enough for an engineer to reproduce it on a matching setup.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Desktop version 1.11187.4

Platform

Other

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

References
• #56805 — Screen Flickering & Mouse Lag on Windows
• #63650 — Claude Desktop blurry due to MSIX packaging
• Google AI Overview: “Claude app window goes blurry when looking at other windows” — identifies NVIDIA G-Sync / Electron GPU context loss as root cause

View original on GitHub ↗

6 Comments

github-actions[bot] · 4 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/56805

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

davidm4164-web · 4 months ago

This is not a duplicate issue.

davidm4164-web · 4 months ago

Appears to have been patched and fixed

he6q · 2 months ago

Additional data point: consistent blur pattern, likely tied to Per-Monitor DPI Awareness V1 (not V2)

I've been debugging a persistent text-blurring issue on Claude Desktop (Windows, MSIX build) for a couple of weeks and wanted to share findings that seem to align closely with this issue.

Environment

  • OS: Windows 11 (64-bit)
  • CPU: Intel Core i5-11400 (iGPU: Intel UHD Graphics 730)
  • Discrete GPU: NVIDIA GeForce RTX 3070 Ti
  • Monitors: one 4K + multiple 2K displays (mixed, non-uniform scaling tested)
  • Claude package: MSIX (Claude_pzs8sxrjxfjjc)

Symptom

  • Text renders sharp right after launch.
  • The moment the mouse cursor hovers over the window, blurring begins and never resolves on its own.
  • A full re-layout (resizing the window, or moving it to a different monitor) temporarily resets it to sharp — then it degrades again over time/interaction.
  • The area directly under the mouse cursor stays in focus while the rest of the window remains blurry, at every scaling level tested (150%, 200%, 300%).

Tests performed (ruling things out)

  • GPU driver update, NVIDIA per-app GPU selection, Windows "High performance" graphics preference → no effect
  • Windows "Hardware-accelerated GPU scheduling" → no effect
  • electron-flags.conf with --disable-gpu, --disable-gpu-compositing, --disable-direct-composition → --disable-gpu alone improved sharpness only immediately after launch, degraded again on interaction
  • Registry EnablePerProcessSystemDPI=1 ("Let Windows try to fix apps that aren't blurry") → minor improvement only
  • NVIDIA windowed G-Sync disabled → no effect
  • Forcing integer display scaling (100% / 200% / 300%, vs. non-integer 125%/150%) → blur becomes progressively less noticeable at higher scale, but never fully disappears
  • GPU cache folder cleared → no lasting effect

Key finding: DPI Awareness level
Checked via Task Manager → Details → "DPI Awareness" column:

  • claude.exe (main window process): Per-Monitor (V1)
  • Other apps confirmed as Per-Monitor V2 on the same system for comparison

Given Per-Monitor V1 is known to fall back to bitmap-stretching for some UI/text regions on mixed/high-DPI multi-monitor setups (unlike V2, which renders natively throughout), this seems like a strong candidate root cause — and it would explain why:

  • the error is a fixed absolute amount that becomes less visible at higher effective pixel density (higher OS scaling or higher native resolution monitors)
  • freshly-invalidated regions (under the cursor) render correctly while the rest of the frame keeps a stale/incorrectly-scaled bitmap

Since this is an MSIX-packaged app, end users can't override the app manifest to force Per-Monitor V2 awareness ourselves. If the packaged manifest could be updated to declare PerMonitorV2 DPI awareness, this might resolve the issue (or at least be worth testing).

Happy to provide more logs/screenshots if useful.

Petro-for-Claude · 1 month ago

Confirmed fix in my case: switching from Game Ready Driver to NVIDIA Studio Driver.

Setup: Windows 11, NVIDIA GPU, Samsung monitor (FreeSync/VRR), Claude Desktop (MSIX), display scaling 150%.

Symptoms matched this issue exactly: the app rendered sharp on launch, then degraded to a blurry/low-quality surface after the window was moved or repainted, and did not recover on its own. Ctrl + + then Ctrl + 0 (or maximize/restore) temporarily restored sharpness every time, which confirmed it was a renderer-repaint/GPU-compositing issue rather than DPI scaling (blurriness persisted even at 100% scaling).

Reducing display scaling did nothing. What actually fixed it permanently: ### uninstalling the GeForce Game Ready Driver and installing the NVIDIA Studio Driver instead. After the switch the blurriness is gone and hasn't returned.

Since "Switch to NVIDIA Studio Driver" was listed under "Not Yet Attempted" above — this is a confirmation that it works, at least on this configuration. A proper in-app option to disable GPU compositing / hardware acceleration would still be the real solution, since the driver swap is a workaround, not something every user can or should do.

grallbring · 1 month ago

<img width="1644" height="1141" alt="Image" src="https://github.com/user-attachments/assets/077cb56b-e4a8-416c-99d5-9eeee4dceb28" />

The application is being g-synced for me as well (visible by the indicator in the top right of the application), even though I have "Fullscreen Only" active in my NVIDIA settings. This causes flickering and uneven mouse movements. NVIDIA driver version: 616.56.

Showing cached comments. Read the full discussion on GitHub ↗

Related Claude Code issues

Matched on shared title terms, labels, topic and reported release — ranked so issues with real discussion come first.

Browse by topic

Same class of failure, ranked by community engagement — this issue is one of many, so it may not appear in the visible list: Windows & WSL problems

Browse all Claude Code issue topics →