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