Windows Install Clash Verge Rev: Full Walkthrough from Download to Working Rule-Based Routing

Pre-Install Checklist: Windows Version, WebView2, and Installer Type

Clash Verge Rev is a desktop client built on the Tauri framework, so its UI rendering relies on the system's built-in WebKit/WebView component, while the core proxy logic runs on the Clash Meta (mihomo) engine. Before you download anything, check these three things first — it'll save you half the troubleshooting later.

1. Windows version: You need Windows 10 or later, 64-bit. Windows 7/8.1 isn't supported — installing on an older system will likely crash on launch or fail to start at all.
2. WebView2 runtime: Tauri apps on Windows depend on the Microsoft Edge WebView2 runtime to render the interface. Most systems updated in the last couple of years already have it built in, but some lightweight or long-untouched installs are missing it, which shows up as a blank window or the app not opening after install.
3. Installer type: Official releases usually offer both an .exe installer and an .msi package — the former is the standard setup wizard, the latter suits silent deployment or bulk installs in enterprise environments. For everyday use, grab the .exe and click through the wizard.

Download and Install: Pick the Right Source, Understand the Installer

The part of the download step that trips people up isn't the process itself — it's where you get the file from. Third-party mirror sites often distribute outdated builds, and in some cases bundle in extra content you didn't ask for. Stick to the official release channel, where the version number and release date are clearly listed.

1. Download the installer that matches your architecture (almost all regular laptops and desktops are x64; ARM devices are rare — if you're not sure, go with x64).
2. Double-click the installer. If Windows SmartScreen pops up with an "Unknown publisher" warning or similar block, click "More info" and then "Run anyway" — this is just Windows' standard caution for newly released apps, not a sign anything's wrong with the installer.
3. Keep the default install path unless you have a specific reason to change it — you'll get more complete default permissions, which lowers the odds of Service Mode authorization failing later.
4. Once the install finishes, don't close the wizard right away — check the "Launch Clash Verge Rev" box and move on to the next step.

First Launch: Importing a Subscription and a Quick Tour of the UI

On first launch, the main window is usually split into a few areas: navigation on the left or top (Subscriptions, Proxies, Rules, Logs, Settings) and an overview of your currently active config in the middle. First thing to do is import your subscription.

1. Go to the "Profiles" (subscription) tab, click to add a new subscription, paste your subscription URL, and click Download to confirm.
2. Once the download succeeds, the subscription entry will show the node count and expiration date (if that info is included in the subscription). Click "Enable" or just click the subscription card to set it as the active profile.
3. Switch to the "Proxies" tab and confirm the proxy group (usually named Proxy, Auto, or a custom group name from your subscription) is showing a list of nodes and isn't empty.

Service Mode and TUN Mode: Authorization and the Right Order to Enable Them

In regular mode, Clash Verge Rev can only intercept traffic from apps that respect the system proxy setting. To capture all traffic system-wide — including apps that ignore the system proxy and some system processes — you need TUN mode. On Windows, TUN mode has to create a virtual network adapter, which requires administrator privileges, and turning it on directly would trigger a UAC prompt every single time — which is exactly why Clash Verge Rev ships with "Service Mode."

Service Mode hands off the operations that need admin rights (creating the virtual adapter, setting up routing tables) to a background Windows service that runs persistently, so the main client no longer needs to run as administrator, and toggling TUN mode no longer pops up a prompt every time. Here's the correct order to set it up:

1. Go to the "Settings" tab, find the "Service Mode" option, and click Install/Enable. A system permission prompt will appear once — confirm it. This is the only manual authorization step you'll need.
2. Once the service installs successfully, go back to the main window (or the "Network Settings" tab) and flip on the TUN mode switch.
3. Check the status indicator — with TUN mode running correctly, it should show the virtual adapter as connected. At this point, also switch the proxy mode to "Rule" instead of "Global" — Global mode routes everything through the same exit node with no rule-based routing, which is fine for quick troubleshooting but not for daily use.

Verifying Rule-Based Routing Actually Works

A finished install doesn't mean a working config, and a working config doesn't mean routing is doing what you expect. Spend two minutes on a quick check instead of relying on a vague "seems fine" feeling.

Check	What to do	Expected result
Blocked site	Open a site in your browser that's normally inaccessible	It loads normally — the proxy chain is working
Local site	Open a commonly used local website or app	It opens via direct connection, not through a proxy node — meaning rule-based routing is actually active, not global proxying
Log panel	Open the "Logs" tab and visit both types of sites above	You should see the two requests matching different proxy groups or rules, not both landing on the same one

If local sites are also being routed through a proxy node, you're likely missing a direct-connection rule, or the current proxy group mode is set to "Global" instead of "Rule" — go back and double-check the mode setting from the previous section. If it's the other way around and sites that should go through the proxy fail to load even with direct connection, first confirm the corresponding node responds in a latency test on the "Proxies" tab, then check whether your rule set actually includes a matching domain or IP range.

Common Windows Install Errors and Fixes

• Window flashes and disappears, or nothing opens at all: This almost always means the WebView2 runtime is missing. Search "WebView2" in Windows "Apps & features" — if it's not there, install the official runtime separately, then relaunch the client.
• Install fails with a "missing VC++ runtime" or similar dependency error: Install the matching Visual C++ Redistributable package (x64 version) — this is a dependency for some lower-level components, unrelated to the Clash Verge Rev version itself.
• Service Mode install fails with a permissions error: Confirm your Windows account has administrator rights and isn't blocked from installing system services by Group Policy — common on corporate managed machines. Contact your IT admin, or fall back to regular mode (system proxy only, no TUN).
• Internet drops after enabling TUN mode: Usually caused by a conflict between the virtual adapter and another VPN client's virtual adapter on your machine — close any other similar tools and test again. If it's still dropping, disable TUN mode and fall back to system proxy mode to confirm the base proxy connection works before troubleshooting further.
• Node list doesn't refresh after a subscription update: Check the auto-update interval in your subscription settings, or manually click the refresh button on the subscription entry. Some subscription providers rate-limit updates, so refreshing too often in a short time can get you throttled.

Follow this walkthrough from downloading the installer through confirming rule-based routing works, and you'll have covered the full path to a working Clash Verge Rev setup on Windows. If you get stuck at any step, first figure out whether the problem is with "install dependencies," "subscription content," or "mode configuration" — then jump to the matching section above. That's faster than just reinstalling and hoping it fixes itself.