Install Clash on Windows: System Proxy, Firewall & Admin Permissions
Choose an installer, launch Clash, import a subscription, and configure the system proxy or service mode. Troubleshoot firewall blocks, port conflicts, and antivirus false positives.
Choose an Installer: Check Your Windows Architecture First
For initial setup, start by testing your browser with the system proxy before deciding whether to enable TUN. This guide uses Windows 11 and Clash Verge Rev as examples: the client handles the interface, subscriptions, and system integration, while the mihomo core listens on local ports, matches rules, and establishes connections. A window opening only confirms that the interface has launched; make sure the core and configuration are also running correctly.
- Open Windows Settings → System → About (called System Information in some versions) and check System type. Choose the x64 installer for an x64-based processor. For an ARM-based processor, use the ARM64 installer if that build is available for your version.
- Choose an installer that matches your system from the Windows downloads page. Check the release notes for the minimum Windows version and any dependencies. If the installer requests permission, make sure the prompt comes from the installer you just launched. On managed devices, use an installation method approved by your organization.
- Launch the client from the Start menu after installation. If you previously had another Clash client installed, fully quit it from the system tray first. Closing its window may leave the core running in the background and its local ports in use.
Import a Subscription: Check That It Downloads, Parses, and Activates
On the Subscription page in Clash Verge Rev, paste the Clash-compatible subscription URL provided by your service, import it, and select the new profile. To use a local file, choose the option for importing a YAML configuration. Button names may vary between versions. Confirm that the new profile appears in the subscription list, is selected, and that the Proxies page shows the policy groups defined in that profile.
- Download failed: Check the client logs first. DNS resolution failures, connection timeouts, and HTTP 403 responses point to different issues. Check whether your current network can resolve and reach the subscription domain, and whether the link has expired or is restricted by your account permissions.
- Download succeeded, but parsing failed: Make sure the response is a configuration supported by the client, not a login page or error message. Ask the provider which subscription format to use. Changing the file extension alone will not fix an invalid format.
- Profile selected, but connections fail: Check the active policy on the Proxies page. In rule mode, rules are matched in
rulesorder. Requests matched byDIRECTconnect directly, so they cannot be used to test whether a proxy node is working.
Enable the System Proxy: Verify Three Steps with One Visit
On the Settings page in Clash Verge Rev, enable System Proxy and leave TUN off. Then open Windows Settings → Network & internet → Proxy → Manual proxy setup and check the address and port. A local proxy usually points to 127.0.0.1; use the port shown in the client's current configuration. For example, this mihomo configuration exposes a local 7897 mixed port that accepts both HTTP and SOCKS connections:
mixed-port: 7897
allow-lan: false
- Visit a site that you know should match a proxy policy using a browser that follows Windows proxy settings. If the browser has its own proxy configured, first check which settings it actually uses.
- Check the visit in the client's Connections or Logs page. Confirm that the request reached the core, then check the matched rule and outbound policy. If the log shows
DIRECT, the request reached the client but did not go through a proxy node. - If the browser works but a desktop app does not, check whether the app supports its own HTTP or SOCKS proxy settings. The Windows system proxy does not route all traffic, and some apps ignore it. Command-line tools may also use separate environment variables.
Service Mode and TUN: Enable Only When You Need to Route More Traffic
Service mode and TUN solve different problems. Service mode lets the client use an installed Windows service to perform operations that require elevated permissions. TUN uses a virtual network interface to receive traffic routed to it by the system. Installing the service does not enable TUN, and enabling TUN does not change the order in which configuration rules are matched.
To test TUN, find the service mode option on the Settings page, install the service as prompted, and approve the Windows User Account Control request. Then enable Virtual Network Adapter mode or TUN mode. Turn off the system proxy during testing so you don't mistake its effect on the browser for TUN working. Test your browser, the target app, and any local network connections you need to keep working.
Insufficient Admin Permissions or No Internet After Enabling
Installing the service requires elevated permissions, but you usually don't need to run the entire client as an administrator for everyday system proxy use. If service installation fails, press Win + R, open services.msc, and check whether the client service is listed. Use the client logs to tell an installation failure from a startup failure. If your organization blocks service installation, contact your administrator.
If enabling TUN disrupts your corporate VPN, intranet sites, or printer, turn TUN off first and check whether the original connection returns. Then look for conflicts involving virtual adapters, routes, or DNS settings. If a domain won't open but a known-working IP address responds, that can help point to a DNS issue; it does not prove the virtual adapter is faulty.
Firewall, Port Conflicts, and Security Software Alerts
No Inbound Firewall Rule Needed for Local Use
A local browser uses the loopback address, so there's no need to expose proxy ports to your local network. If a firewall prompt appears, first check whether Allow LAN is enabled. If you need to provide a proxy to trusted devices on your local network, follow your organization's policy in Windows Security → Firewall & network protection → Advanced settings. Restrict inbound rules to the actual listening app and required ports, and limit them to private networks and trusted source addresses. Don't disable the firewall to troubleshoot a local issue.
Find the Conflicting Process by Its Listening Port
If the logs show address already in use, use PowerShell to check the TCP port reported in the error. The example below uses 7897. The second command maps the PID in the listening record to a process name:
Get-NetTCPConnection -LocalPort 7897 -State Listen |
Select-Object LocalAddress, LocalPort, OwningProcess
Get-NetTCPConnection -LocalPort 7897 -State Listen |
ForEach-Object { Get-Process -Id $_.OwningProcess }
If the process using the port is an old client, quit it from its system tray menu. If another program that needs to keep running occupies the port and 7898 is available locally, change the current client's mixed port to 7898. Restart the core, then recheck the Windows system proxy and any app-specific proxy port. If no listening process is found, check the logs to see whether the core exited because of a configuration error instead of assuming the port is occupied.
Tell SmartScreen Warnings Apart from Malware Detections
A SmartScreen reputation warning is not the same as a Microsoft Defender threat detection. If an installer or core has been quarantined, open Windows Security → Virus & threat protection → Protection history and check the detection name, affected path, and time to identify the file involved. Stop the installation if you can't verify where the file came from. If you suspect a false positive, submit it for review through the project's or security vendor's official channels. Don't exclude your Downloads folder, client folder, or entire drive.
Restore Windows Network Settings Before You Quit
To stop temporarily, turn off TUN and the system proxy enabled by the client, then quit from the system tray. If the client crashes and your browser reports a proxy connection error, go to Windows Settings → Network & internet → Proxy and check whether manual proxy settings still point to a local port that's no longer listening. If you previously used a workplace proxy or an automatic configuration script, restore those settings rather than clearing everything. Finally, visit a site that normally connects directly to confirm your network still works after quitting.