Choose the Right Windows Installer: Check Your System Architecture and Core
On Windows 11, open Settings → System → About and check System type. If it shows an x64-based processor and a 64-bit operating system, choose the Windows package labeled x64 or amd64. The latter also works on compatible Intel PCs. If it shows an ARM-based processor, choose the client’s arm64 package when available. If you plan to use TUN, also make sure the client’s service or driver supports your architecture—a successful launch alone doesn’t confirm compatibility.
- GUI client: Choose a client with a graphical interface to import subscriptions, switch proxy groups, and view connections. A standalone core executable doesn’t include these features.
- Installer or portable version: If both are available, install the installer version according to the release instructions. For the portable version, extract all files to a writable folder before launching it. Don’t run the app from the archive preview.
- Core compatibility: Clash Meta is now called Mihomo. If your subscription provider specifies Mihomo, check which core the client actually includes. A client with Clash in its name won’t necessarily support every Mihomo field. On Windows 10, also check whether the client version still supports it.
Before installing, back up your existing client’s configuration and quit any older instance still running in the system tray. Closing its window may leave it running in the background. Two instances can compete for the same local listening port or repeatedly overwrite the Windows system proxy settings.
First Import: Validate the Configuration Before Enabling the System Proxy
- Import the Clash or Mihomo subscription link from your service provider on the client’s Configuration or Subscription page. You can also import an existing local YAML file. Button names vary by client. After importing, select the configuration and make sure it’s applied—not just listed.
- Leave TUN and the system proxy off for now. Check the logs to confirm the core has started, then make sure the proxy groups show available options. If the configuration downloads but fails to apply, start by checking the field name and line number in the logs. That’s a separate issue from nodes failing to connect.
- Select rule mode, then turn on the client’s System Proxy switch. In Windows, go to Settings → Network & internet → Proxy and check the address and port. With manual proxy settings, you’ll usually see a loopback address and a local HTTP or mixed-protocol port. If the client uses PAC, check the automatic configuration script instead; don’t also enter a separate proxy address manually.
- Visit a site you normally use, then check the client’s connection list to see which rule matched and which outbound route was used. In rule mode, a
DIRECTmatch means the core connected directly for that traffic; it doesn’t mean the proxy entry isn’t working.
Use Local Ports to Isolate the Problem
Suppose the client shows 7890 as its mixed port. Run these two commands in PowerShell. If the client shows a different port, replace it in both commands. The second command uses HTTP proxying, so enter an HTTP or mixed port—not a SOCKS-only port.
Test-NetConnection -ComputerName 127.0.0.1 -Port 7890
curl.exe --max-time 15 --proxy http://127.0.0.1:7890 -I https://example.com/
A TcpTestSucceeded : True result from the first command only means something is accepting connections at that address and port; it doesn’t prove that the listener is Clash. The second command explicitly uses the proxy, bypassing the question of whether an app reads the system proxy settings. If you get a response from the target site and the client logs the request, the local proxy path is working. Check the connection’s outbound route to confirm whether it went through a proxy node. If explicit proxying works but your browser bypasses it, check the browser’s own proxy settings, extensions, or policies pushed by your organization.
UAC and Firewall: Handle Permissions and Inbound Access Separately
When to Approve a UAC Prompt
UAC is Windows’ prompt for elevating permissions. A client may need administrator rights to install a system service, add a virtual network adapter, or change system routes. You usually don’t need to run the interface as an administrator all the time just to use the current user’s system proxy. If the client offers a service mode, follow that version’s instructions to authorize service installation, then use the interface without admin rights while the service handles network operations that require elevation.
Before approving an elevation prompt, make sure the program requesting it matches the action you just started. On a work computer without administrator credentials, use an approved system proxy method or ask your administrator whether TUN is allowed. Don’t lower the UAC level just to stop the prompts.
Local Use Doesn’t Require an Inbound Firewall Rule
Apps connect to 127.0.0.1 over the local loopback interface. If you only need Clash on this PC, leave Allow LAN disabled. If Windows Firewall asks whether to allow network access, don’t allow access on every network just for troubleshooting. If your browser can’t connect, check the core status and port first; an inbound firewall rule won’t fix a core that isn’t listening.
Only check the client’s bind address, proxy port, and network profile if another device on your local network genuinely needs to use the proxy. On a network where sharing is permitted, go to Windows Security → Firewall & network protection → Advanced settings → Inbound Rules to limit access: open the required port only for the trusted Private profile, and restrict remote addresses to the devices or trusted subnet that need access. Don’t confuse the proxy listening port with the control interface, and don’t change a public Wi-Fi network to Private for this purpose.
Enable TUN: Turn Off the System Proxy First, Then Test the Target App
The system proxy only works when an app chooses to read and use those settings. TUN uses a virtual network adapter and routes to capture system traffic, making it useful for apps that ignore the system proxy. TUN sends traffic to the core; it doesn’t switch rule mode to global mode. The configuration still determines whether each connection goes direct or through a proxy.
- Keep a working baseline. First, use the local port test from the previous section to confirm the configuration works. Note your current proxy settings, especially any manual proxy or PAC provided by your organization, so you can restore them after testing.
- Enable one entry point at a time. Turn off the system proxy controlled by the client, then enable TUN. If prompted to install a service, follow the client’s instructions to authorize it, then check the status again. The client’s Auto Route option usually corresponds to Mihomo’s
tun.auto-route, which configures routes to send traffic through TUN. For your first test, use the client’s recommended settings and don’t change the network stack or DNS at the same time. - Check the adapter and connections. Press Win + R, run
ncpa.cpl, and check the network adapters. The adapter name depends on the client. Seeing the adapter is only the first step: reopen the target app to start a new connection, then check whether the client logs it and which outbound route it uses.
If your work VPN, internal domains, or shared drives stop working after you enable TUN, turn TUN off first and check whether they recover. The VPN and TUN may both change routes, and internal domains may rely on DNS provided by the VPN. Use route print to view routes and ipconfig /all to check adapters and DNS settings, then share the differences with your network administrator. Don’t switch to public DNS or delete organization-managed routes as a first step.
Startup Failures or No Internet After Exiting: Roll Back by Symptom
| Symptom | Check first | What to do |
|---|---|---|
| The log says the address is already in use | The listening port and the process using it | For the example port 7890, run Get-NetTCPConnection -LocalPort 7890 -State Listen and check OwningProcess. Then find the PID in Task Manager’s Details tab. Quit the process only if you confirm it’s an old client instance. If you change the port, update the proxy settings in the apps using it too. |
| The system proxy works, but TUN fails as soon as it’s enabled | Service status, core logs, and virtual adapter creation | Turn off TUN first and keep the working system proxy. Use the logs to identify whether the issue is insufficient permissions, a service that hasn’t started, or a failed adapter initialization. Don’t use a firewall exception as a substitute for authorizing the service. |
| Websites won’t load after exiting the client | Whether Windows still points to a local proxy | If Windows still points to a 127.0.0.1 port that’s no longer listening, turn off that manual proxy or restore your original proxy and PAC settings. Restart the browser and test again; there’s no need to reset the entire network first. |
If you only use a browser and apps that support the system proxy, you can stop here once the system proxy is working. If you need TUN, test the target app and your usual internal network separately. Before uninstalling, turn off TUN and the system proxy managed by the client, quit the tray app, and remove its service according to the client’s instructions. Finally, check that Windows proxy settings have returned to their original state.