Install Clash Verge Rev on Windows 10/11: Setup, Proxy, and Startup

Before you install: check your system, architecture, and configuration source

Clash Verge Rev is a graphical client that typically uses the mihomo core to handle proxy connections, DNS, and rule-based routing. Installing the client prepares the software environment; to connect to proxy nodes, you’ll also need a valid subscription or a configuration you maintain yourself. The client installer, subscription URL, and node service are three separate things.

This guide covers Windows 10 and Windows 11 desktop PCs. Minimum system requirements, installer names, and settings categories may vary by release, so check the release notes for your version before downloading. This guide uses the Chinese interface labels for “subscription,” “proxy,” and “settings”; in English, these are commonly called Profiles, Proxies, and Settings.

Choose an installer

1. Open Windows Settings → System → About and check System type. Most Intel- and AMD-based desktop PCs use the x64 installer; for ARM devices, choose the ARM64 package if the release provides one.
2. Visit the client downloads page, find the Windows download for Clash Verge Rev, and check the release’s supported Windows versions and processor architectures.
3. Save the installer before running it. If it reports that WebView2 Runtime is missing, install the Microsoft Edge WebView2 Runtime as prompted, then restart the client.

First launch: finish installation and review permissions

Double-click the installer, choose an installation folder in the setup wizard, and complete installation. On first launch, use a standard user account; there’s no need to enable “Run as administrator” by default. Managing subscriptions and using the system proxy generally don’t require the entire interface to run with elevated privileges.

1. Launch Clash Verge Rev and check that the main window opens and the client icon appears in the system tray.
2. Open Settings and note the current version, mixed port, and service mode status for troubleshooting later.
3. Open Logs and check for recurring configuration parse errors or failed port bindings.
4. If Windows Firewall asks whether to allow network access, choose the scope that matches your setup. For local use only, there’s no need to allow access on public networks to share the proxy.

A Windows SmartScreen reputation warning is different from a malware detection by security software. If a warning appears, verify the download source, publisher information, and release notes before proceeding. If you can’t confirm the source, don’t run the file. If your security software quarantines it, review the specific detection under Windows Security → Virus & threat protection → Protection history. Don’t turn off real-time protection.

The window opens, but the content is blank

Exit the client from the system tray, then launch it again. If the window is still blank, check that the WebView2 Runtime is working, Windows is up to date, and security software hasn’t blocked the interface components. Don’t keep installing different versions over and over. Back up your configuration first, then follow the troubleshooting notes for your release to repair the runtime environment.

Import a subscription, then choose a node

Subscription URLs often contain account tokens, so treat them like passwords. Don’t paste the full URL into public logs, screenshots, or online configuration converters. Import it only after confirming that the provider supports the Clash or mihomo configuration format.

1. Open Profiles, paste the full URL into the subscription link field, and click Import. In some versions, this option is under New.
2. Wait for the remote content to download, then check that a configuration card appears. If the import fails, check the HTTP status code and parse error first; don’t change the system proxy yet.
3. Select the configuration card to make it active. A configuration appearing in the list doesn’t mean the core is already using it.
4. Open Proxies, set the mode to Rule, expand the policy group used to access external services, and choose an available node.
5. Run a latency test, then visit a website you actually need and check the matched rule and outbound connection on the Connections page.

A successful latency test only shows that the test address is reachable. It doesn’t guarantee that every website, streaming service, or UDP connection will work. If the test returns a result but websites won’t load, check the policy group selection, DNS, and connection logs for the target site.

What to check when an update fails

• 401 or 403: Check the subscription token, expiration date, and provider restrictions. Repeatedly clicking Update won’t fix an authorization issue.
• Timeout or DNS lookup failure: Check your local connection and the subscription domain. If updates are routed through the proxy, first confirm that the current node can still connect.
• YAML parse error: Check whether the response is actually a configuration, rather than a login page, error page, or unsupported node list.

Updating a subscription may replace remote configuration content. To keep custom rules, use the override or extension mechanism supported by your client and read its documentation first. Changes made directly to the remote configuration may be lost on the next update.

System proxy: start by testing with a browser

For your initial setup, use the system proxy and leave TUN, browser proxy extensions, and other VPNs off. Fewer moving parts make it easier to tell whether the core hasn’t started, the app isn’t using the proxy, or the node is unavailable.

1. Turn on System Proxy in the client and keep the mode set to Rule.
2. Open Windows Settings → Network & Internet → Proxy and check that the manual proxy points to the local listening address.
3. Use the port shown in the client. For example, if the mixed port is 7897, the address is usually 127.0.0.1 and the port is 7897. Don’t copy 7890 from another guide.
4. Temporarily disable proxy management extensions in your browser. Close and reopen the browser, then visit the target page.
5. Return to the client’s Connections page, find the request, and check whether it used a direct connection or a proxy node.

Test from a terminal

