Windows Setup for the Clash Client: System Proxy, TUN Mode, and Common Pitfalls

Install Clash on Windows, import a subscription, and configure system proxy or TUN mode. Troubleshoot firewall blocks, port conflicts, and service permissions.

Install the Client: Check Your System Architecture First

This guide uses Clash Verge Rev on Windows 11. Clash Verge Rev provides a graphical interface for managing subscriptions, configurations, and the system proxy; mihomo is the core that handles connections, DNS, and rule matching. After installing the client, you still need to import and activate a valid configuration. Seeing the tray icon does not mean the proxy is working.

  1. Open Windows Settings → System → About and check the processor architecture under System type. Choose the x64 installer for an x64 processor. On ARM devices, use an ARM64 installer if the client provides one. If there is no build for your architecture, choose a client that supports it.
  2. Run the installer obtained from the official release channel. On first launch, turn off the system proxy and TUN switches in the client, then check the logs for repeated configuration parsing errors or listener binding failures. If an organization policy blocks the installer, ask your administrator about the approval process; do not change security policies.
  3. Check the system tray for other proxy clients that may be running. Before switching, note the existing Windows proxy address, port, or setup script. Quit the old client from its tray menu: closing its main window may only minimize it.

Import a Subscription: Know the Difference Between Downloading, Activating, and Choosing an Egress

Open Subscriptions in the left sidebar of Clash Verge Rev. Paste the Clash or mihomo subscription URL from your provider into the import field and import it. Button placement may vary between versions. After importing, select the subscription card to make it the active configuration, then open Proxies to check the policy groups and nodes. Creating a subscription card alone does not switch the configuration used by the core.

  • Returns 401 or 403: Check that the subscription is still valid and the URL is complete. Also check whether your provider requires a specific client entry point. Never paste a subscription URL containing query parameters into a public support ticket or online conversion site.
  • Download succeeds, but parsing fails: Check the first parsing error in the logs. The subscription URL may be returning a login page or a format intended for another client. Ask your provider for a compatible output. If the error started after adding a local override, disable the override first and check whether the original configuration loads.
  • Configuration loads, but connections fail: In Proxies, manually select a node in the relevant selection group, then test it with the application you need to use. A speed test only shows that its test request reached the test address; it does not prove that a particular domain will use the same egress.

For initial testing, use Rule mode. The core checks rules in order and uses the egress or policy group specified by the first matching rule. Traffic that matches no rule is usually handled by the final MATCH rule. Compare the destination domain, matched rule, and actual egress in Connections or the logs. If you see DIRECT, check the routing result before blaming the node.

System Proxy: Test Browser Traffic First

Turn on System Proxy in the client settings and leave TUN off for now. Then open Windows Settings → Network & internet → Proxy and check that the address and port under Manual proxy setup match the client's active listener. For example, if the local listener is 127.0.0.1 and the actual mixed-port is 7897, check for 127.0.0.1:7897. This port is only an example for troubleshooting, not a default for every client.

Open a new page in a browser that follows the system proxy settings, and watch the client's Connections list. You can also specify the local HTTP proxy explicitly in PowerShell to separate proxy issues from browser extensions or settings:

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

Before running the command, replace 7897 with the actual HTTP or mixed proxy port. This checks the explicit proxy path; it does not verify that the Windows switch is working or guarantee that the rules select a remote node. If the command works but the browser does not, check the browser's own proxy settings, extensions, and Windows proxy bypass list first. Some command-line tools, games, and background services do not use the Windows system proxy, so it is possible for a browser to work while an application shows no connection records.

TUN Mode: Check Service Permissions and Routing Separately

TUN receives IP traffic routed through a virtual network interface, making it useful for apps that do not read the system proxy settings. It does not mean every connection will use a remote node: route exclusions determine which traffic enters the core, and connections that do enter still follow the rules to select an egress. Turn off the system proxy while testing TUN to identify which entry point an app depends on. This does not mean the two modes can never be used together.

  1. In Clash Verge Rev settings, find the options for service mode and the virtual network interface. If your version asks you to install the service first, use the option provided by the client and confirm the Windows UAC prompt only after checking who authorized it. Installing the service and turning on TUN are separate steps. After installation, check the service status and core logs.
  2. After turning on TUN, run Get-NetAdapter in PowerShell to check the interface, then compare routing changes before and after with Get-NetRoute -AddressFamily IPv4. If the app uses IPv6, also check with Get-NetRoute -AddressFamily IPv6. Interface names vary by configuration and version. Seeing an interface only confirms that it was created; it does not prove the target traffic is reaching the core.
  3. Restart an app that did not previously use the system proxy, start a new connection, and check the client's connection records. If there is no record, check for routing conflicts first. If there is a record but DNS resolution fails, check the DNS logs and the tun and dns sections in the active configuration. See the configuration reference for field definitions.

If turning on TUN makes a corporate VPN or local network service unreachable, turn TUN off and test the same destination again. If access returns, investigate overlapping routes, DNS routing, or interface selection before switching nodes. On managed devices where installing services or adding virtual interfaces is not allowed, use a system proxy or application proxy approved by your administrator.

Port Conflicts, Firewall Blocks, and Restoring Connectivity

Listener Fails to Start: Check the Process Before Changing Ports

If the logs show address already in use or Windows socket error 10048, first identify whether the failing port belongs to the proxy listener or the control interface. They serve different purposes; do not enter the control interface port in Windows proxy settings. The commands below use proxy port 7897 as an example:

$listeners = Get-NetTCPConnection -State Listen -LocalPort 7897 -ErrorAction SilentlyContinue
$listeners | Select-Object LocalAddress, LocalPort, OwningProcess
$listeners | ForEach-Object { Get-Process -Id $_.OwningProcess }

If the port is held by an old client, quit it normally from the system tray. If it belongs to an app you need to keep, choose an unused port in the current client's settings or a local override. Then turn the system proxy off and back on, and check that Windows has the new port. No command output only means no matching TCP listener was found at that moment; check the logs to confirm the bound address and port.

Firewall Prompts: Separate Local Proxy Use from LAN Access

For local use only, bind the proxy to the loopback address and keep LAN sharing off. A Windows inbound firewall prompt does not mean the core's outbound connections have failed, and local use does not require opening inbound access on public networks. If the local proxy connects but the logs repeatedly show upstream dial failures, check outbound restrictions on the current network and records from endpoint security software. On managed networks, an administrator should configure any exception for the specific app and network scope.

Most Apps Lose Connectivity: Roll Back the Two Switches Separately

  1. If you just turned on TUN, turn it off first and retry a site that worked before. This helps determine whether virtual routing or DNS caused the problem.
  2. If the browser still cannot connect, turn off System Proxy in the client, open the Windows Proxy settings page, and restore the previous manual proxy or setup script. Do not delete existing organization settings.
  3. Once basic network access is restored, enable only the entry point you need and retest the same site in the same app. Note the client version, core version, active port, and first error in the logs. Before sharing logs, remove subscription URLs, node credentials, and sensitive local addresses.
Download Clash