Clash Verge Windows Setup: 7 Common Pitfalls from Download to Service Mode

1. Before You Install: System Requirements and the WebView2 Runtime

The Clash Verge Windows client uses WebView2 to render its settings interface. If the WebView2 Runtime is missing, the app fails to launch or shows a blank window — the first and most common pitfall of the installation stage.

Pitfall 1: Missing WebView2 Runtime

Symptoms: After double-clicking the app icon, the window is blank, or the app crashes after showing a missing WebView2 Runtime prompt.

Cause: Windows 11 and Windows 10 updates from 2022 onward usually include WebView2; older Windows 10 builds need it installed manually.

Fix: Download the x64 offline installer for the WebView2 Runtime from Microsoft's official site, install it, then reopen Clash Verge. No system restart is needed.

System requirements:

• Windows 10 version 1809 (build 17763) or later, or Windows 11
• Intel / AMD devices: choose the x64 installer. ARM devices: choose the arm64 installer.
• Runtime memory usage is about 200 MB; 4 GB of RAM is enough for smooth use.

Download the installer only from the official release page. Files from third-party download sites are outdated and of unknown origin — don't use them.

2. Installing Clash Verge: Path, Permissions, and Service Mode

Installation steps:

1. Run the installer, choose the installation directory, and check 'Create a desktop shortcut'.
2. Click Install and wait for the progress bar to finish.
3. After first launch, go to 'Settings' → 'Service Mode' and click 'Install'.

Pitfall 2: Installation Path Contains Chinese Characters or Spaces

Symptoms: Service mode fails to install, or the virtual network adapter can't be created after enabling TUN mode.

Cause: Windows service registration and the virtual network adapter driver have incomplete support for non-ASCII paths.

Fix: Use the default path C:\Program Files\Clash Verge, or choose a custom path with only English characters and no spaces. If it's already installed under a Chinese path, uninstall and reinstall.

Pitfall 3: Service Mode Installation Fails

Symptoms: After clicking 'Install Service Mode', you get an 'insufficient permissions' or 'installation failed' error.

Cause: The current account isn't an administrator, or security software blocked the service registration.

Fix: Right-click the Clash Verge icon and choose 'Run as administrator', then go to 'Settings' → 'Service Mode' and try again. If it still fails, temporarily disable the security software's system protection and re-enable it after installation.

Service mode runs the mihomo core as a Windows service. TUN mode depends on service mode, and once it's enabled you won't get a UAC prompt on every launch — don't skip this step.

3. Importing a Subscription: Link Formats and Parsing Failures

On the 'Subscriptions' page, click 'New', enter a subscription name, paste the subscription link, and click 'Confirm'. The client fetches the link content and parses it into a node list.

Pitfall 4: Subscription Parsing Fails

Symptoms: After importing, you see 'parse failed' or 'subscription is empty', or the node list shows 0 nodes.

Check these in order:

1. Is the link expired? Open the subscription link directly in a browser. If you get a 401, 403, or an 'expired' message, regenerate the link in your provider's dashboard.
2. Is the response YAML? Opening the link in a browser should show text starting with proxies:. If it returns JSON or sing-box format, switch the subscription format to Clash Meta in your provider's dashboard and import again.
3. Can your network reach the subscription domain? Some network environments can't connect directly to the subscription server. Enable the system proxy first, then click 'Update' on the subscription card and try again.

Subscription links usually look like this:

https://example.com/api/v1/client/subscribe?token=xxxxxxxx

After a successful import, select a node or policy group on the 'Proxies' page. Clash Verge uses the mihomo core, so Clash Meta extension fields like proxy-providers and rule-providers are parsed correctly.

4. Enabling System Proxy: Port Conflicts and Browser Extensions

Clash Verge's default mixed port is 7897, providing both HTTP and SOCKS5 proxy. To enable it: 'Settings' → 'System Proxy' → turn on the switch. The system proxy is written to Windows' Internet Options, so any app that reads the system proxy will use it.

Pitfall 5: System Proxy Is On, but the Browser Still Connects Directly

Cause 1: A proxy extension like SwitchyOmega is installed in the browser. The extension takes over proxy settings and the system proxy is ignored.

Cause 2: Port 7897 is occupied by another program, so the mihomo core fails to start.

Fix:

• Disable or remove the browser proxy extension so the browser follows the system proxy.
• Check port usage from the command line:

  netstat -ano | findstr 7897

• If the output isn't empty and the process isn't Clash Verge, change the mixed port under 'Settings' → 'Port', then restart the app.
• Restart the browser and visit ip.sb to verify the exit IP.

If the browser can't load pages after turning on the system proxy, turn the switch off first, then troubleshoot with the two steps above. Don't keep toggling it on and off.

5. Switching to TUN Mode: Virtual Adapter and DNS Override

TUN mode takes over all system IP traffic through a virtual network adapter and doesn't rely on apps reading the proxy settings on their own. Command-line tools, games, and UDP apps often bypass the system proxy; after switching to TUN mode, all of them are captured.

Prerequisite: service mode is installed. To enable it: 'Settings' → 'TUN Mode' → turn on the switch. The first time you enable it, Windows will show a virtual adapter installation prompt — click 'Allow'.

Pitfall 6: TUN Mode Turns Off Immediately After Enabling

Cause 1: Service mode isn't installed or failed to install.

Cause 2: The virtual adapter driver was quarantined by security software.

Fix:

1. Check that 'Settings' → 'Service Mode' shows 'Installed'.
2. Open Device Manager → Network adapters and confirm the Clash Verge virtual adapter is present.
3. Restore the blocked driver file from the security software's quarantine, then restart Clash Verge.

In TUN mode, it's recommended to enable DNS override as well: 'Settings' → 'DNS Override' → enable Fake-IP. mihomo takes over DNS resolution so that some apps' DNS requests can't bypass the proxy and cause leaks. mihomo's default Fake-IP range is 198.18.0.1/16 — no need to change it.

6. Service Mode, Auto-Start, and Firewall

Once service mode is installed, Clash Verge runs as a system service, so auto-start at boot isn't affected by user login.

Auto-start: 'Settings' → 'Auto Start' → turn on the switch. If the proxy isn't working after boot, check the Startup tab in Task Manager and make sure Clash Verge isn't disabled.

Pitfall 7: Firewall Blocks

Symptoms: After enabling TUN mode, some apps can't connect to the network, and Windows Security shows an 'allow access' prompt.

Fix:

1. When the prompt appears, check 'Private networks' and 'Public networks', then click 'Allow access'.
2. If you accidentally clicked Cancel, go to Windows Security → Firewall & network protection → Allow an app through firewall, and add Clash Verge manually.
3. If it's not in the list, click 'Allow another app' and browse to the Clash Verge executable in the installation directory.

7. Quick Reference: The Seven Pitfalls

8. Verification Checklist After Setup

1. System proxy works: visit ip.sb and confirm the exit IP matches the node's region.
2. TUN works: open Command Prompt and run curl -I https://www.google.com. An HTTP/2 200 response means it's working.
3. Subscription updates: click 'Update' on the subscription card with no errors.
4. Auto-start: restart the computer and confirm you can go online without manually opening the app.

Once you've gone through all seven pitfalls, the Windows setup is complete. If you run into policy group selection or rule matching issues later, check the usage documentation.