Clash for Windows: Complete Installation & Configuration Guide 2026

Introduction: Why Clash Verge Rev

The original Clash for Windows project was archived in November 2023. Since then, the community has rallied around several successors, and Clash Verge Rev has emerged as the most actively maintained fork for Windows users. It brings a modern interface built on Tauri, a robust rule engine, and full compatibility with existing Clash Meta (mihomo) cores.

This guide walks you through every step, from downloading the installer to having a fully functional proxy on your Windows machine. No prior experience with Clash is needed. If you get stuck at any point, check our node connection troubleshooting guide or subscription import fixes.

System Requirements and Prerequisites

Before you begin, make sure your system meets these minimum requirements:

• Windows 10 version 1809 or later (64-bit only)
• At least 200 MB of free disk space
• An active proxy subscription from your service provider
• Administrator privileges on your computer

If your subscription URL has expired or you are not sure whether it is still valid, refer to our subscription import troubleshooting article for steps to verify and refresh your link.

Downloading Clash Verge Rev

Always download Clash Verge Rev from the official GitHub repository to avoid supply-chain attacks. The project is hosted at github.com/clash-verge-rev/clash-verge-rev.

Navigate to the Releases page and download the file that matches your architecture:

• x64: Clash.Verge_x.x.x_x64-setup.exe (most common)
• arm64: Clash.Verge_x.x.x_aarch64-setup.exe (for ARM-based Windows devices)

Installation Walkthrough

The installer follows a standard Windows setup wizard. Double-click the downloaded .exe file and follow these prompts:

1. Accept the license agreement
2. Choose the installation directory (the default is fine for most users)
3. Click Install and wait for the process to complete
4. Launch Clash Verge Rev from the Start menu or desktop shortcut

On first launch, the application may prompt for administrator permissions. This is required to modify system proxy settings and, later, to enable TUN mode. Grant the permission and proceed.

Initial Core Selection

When you first open the app, you will see a core selection screen. Choose mihomo (the Clash Meta core). This is the most feature-complete and actively maintained core. The app will automatically download the matching core binary if it is not already present.

Importing Your Subscription

Once the main interface loads, follow these steps to import your subscription:

1. Click the Profiles tab in the left sidebar
2. In the URL field at the top, paste your subscription link
3. Click the Import button
4. Wait for the download to complete (a green indicator confirms success)
5. Click on the newly imported profile card to activate it

If the import fails, common causes include expired links, network connectivity issues, or format incompatibilities. Our detailed guide on subscription import failures covers all six known causes and their solutions.

Selecting and Testing Nodes

After importing your subscription, switch to the Proxies tab. Here you will see the proxy groups defined by your subscription provider.

Running a Latency Test

Before selecting a node, run a latency test to identify which servers are reachable:

1. Click the delay icon (a small circular arrow) next to each proxy group
2. Wait for all nodes to report their latency values
3. Nodes showing a timeout symbol are currently unreachable and should be avoided

Sort the results by latency to find the fastest available server. For most daily browsing, any node under 200ms will feel responsive.

Enabling System Proxy

Clash Verge Rev intercepts your traffic in two ways: system proxy mode and TUN mode. The system proxy is the simpler option and handles most use cases.

To enable system proxy:

1. Go to the main dashboard
2. Toggle the System Proxy switch to ON
3. A green indicator confirms that the system proxy is active

This modifies your Windows proxy settings to route HTTP and HTTPS traffic through 127.0.0.1:7897 (the default Clash listening port). Applications that respect Windows system proxy settings, such as browsers and most desktop apps, will now route their traffic through Clash.

When System Proxy Is Not Enough

Some applications, particularly those using raw sockets or non-HTTP protocols, ignore system proxy settings. These include certain games, SSH clients, and some development tools. For complete traffic interception, you need TUN mode, which is covered later in this guide.

Setting Up TUN Mode

TUN mode creates a virtual network interface that captures all traffic at the network layer, making it impossible for applications to bypass the proxy. This is essential if you need to proxy traffic from apps that ignore system proxy settings.

Enabling TUN Mode

There are two ways to enable TUN mode in Clash Verge Rev:

Method 1: GUI Toggle

1. Navigate to Settings in the sidebar
2. Find the TUN Mode option
3. Toggle it to ON
4. Accept the administrator permission prompt

Method 2: YAML Override

For more control, you can configure TUN mode directly in your profile override:

tun:
  enable: true
  stack: mixed
  dns-hijack:
    - any:53
  auto-route: true
  auto-detect-interface: true

The mixed stack combines gVisor and System stacks for the best balance of compatibility and performance. The dns-hijack rule ensures all DNS queries are captured by Clash's built-in DNS resolver.

Understanding Rule Mode

Clash operates in three modes: Rule, Global, and Direct. For daily use, Rule mode is the recommended setting. It applies the rules defined in your subscription profile to decide whether each connection goes through a proxy or directly.

Typical rule behavior:

• Domestic Chinese websites route directly (faster, no unnecessary encryption overhead)
• Foreign websites route through your selected proxy
• Ad-tracking domains are rejected at the DNS level

For a deeper dive into rule configuration, read our beginner's guide to Clash rule configuration.

Verifying Your Setup

After enabling the system proxy (and optionally TUN mode), confirm that your traffic is properly routed:

Step 1: Check Your IP Address

Open a browser and visit an IP checking service. You should see the IP address of your proxy server, not your real IP address.

Step 2: DNS Leak Test

Visit a DNS leak testing website. It should show your proxy provider's DNS servers, not your ISP's. If you see your ISP's DNS resolvers, your setup has a DNS leak. Refer to our DNS anti-pollution configuration guide to resolve this.

Step 3: WebRTC Leak Test

WebRTC can sometimes leak your real IP address even when a proxy is active. Use a WebRTC leak test tool in your browser to verify that your real IP is not exposed through WebRTC channels.

Common Issues and Fixes

Issue: "No response from proxy"

This usually means the Clash core has crashed or is not running. Check the Logs tab in Clash Verge Rev for error messages. A quick fix is to restart the application.

Issue: Nodes fail to connect

If latency tests show all nodes timing out, verify that your subscription is still active. Then check that the node protocols are supported by the mihomo core. See our node connection troubleshooting guide for eight detailed causes and fixes.

Issue: Windows Defender flags the installer

This is a known false positive. If you downloaded from the official GitHub repository, add the installation directory to Windows Defender exclusions. Navigate to Windows Security > Virus & threat protection > Manage settings > Exclusions and add the Clash Verge Rev folder.

Issue: TUN mode does not activate

TUN mode requires administrator privileges and the Service Mode helper. In Clash Verge Rev, go to Settings > TUN Mode and ensure that the Clash service is installed and running. If the service shows an error, try reinstalling it from the same settings page.

Issue: Slow speeds on proxied connections

Slow speeds can result from several factors: an overloaded proxy node, incorrect proxy group selection, or TUN mode stack misconfiguration. Try switching to a different node, ensuring you are using the mixed stack in TUN mode, and checking that your DNS configuration is optimized. Our DNS configuration guide covers optimization techniques.