How to Install Clash Verge Rev on Windows 10: Setup Guide

Before Installation: Check Windows 10 and the Package

Clash Verge Rev is a Windows graphical client for Clash-compatible configurations. It provides the interface for importing profiles, selecting proxy groups, changing routing modes, viewing connection logs, and enabling features such as the system proxy or TUN mode. The client interface is not the proxy service by itself: traffic handling is performed by the bundled Clash Meta or mihomo-compatible core. This distinction matters when you troubleshoot an installation that appears successful but cannot load a profile or connect to a node.

Before downloading anything, confirm that the computer is running a supported 64-bit edition of Windows 10. Press Win + R, enter msinfo32, and check System Type. Most current Windows 10 computers show x64-based PC. If the machine uses an ARM processor, do not assume that an x64 package is the best choice; look for a compatible build or use the Windows compatibility layer with realistic expectations about performance and driver support.

Keep Windows 10 updated. Install pending cumulative updates and restart before installing a network client. Older system components can cause certificate, firewall, or virtual-network-driver errors.
Close competing network tools. Exit other proxy clients, VPN applications, traffic filters, and network acceleration utilities during the first installation. Multiple programs attempting to control the same proxy or routing table make the result difficult to diagnose.
Prepare enough permissions. The basic application can run without changing system-wide settings, but system proxy integration, TUN mode, and virtual adapter installation may request administrator approval.
Prepare a valid subscription URL or local profile. A successful installation does not automatically provide proxy nodes. You need a configuration supplied by your service provider or a local YAML profile that you are authorized to use.
Use a normal local folder. Avoid installing or extracting the application inside a cloud-synchronized directory, a compressed archive, or a path with unusual permissions. A path such as C:\Apps\Clash Verge Rev is easier to maintain.

Treat the Subscription URL as a Password

A subscription URL normally contains an account token. Anyone who obtains it may be able to download your profile or consume your traffic allowance. Do not paste the complete URL into a public issue, screenshot, chat group, or configuration repository. If it is exposed, reset or rotate it from your provider's account panel and import the replacement URL.

Use the site's download center to choose the Windows package. Prefer an installer when you want automatic shortcuts, a standard uninstall entry, and a smoother first-run experience. A portable archive is useful when you do not want a conventional installation, but it requires you to manage extraction, shortcuts, updates, and write permissions yourself.

Choose the Correct Windows Build

The package name can contain several details: the application name, release number, operating system, CPU architecture, and packaging format. Do not choose a file solely because it is the largest or newest-looking download. Read the filename and select the build that matches the computer.

Build or format	Best use	Important note
Windows x64 installer	Most Intel and AMD Windows 10 computers	Usually the easiest option for a permanent installation
Windows x64 portable archive	Testing, removable storage, or restricted user accounts	Extract fully before launching; do not run it directly inside the archive
ARM64 build	Windows 10 devices with ARM processors	Use only when the hardware and bundled components are compatible
Package for another operating system	macOS or Linux computers	It cannot be installed as a native Windows application

After the download finishes, check the file extension. A normal Windows installer may use .exe or a supported installer package, while a portable download is commonly a .zip archive. If Windows shows that the file came from the internet, right-click it, choose Properties, and review the displayed publisher and file information. A warning is not proof that a file is unsafe, but it is a reason to stop and confirm that the package came from the intended download page rather than an advertisement, mirror, or random file-sharing link.

Windows Defender or SmartScreen may display a warning for a newly published desktop application that has not built enough reputation with Microsoft's detection service. Do not disable antivirus protection globally just to force an installation. Instead, cancel if the filename or source is unexpected, download the package again from the official site, and consult your administrator if the device is managed by an organization. Security software may also quarantine the bundled network component; if that happens, record the exact detection name before taking any action.

Installer or Portable: Which One Should You Use?

The installer is the practical default for a personal Windows 10 computer. It can create a Start menu entry and desktop shortcut, and it makes later removal easier through Settings › Apps › Apps & features. A portable build keeps its files together and may be convenient for temporary testing, but it should still be extracted into a writable folder. Running directly from Downloads or from an archive viewer can prevent the client from saving profiles, logs, or downloaded rule data correctly.

Do not place a portable copy in C:\Program Files unless you understand Windows folder permissions. A user-writable directory such as C:\Tools\ClashVergeRev avoids many “configuration disappeared after restart” problems. Whichever format you choose, keep only one active copy at first. Two copies using the same profile directory or listening ports can produce confusing behavior.

Install Clash Verge Rev on Windows 10

Once the correct package is ready, the installation itself normally takes only a few minutes. The steps below use the installer workflow. If you downloaded a portable archive, extract it to a permanent folder and skip directly to the first-launch checks.

