Launching Clash for Windows to a fully blank window (or overlapping, garbled UI) is usually unrelated to networking - the core is often running fine; the Electron interface failed to render.

First: is the proxy still working?

If pages still load through the proxy while the window is blank, this is purely a UI problem - fix the interface, leave the config alone.

Fixes, in order

  1. Full restart: tray icon → Quit (not the window X), confirm no Clash for Windows processes remain in Task Manager, relaunch.
  2. Disable GPU acceleration: the top cause is a graphics-driver/Electron mismatch. Quit fully, then launch with:
    "C:\Program Files\Clash for Windows\Clash for Windows.exe" --disable-gpu
    If that cures it, append --disable-gpu to the shortcut's Target for permanent use.
  3. Clear UI caches: quit, delete the cache folders in the data directory, relaunch:
    %USERPROFILE%\.config\clash\Cache
    %USERPROFILE%\.config\clash\GPUCache
    Cache corruption typically follows power loss or a full disk.
  4. Update the graphics driver - integrated GPUs with old drivers are chronic Chromium troublemakers.
  5. Reinstall over the top - user data survives (see the data directory guide).

Related edge cases

  • Window lost off-screen (after monitor changes): summon via tray double-click, then Win+arrow keys to drag it back.
  • Choppy UI in RDP/VMs is expected - Electron falls back to software rendering without a GPU.
  • Broken glyphs: check system locale settings, or switch the UI language once to force a redraw.
Tip: need to operate Clash while the window is blank? Connect a web dashboard to 127.0.0.1:9090 - the core and the UI are separate processes.