Before You Download
Clash Verge Rev is a Windows desktop client for managing proxy profiles and a Clash-compatible core. The client provides the interface and controls; a subscription or configuration provides proxy nodes, groups, and rules. Installing the app by itself does not provide a working proxy service. You will need a subscription from a provider or a configuration you are authorized to use.
Start at the Clash client download page and select the Windows build that matches your computer. Most Windows 11 PCs with Intel or AMD processors use the x64 package. Windows on ARM requires an ARM64 build when one is offered. If you are unsure, open Settings > System > About and check System type. Do not choose a package based only on the Windows 11 version number.
Use the current download information on the client page rather than an old installer saved on a third-party site. Release assets and supported Windows versions can change. Check the listed package type, architecture, and release notes before downloading. A file whose name contains “x64” is not the right choice for every Windows 11 device.
| Check | Where to look | Why it matters |
|---|---|---|
| Processor architecture | Settings > System > About | Helps you select x64 or ARM64 when both builds are available |
| Available disk space | File Explorer > This PC | Leaves room for the installer, app files, and downloaded profiles |
| Subscription access | Your provider’s account or setup message | The client does not include your provider’s nodes or account access |
| Other proxy or VPN apps | Windows Settings and the system tray | Another app may change proxy settings or compete for network control |
Install and Open Clash Verge Rev
After downloading, open the folder containing the installer and check that the filename and package type match the Windows build you intended to get. If Windows shows a security warning, pause and confirm that you obtained the file from a source you trust and that its release details match. Do not disable Microsoft Defender or bypass a warning for an unfamiliar file simply to continue.
- Double-click the downloaded installer. If Windows asks whether to allow the app to make changes, check the app name and confirm only if you intended to install it.
- Follow the installer prompts. Keep the default installation location unless you have a specific reason to change it, and do not install a second copy into a different folder to work around a failed update.
- When setup finishes, open Clash Verge Rev from the Start menu. If you do not see it immediately, search for the app name in Start rather than launching a similarly named file from an unrelated download folder.
- Allow the app time to start its interface and core. If Windows asks for permission to communicate on private or public networks, read the prompt before choosing. A local desktop proxy normally does not need to be exposed to public networks.
The interface may change between releases, so labels and locations can differ slightly. Look for sections named Profiles, Proxies, Settings, and connection or log status. If the window opens but the core does not start, check the app’s status or logs before importing the same profile repeatedly.
Some features require additional Windows permissions. For example, TUN mode creates a virtual network interface and may request administrator access or a driver-related confirmation. This is separate from installing the client and is not required for the basic system-proxy test later in this guide. Do not approve an unexpected driver prompt from an app or installer you cannot verify.
Import a Profile and Choose a Node
In Clash Verge Rev, open Profiles or the equivalent profile-management page. Choose the option to add a profile from a URL, paste the subscription address provided by your service, and start the import or download. If your provider gives you a configuration file instead, use the local-file import option where available. The quick-start instructions at the setup guide cover the general subscription-import process.
Wait for the download to finish, then select the imported profile so it is active. A profile appearing in the list is not enough: it may be downloaded but not selected, expired, or unable to parse. If the app displays a configuration error, open its log or profile details and note the first meaningful error message. A message about a missing field, unsupported proxy type, or invalid YAML can point to a provider-side compatibility issue rather than a Windows installation problem.
- Confirm that the imported profile is selected and that its update status is successful.
- Open the proxy-group or Proxies page and choose a usable node in the group that handles your traffic. Some groups select a node automatically; others require a manual choice.
- Keep the normal rule-based mode for the first test. Global mode changes routing more broadly and is not needed just to check that a selected node works.
- Check that the core is running and that no profile or port error is shown in the app’s status or logs.
Subscription profiles can include proxy groups and rules as well as nodes. The name of a group is not necessarily the name of a server, and choosing a node in one group may not affect traffic assigned to another. If the app shows a connection or rule panel, use it to see which rule and proxy chain handled a test request.
Enable the System Proxy and Test It
For a beginner’s first connection check, use Clash Verge Rev’s System Proxy control rather than enabling TUN immediately. System Proxy asks Windows to use the local proxy endpoint provided by the running core. This is generally the simplest route for browsers and other applications that respect the Windows proxy settings. It does not automatically redirect every program on the computer.
- In the client, confirm the active profile and selected node, then turn on System Proxy.
- Check that Windows did not show an error and that the client indicates the proxy is enabled. If the client displays a local port, note it; the port can differ by configuration, so do not assume it is always
7890. - Open a new browser tab and visit a site that you expect to use the proxy. If the site does not load, test another known site before changing multiple settings.
- Return to the client’s connections or logs view. Check whether the test request appeared and which rule or proxy group handled it.
A browser test can fail even when the client is running if the profile routes that site directly, the chosen node is unavailable, or the browser uses a separate proxy setting. Conversely, seeing the System Proxy switch enabled does not prove that every application is routed through Clash. Some games, command-line tools, and applications with their own network settings may ignore Windows’ system proxy.
If you need to route applications that do not honor the system proxy, consider TUN only after the basic test works. TUN uses a virtual network interface to capture more traffic and can require administrator approval. It may also conflict with another VPN, firewall, or traffic-filtering application. Enable one routing method at a time so that you can identify which change affects the result.
| Control | Typical scope | Use for the first test? |
|---|---|---|
| System Proxy | Applications that follow Windows proxy settings | Yes; it is a straightforward starting point |
| TUN | Captures a broader range of network traffic through a virtual interface | No; test the profile and system proxy first |
| Global mode | Changes how matching traffic is directed through proxy groups | No; Rule mode is usually easier to diagnose |
Fix Common First-Run Problems
When a first test fails, avoid changing the profile, mode, node, and Windows settings all at once. Make one change, test again, and check the logs. This makes it easier to distinguish a client-startup issue from a subscription problem, a node outage, or an application that does not use the system proxy.
The app will not open or closes immediately
Search for Clash Verge Rev in the Start menu and try opening it once more. If it still fails, restart Windows to clear a pending installer or update, then check whether your security software recorded an alert. Confirm that you installed a package for your processor architecture and that the installer came from a trusted source. Avoid deleting app data as a first step; it may remove profiles or settings that would help identify the problem.
The profile imports, but the node does not connect
Update the profile if the provider allows it, confirm it remains selected, and try another available node in the relevant group. Check the client’s logs for DNS, timeout, authentication, or unsupported-protocol errors. A subscription may download successfully while a particular node is offline, credentials have expired, or the installed core does not support a configuration feature. If several nodes fail with similar errors, send the provider the error text with the subscription URL removed.
The browser still appears to connect directly
Check that System Proxy is enabled in the client and that the core is running. Close and reopen the browser, then test a site that should be handled by a proxy rule. Inspect the request in the client’s connections view: if it is marked DIRECT, a rule or group may intentionally have routed it without a proxy. If no request appears, the browser may use its own proxy setting, a separate profile, or a network extension that changes routing.
Windows reports a permission or network conflict
First disable other proxy or VPN tools temporarily and retest. Two applications may compete to set the Windows proxy or control a virtual adapter. If only TUN fails, close the client, reopen it with the required permissions if appropriate, and inspect the specific driver or permission message. Do not switch off Windows Firewall as a general troubleshooting step. If you deliberately need LAN access, configure it separately and restrict it to trusted networks rather than exposing the proxy on public Wi-Fi.
After the First Successful Test
Once a browser request is routed as expected, leave the working profile selected and learn where the client reports its core status, active mode, and connection history. Update the profile only through your provider’s intended method, and avoid replacing a working configuration with an unknown file. If the provider changes node types or configuration fields, check the client and core compatibility notes before assuming the profile is broken.
You can then decide whether Windows System Proxy is sufficient for your normal applications. If you need wider traffic capture, read the TUN settings carefully, check for conflicts with other networking tools, and test with one application at a time. For additional installation and profile steps, use the quick-start guide; to choose or update a client, return to the download page.
A reliable setup is not defined by having every switch enabled. It is a setup where the correct profile is active, the intended node or group is selected, the chosen routing method matches the applications you use, and the connection can be verified in the client. Keeping those checks separate makes future updates and troubleshooting much easier.