Open the downloaded installer. If Windows asks whether the application may make changes to the device, confirm only after checking the filename and source. A request for administrator approval is expected when the installer needs to create protected files or network components.
Choose the installation location. The default location is suitable for most users. If you select another folder, use a short path without characters that may be interpreted incorrectly by older tools.
Complete the setup wizard. Allow the installer to create a Start menu entry or desktop shortcut if you want quick access. Do not launch several copies while the wizard is still running.
Start the application once. Right-click the shortcut and choose Run as administrator for the first launch if TUN support or a virtual adapter will be used. Basic profile editing and system proxy operation may not require permanent administrator mode.
Approve Windows Firewall prompts carefully. Allow the application on the network types that match your use. Private network access is usually relevant for a trusted home or office network. Public network access should be considered separately, especially on shared Wi-Fi.
Wait for the main window to finish loading. Confirm that the dashboard, profile area, proxy groups, and log panel are visible. If the window opens and immediately closes, record the time and check Windows Event Viewer and the application log before reinstalling repeatedly.

A firewall prompt does not mean that every inbound connection should be allowed without thought. Clash commonly listens on local addresses for HTTP, SOCKS, mixed, or control functions, depending on the configuration. If you only use the client on the same computer, local access is normally enough. LAN access is a separate decision and should be enabled only when another device on your trusted network must use this computer as a proxy gateway.

Do Not Turn on Every Feature at Once

For the first verification, start with the client open, a profile imported, and system proxy enabled. Test that simple path before enabling TUN, LAN sharing, custom DNS, and third-party rule providers. Changing one layer at a time makes it clear which setting introduced a failure.

First-Launch Checks

Look for an application status indicator and confirm that the selected core has loaded without an error. The exact labels can vary between Clash Verge Rev releases, but the important facts are consistent: a profile must be selected, at least one proxy group must contain usable nodes, and the client must have a local mixed, HTTP, or SOCKS listener available before applications can send traffic through it.

Do not confuse a downloaded profile with an active connection. A profile can import successfully while every node is unavailable, expired, or incompatible with the current core. Open the proxy group, select a node manually, and inspect the log after starting a test request. A healthy local setup should show that the request entered Clash and was assigned to the chosen policy, even if the remote node itself later fails.

Import a Profile and Complete the Basic Setup

After installation, open the profile or configuration section. Most providers give a subscription URL, while advanced users may have a local YAML file. For a subscription, use the add or import function, paste the complete URL, assign a recognizable name, and save it. For a local file, choose the file from disk and keep a backup copy outside the application's working directory.

Import the profile. Make sure the URL begins with the protocol supplied by the provider, usually https://. Avoid removing query parameters because they may carry account or format information.
Update the profile. Run an update only after the profile appears in the list. If the update fails, check the exact error: a timeout, TLS certificate problem, HTTP status error, or invalid YAML requires a different fix.
Select the active profile. Importing several profiles does not necessarily make the newest one active. Click the intended profile and confirm that its proxy groups populate.
Select a policy group and node. Start with a manually selected node instead of an automatic latency group. This gives you a stable baseline for testing.
Choose a mode. Rule mode is usually the best starting point because traffic follows the rules in the profile. Global mode sends matching traffic to one selected proxy and is useful for testing but may route domestic or local services unnecessarily.
Enable the Windows system proxy. Turn it on from the client dashboard or tray menu. This affects applications that respect Windows proxy settings; it does not automatically capture every program.

Setting	What it changes	Recommended first value
Mode	How matched connections are assigned to outbounds	Rule
Policy group	The node or group used by a rule	Manual selection for initial testing
System proxy	Windows HTTP and HTTPS proxy settings	On for browser testing
TUN	Creates system-level traffic capture through a virtual interface	Off until basic proxy mode works
Allow LAN	Permits other devices to connect to local listeners	Off unless specifically needed

System proxy mode and TUN mode solve different coverage problems. System proxy mode changes Windows proxy values, commonly using local addresses such as 127.0.0.1 and a client listener port. Browsers and many desktop applications follow these values, but software that uses its own network stack may ignore them. TUN mode works closer to the network layer and can capture more applications, but it may require administrator approval, a virtual adapter, route changes, and correct DNS interception.

Use TUN only after confirming that normal proxy mode works. In Clash-compatible configurations, TUN commonly depends on settings such as automatic route handling, interface detection, and DNS hijacking. An incorrect combination can cause duplicate routes, inaccessible local devices, or a loop where Clash tries to proxy its own control traffic. If enabling TUN breaks connectivity, turn it off first, restore the previous system network state, and then review one option at a time.

Verify That the Client Is Ready

A good installation test checks more than whether the window opens. Test the local listener, the selected policy, DNS behavior, and recovery after restarting the client. Keep the test simple: use one browser, one selected node, and one profile so that an unrelated application does not hide the source of the problem.