Some command-line programs don’t use the Windows system proxy. In PowerShell, specify a proxy explicitly to test the connection to the local listening port. The example below uses mixed port 7897; replace it with the port shown in Settings before running the commands.

Test-NetConnection 127.0.0.1 -Port 7897
curl.exe --proxy http://127.0.0.1:7897 --head --max-time 15 https://example.com/

TcpTestSucceeded : True means a TCP connection to the port succeeded; it doesn’t guarantee the remote node is available. Even if the second command returns an HTTP error status, check the client’s connection records to see whether the request went through the proxy. If it times out, continue troubleshooting the node and rules. These commands check connectivity, not actual speed.

Service mode and TUN: enable them only when needed

The system proxy works for apps that follow the system proxy settings. Games, some launchers, command-line tools, and apps that create their own network connections may bypass it. TUN mode routes eligible traffic through a virtual network interface, giving it broader coverage but potentially affecting routing, DNS, and compatibility with other VPNs.

Install service mode

1. Open Settings and find Service Mode. If your version places it in a submenu, follow the layout shown in that version.
2. Click the button to install the service. When Windows User Account Control appears, verify the program’s source before approving it.
3. Wait until the status shows that the service is installed and running, then turn on Service Mode. Some versions enable it automatically after installation, so check the status.
4. If you need TUN, turn on TUN Mode and check the logs for errors initializing the virtual interface, routes, or DNS.

Service mode uses a background service for tasks such as managing the core that require elevated privileges. It’s not the same as the system proxy, and it doesn’t mean TUN is enabled. Installing the service doesn’t automatically route traffic from every app.

If your company intranet, printer, or local network services stop working after you turn on TUN, turn TUN off to compare, then check your subnet bypass rules and other VPNs. Don’t run multiple apps that take over system routing unless you understand how they interact. UDP availability also depends on the node protocol, server support, and routing rules; the TUN switch alone can’t provide those.

Launch at startup: verify the UI, core, and proxy separately

“Launch at startup” usually means the client starts after you sign in to Windows; it doesn’t determine when a background service starts. A running service also doesn’t guarantee that the interface has loaded the selected configuration. Restart your PC once to verify the startup setup.

1. Turn on Launch at startup in Settings. To keep the desktop clear, you can also enable the silent launch or start minimized option if your version provides one.
2. Open Windows Settings → Apps → Startup and check that the client’s startup entry isn’t disabled. You can also check under Startup apps in Task Manager.
3. Keep a configuration and policy group selection that you’ve already verified works. If you use TUN, make sure Service Mode is running properly.
4. Restart your PC and sign in. Once the desktop and system tray have loaded, check that the client started, the core is running, and the configuration is active.
5. Visit a target website and check the outbound connection on the Connections page. If you use the system proxy, also verify the proxy address and port in Windows.

If the startup entry exists but the client doesn’t launch, first check security software logs, whether the installation folder has changed, and the client logs. Don’t create a scheduled task right away; it could launch a second instance and cause a port conflict. Windows’ Restart apps feature may also reopen windows that weren’t closed properly, so don’t confuse it with the client’s startup setting.

Common issues: follow the logs and avoid stacking settings

Port conflict: “address already in use”

Exit other proxy clients first, then check which process is listening on the local port. The example below uses 7897 and returns the process ID using that port.

Get-NetTCPConnection -LocalPort 7897 -State Listen |
  Select-Object LocalAddress, LocalPort, OwningProcess

Find the process by PID under the Details tab in Task Manager. Once you’ve confirmed what it does, close the related program normally, or change the mixed port in Clash Verge Rev and turn System Proxy back on. Don’t end an unfamiliar system process. If the command returns no listening process, check for port reservations or permission errors; an empty result alone doesn’t prove the core is working.

The browser loses internet access after closing the client

First, check Windows Settings → Network & Internet → Proxy. If the manual proxy still points to 127.0.0.1 after the client has exited, turn off the manual proxy. For a normal shutdown, turn off System Proxy in the client before choosing Exit from the system tray to avoid leaving proxy settings behind after an unexpected exit.

Service installation fails or TUN won’t start

Note the error shown during service installation, then check whether your account has administrator approval, security software quarantined a service component, or another VPN is running. Get the system proxy working first, then test Service Mode and TUN separately. To remove the service, use the client’s uninstall service option whenever possible; don’t manually delete an unknown service.

What to gather before requesting help

• Record your Windows, client, and core versions, along with the installer architecture.
• Record the mode, mixed port, and whether System Proxy, Service Mode, and TUN are on.
• Include only the relevant log lines from around the error. Hide subscription tokens, account details, and node credentials.
• Say whether the issue is reproducible and what changes when TUN is off and other proxy apps are closed.

Once the basic setup works, add custom DNS, rule overrides, or LAN sharing one at a time. Keep a way to roll back each change; changing several settings at once makes issues harder to isolate. For general troubleshooting steps, see the troubleshooting guide. To understand the differences between policy groups, rules, and TUN, see the quick reference.