Platform Guide 7 min read

How to Install and Set Up Clash on Windows: Admin Permissions, Firewall Rules, and System Tray Fixes

Choose the right installer, configure service mode and firewall access, and set Clash to start with Windows. Includes fixes for missing tray icons and port conflicts.

Choose the Installer for Your Windows System Type

This guide uses Windows 11 and Clash Verge Rev 2.x as examples. Open Windows Settings → System → About and find System type. If it says “x64-based processor,” choose the x64 package. For ARM devices, choose a package explicitly labeled ARM64 on the release page. Don’t rely on “64-bit operating system” alone; both architectures may show that. If you already have an older client, back up your configuration, turn off its system proxy, then quit it from the system tray before proceeding. This prevents two clients from changing system settings at the same time.

Get the installer from the project’s release page and follow the setup wizard. The installation scope, path, and organization policies can affect whether a UAC prompt appears, so its presence or absence doesn’t tell you whether installation succeeded. Launch the app with your usual Windows account. On a managed work PC, ask your administrator if policies block installation or service permissions; don’t bypass them by forcing changes to system policy.

Import Your Config and Verify the System Proxy

  1. Open Subscription from the client’s left sidebar. Import a subscription URL using the field at the top, or use the add option to import a local config file. Button labels may vary between minor releases. After importing, select the config; seeing a subscription card alone doesn’t mean it’s active. Subscription URLs may contain access tokens, so redact them before sharing screenshots or logs.
  2. Open Proxies, select Rule mode, then choose an available node in the proxy group used by your rules. With mode: rule, connections matched by DIRECT still connect directly. Some direct connections are expected; there’s no need to switch to Global mode right away.
  3. In the client, open Settings → System Settings and enable System Proxy. Leave TUN off for now. Then go to Windows Settings → Network & Internet → Proxy and check that the manual proxy address and port match the client. Reload a test page and check the target domain and outbound policy under Connections in the client. A page loading successfully only confirms that the request completed; connection logs help verify whether it went through the core.

A failed subscription import and a proxy connection problem require different troubleshooting steps. For an import failure, first check that the URL is reachable and returns a config the client supports. For a connection issue, check that the core is running and the proxy group has an available node selected. Terminal apps may not use the Windows system proxy, so don’t reinstall the client just because your browser works but a terminal app doesn’t.

How Admin Permissions, Service Mode, and TUN Work Together

The system proxy is a per-user setting, so the client usually doesn’t need to run as administrator all the time. Service mode lets a background service handle tasks that require elevated permissions. It’s separate from the outbound modes Rule, Global, and Direct. If you only use browsers that follow the system proxy, you can skip installing the service.

If you need to route traffic from apps that ignore the system proxy, open Settings → System Settings in Clash Verge Rev and find the Service Mode installation option. Check that the UAC prompt matches the action you just started, then approve it. Once the service is available, enable Virtual Network Interface. To confirm which routing path is in use, temporarily turn off the system proxy, send another test request, and check Connections. TUN routes traffic through a virtual network interface; actual coverage also depends on route exclusions, DNS settings, and other VPNs or virtual adapters.

Windows Firewall Rules: Distinguish Local Access from LAN Access

A browser connecting to a proxy on 127.0.0.1 doesn’t need an inbound port opened to the LAN. A Windows Security Alert doesn’t necessarily mean the proxy has failed. If you’re only using the proxy on this PC, keep allow-lan: false and don’t allow inbound access on public networks. If the client applies configuration overrides, check the runtime settings—not just the line in the subscription file.

Enable Allow LAN only if you specifically want other devices on the same trusted network to use the proxy. Open Windows Defender Firewall with Advanced Security using wf.msc. Under Inbound Rules, create a rule with a restricted scope for the actual listening port and protocol. For example, to let another PC use the HTTP proxy, limit the rule to TCP, the actual mixed port, the Private profile, and that device’s source address. Check for any existing allow rules with broader scopes, too. Don’t open access on public networks or expose the external-controller interface. When testing is complete or sharing is no longer needed, turn off LAN access and disable the associated rule.

Missing System Tray Icon and Startup Settings

Check Whether the Icon Is Hidden or the App Has Closed

Click the up arrow on the right side of the taskbar to view hidden icons. In Windows 11, adjust visibility under Settings → Personalization → Taskbar → Other system tray icons. Then press Ctrl+Shift+Esc to open Task Manager. If the app is running but its icon is missing, reopen the window from the Start menu. Seeing only the background service or core doesn’t confirm that the app’s tray icon is working. What happens when you click the window’s close button depends on the client settings; it’s not the same as choosing Exit from the tray menu.

Starting with Windows Doesn’t Mean the Proxy Is Enabled

In the client, open Settings → System Settings and enable Start with Windows. If the client registers as a Windows startup app, you can also check that it hasn’t been disabled in Task Manager under Startup apps. Sign out and back in, then check in order that the app launches, the config loads, and the system proxy or TUN is restored as expected. Starting the app when a user signs in and starting the background service are separate things. A running service doesn’t prove that the system proxy is set for the current user.

Port Conflicts: Find the PID Before Taking Action

If the logs show address already in use, note the port in the error message. The example below uses 7897 as a mixed port; this isn’t the default for every client. In PowerShell, check the TCP listener and its process:

Get-NetTCPConnection -LocalPort 7897 -State Listen -ErrorAction SilentlyContinue |
  Select-Object LocalAddress, LocalPort, OwningProcess

Get-Process -Id 1234

Replace 1234 with the OwningProcess value from the query. If it’s an older Clash client, quit it from the system tray and check whether the listener is gone. If the process still needs to run, change the mixed port in the new client—for example, to 7898 after confirming it’s available. Apply the config, toggle the system proxy off and back on, and make sure both Windows settings and any apps with a manually configured proxy use the new port. If the error refers to the controller port or a UDP listener, check the relevant field or use Get-NetUDPEndpoint; don’t just change mixed-port.

If your browser loses internet access after the client exits, check whether Windows still points to a local port that’s no longer listening. Remove only the manual proxy setting added by this configuration. Restore any proxy or automatic configuration script managed by your organization to its original settings.

Download Clash