Updated July 2026 · 6 min read
Fix Windows WebView2 issues
The tray icon is there and the process is running, but the main window is blank white or never appears at all. Nine times out of ten the WebView2 runtime that draws the interface is at fault, not the proxy.
A white window points at the UI layer
The client is built with Tauri, so the interface is rendered by the WebView2 runtime that lives in Windows, while the core and the tray menu run separately. That is why pages keep loading fine while the window shows nothing at all.
You can turn that into a test. If the tray menu responds and traffic still flows, and only the window is blank or missing, the runtime is the suspect and there is no point digging through configs and logs.
Check whether the runtime is installed
Windows 11 ships the WebView2 runtime, so it is rarely missing there. Windows 10 is another story, especially on trimmed-down images, heavily optimised installs and machines that have not seen an update in years, where it was often stripped out during setup.
Search the installed apps list for WebView; an entry named Microsoft Edge WebView2 Runtime means it is present. If nothing shows up, take the evergreen installer from the WebView2 page on the Microsoft site rather than from whatever download portal a search throws at you.
While the window is white the proxy usually still works. Do not start by reinstalling the client — its installer never touches the runtime, so the window stays just as white.
Repairing beats reinstalling the client
Find the WebView2 runtime in the installed apps list and choose the modify or repair option rather than removing it. The repair pulls the missing files down again, which is exactly what a half-deleted runtime needs, and it keeps the existing registration intact.
Quit the client from the tray completely before you run the repair, then start it again. Reinstalling Clash Verge Rev does nothing here because its installer does not maintain the runtime; the two are separate products.
Old runtimes frozen by company policy
Managed machines often have evergreen auto-update switched off by policy, which leaves the runtime stuck on a build from long ago. The window is then not always fully white: half-empty panels and buttons that ignore clicks are more typical.
Either ask IT to allow the update or install a current runtime by hand. And keep debloat scripts away from the Edge components: plenty of them remove the runtime as well, and reinstalling only helps until the script runs again.
What is the project?
Clash Verge Rev is a Tauri-based GUI for Mihomo with profile management, system proxy, TUN mode, rule editing and WebDAV backups.