Confirm the profile is active. The profile list should show the selected configuration, and the proxy group should contain nodes rather than an empty or parsing-error state.
Select a known working node. Automatic selection can be useful later, but a fixed node makes the first diagnosis easier.
Enable system proxy. Open Windows Settings › Network & Internet › Proxy and confirm that the manual proxy values reflect the client listener. Do not edit them manually unless you know which listener the profile exposes.
Open a browser test page. Visit a service that reports the outbound address and compare the result with the selected node's expected region. An address change confirms routing, not necessarily correct DNS handling.
Read the Clash log. Load a page and check whether the request appears with a rule, policy group, and connection result. A timeout, DNS error, connection refusal, or rejected rule points to different layers.
Test a local address. Open a local router or intranet address if appropriate. A correct rule profile should not accidentally send every private address through a remote node.
Restart and retest. Close the client completely from the tray menu, reopen it, and confirm that the profile, selected group, and system proxy state behave as expected.

Observation	Likely meaning	Next check
The dashboard opens but no groups appear	The profile was not imported, failed to parse, or contains no usable proxies	Review the profile update message and YAML structure
Browser traffic does not enter the log	System proxy is off, the browser bypasses it, or another tool controls the proxy	Check Windows Proxy settings and close competing clients
Requests enter the log but all nodes time out	The remote nodes, transport parameters, or subscription may be invalid	Test another node and update the profile
Web pages work but some applications do not	Those applications may ignore system proxy settings	Consider TUN after the basic setup is stable
Internet stops when TUN is enabled	Route, DNS hijack, adapter, or permission conflict	Disable TUN, restore connectivity, then inspect TUN settings

When checking DNS, remember that a successful page load does not prove that every DNS request follows the intended path. Some applications use their own encrypted DNS, while others send queries directly to the system resolver. If the profile uses fake-IP or a custom DNS module, the addresses shown by diagnostic commands may look different from ordinary public IP results. Compare the Clash log, the active DNS configuration, and the application's behavior together rather than treating one number as the complete diagnosis.

A Complete First-Run Baseline

The installation is ready for normal configuration when the application stays open, a profile imports and updates, a proxy group contains selectable nodes, browser requests appear in the log, the selected mode behaves as expected, and Windows connectivity returns normally after the client is closed.

Common Windows 10 Installation Problems

Windows Blocks the Installer or a Component

SmartScreen, Defender, or an organization policy may prevent the installer from starting. First verify that you downloaded the intended Windows build and that the filename has not changed unexpectedly. On a managed computer, application-control policy may block unsigned or unfamiliar software even when the package is legitimate. In that situation, contact the administrator rather than attempting to bypass the policy. If the installer starts but a network component is removed, inspect the security product's quarantine history and use its documented review process.

The Profile or Settings Disappear

This often happens with a portable copy placed in a read-only folder, a directory controlled by synchronization software, or a second application instance using a different data path. Exit the client completely, move the portable folder to a writable local directory, and import the profile again. Avoid editing generated configuration files while the client is running because the interface or update process may overwrite those changes.

The Port Is Already in Use

A local listener cannot start if another process already occupies the configured port. Check the log for a message such as “address already in use,” then close other proxy applications and restart Clash Verge Rev. Advanced users can identify the process with netstat -ano in Command Prompt and map the process ID through Task Manager. Change the listener port only after confirming which applications depend on it; changing a port without updating the related system proxy setting can leave the browser pointed at a dead listener.

Uninstalling or Reinstalling

Before uninstalling, export or copy any configuration that you are allowed to keep. Turn off system proxy and TUN mode first, then exit the client from the tray. Use Settings › Apps › Apps & features to remove the installed application. A reinstall should be a later troubleshooting step, not the first response to a profile or node failure, because reinstalling the interface does not repair an expired subscription or an invalid remote configuration.

FAQ: Clash Verge Rev on Windows 10

Does installing Clash Verge Rev include proxy nodes?

No. The installation supplies the client interface and its supported core, but nodes come from a profile or subscription that you obtain separately. Import a valid configuration, update it, and select a policy group before testing traffic.

Should I use Global mode or Rule mode after installation?

Start with Rule mode when the profile contains suitable domestic, private-network, and proxy rules. Global mode is useful as a short diagnostic because it sends matching traffic to one selected proxy, but it can add latency to local services and consume node bandwidth unnecessarily.

Why does the browser work while another application does not?

The browser probably follows the Windows system proxy while the other application uses a separate network stack or ignores system proxy values. Confirm this in the Clash log. If broader capture is required, test TUN mode only after normal proxy mode is stable and after reviewing its administrator, route, and DNS requirements.

Is administrator mode required every time?

Basic profile management and system proxy use may work without permanent elevation. TUN mode, virtual adapters, route changes, or privileged helper operations can require administrator approval. Grant only the permissions needed by the feature you are enabling, and avoid running the application as administrator by default unless the setup specifically requires it.

Once the first launch and connectivity checks pass, continue with the site's setup tutorial for profile organization, rule modes, DNS choices, and TUN configuration. Keeping the initial configuration simple gives every later change a clear baseline.