Configuration November 4, 2026

How to Enable TUN Mode in Clash Verge Rev on Windows

Get apps that bypass the Windows system proxy working with Clash Verge Rev. This walkthrough covers the TUN toggle, permission checks, virtual adapter setup, and quick ways to confirm traffic is being routed correctly.

Docker Proxy GitHub Acceleration Advanced Config YAML

1. What TUN mode changes on Windows

If a browser works with Clash Verge Rev but a game launcher, command-line tool, desktop app, or background service does not, the gap may be Windows proxy support rather than the proxy profile itself. The Windows system proxy is a setting that applications can choose to honor. Browsers and many desktop apps do; other programs open network connections directly and never consult that setting. Switching on the system proxy therefore does not guarantee that every app will use Clash.

TUN mode addresses that gap by having Mihomo create a virtual network interface and route selected traffic through it. Instead of asking each application to understand proxy settings, Windows can send network packets to the interface, where Mihomo applies the rules in your active profile. Depending on the profile and TUN settings, traffic can then go through a proxy node or use a DIRECT rule. TUN is useful for apps that ignore the system proxy, but it does not mean every connection must use a remote proxy.

It helps to separate three things that are often treated as one switch: the system proxy, the TUN interface, and the rules in your Mihomo configuration. The system proxy serves applications that support Windows proxy settings. TUN captures traffic at the network level, subject to its routing and exclusion settings. The rules decide what Mihomo does with captured connections. If the profile sends a destination to DIRECT, enabling TUN will not make that destination use a proxy node.

This walkthrough is for Windows 10 or Windows 11 users who already have Clash Verge Rev installed and have a working profile. It covers the settings to check, how to enable TUN, how to verify that traffic is being captured, and how to narrow down common failures. Interface names and available options can differ between Clash Verge Rev releases and Mihomo builds, so use the controls available in your installed version rather than assuming every screenshot or guide describes the same release.

TUN changes how network traffic is routed, so make one change at a time and keep a way to reverse it. If this is a managed work or school computer, check local network policy before enabling a virtual adapter or changing routing behavior. Do not use TUN to bypass organizational controls or to send sensitive traffic through a relay that your organization has not approved.

2. Check the profile, permissions, and other network tools

Start with a baseline. Open Clash Verge Rev, select the profile you intend to use, and confirm that it loads without errors. If the profile has a connection or proxy test, use it to check that at least one node is reachable. Then test an ordinary website with the system proxy in the state you normally use. Record what works and what does not. This gives you a useful comparison after TUN is enabled; otherwise, a profile problem can look like a TUN problem.

Next, look for a TUN or service control in the application’s settings. Depending on the build, the TUN switch may depend on a separately installed service or elevated permissions. If Clash Verge Rev offers an option to install or manage its service, follow the application’s own prompt. Windows may display a User Account Control dialog: read the publisher and requested action, and approve it only when you trust the application and intended to make the change. Do not repeatedly relaunch the app as administrator as a substitute for understanding why its service is unavailable.

Close or temporarily disable other tools that install virtual network adapters or alter routes, such as a second VPN client, another proxy client’s TUN mode, or a corporate network agent if your policy permits doing so. Two routing tools can compete for the same traffic or install conflicting routes. Also note whether you use virtualization software, a custom firewall, or endpoint security that controls network adapters. These tools can affect the outcome even when the Clash profile is correct.

Check the profile’s rule behavior before expecting a particular destination to appear proxied. If its rules select DIRECT for a destination, that is the expected result. If you manage the configuration, review the relevant rule and policy group; if you use a subscription, avoid editing generated configuration unless you know how your client handles updates. A profile refresh may replace manual edits. When in doubt, use a controlled test destination whose routing behavior you understand rather than changing broad rules to force all traffic through a node.

Finally, save your current state in a way you can restore. Note whether the system proxy was on or off, which profile was active, and whether another VPN or adapter was enabled. If you have recently changed DNS, firewall, or adapter settings, record those too. A short checklist makes it much easier to distinguish a new TUN issue from a pre-existing Windows network problem.

3. Enable TUN mode in Clash Verge Rev

With the profile loaded and other routing tools accounted for, open Clash Verge Rev’s settings and locate its TUN controls. The exact layout changes across versions, but look for a TUN section or a mode switch associated with the Mihomo core. If the application provides a separate service control, install or start that service using the app’s instructions before enabling TUN. A TUN switch that appears active in the interface is not, by itself, proof that Windows accepted the virtual adapter or that routes were installed.

Enable TUN and accept any Windows permission prompt that corresponds to the action you initiated. Give the application a moment to start the service and create the adapter. If the app reports an error, copy the exact message before making more changes. Common clues include a service that is not installed or running, insufficient permissions, a driver or adapter creation failure, or a conflict with another network tool. Restarting the app may help after a service installation, but repeatedly toggling the switch without checking the reported error usually obscures the cause.

If your build exposes stack or routing options, keep the defaults unless you have a specific reason to change them. Mihomo builds may offer different TUN stacks and options for automatic route setup, interface detection, or strict routing. These affect how packets and routes are handled; they are not universal performance switches. A stack that works well on one Windows setup may behave differently with a particular firewall, virtual machine, or network adapter. Change one option at a time, then test the same applications and destinations.

DNS is another part of the path. A profile may configure DNS handling or DNS hijacking for TUN traffic, and the names resolved by Windows may affect whether a connection matches the rules you expect. Do not add duplicate DNS or TUN configuration just because you found an example YAML file online. Clash Verge Rev may generate or manage parts of the Mihomo configuration itself, and conflicting settings can prevent the core from starting or make behavior difficult to diagnose. Prefer the client’s interface and documentation for your installed version.

After enabling TUN, check both the app’s status and Windows. If Clash Verge Rev indicates that the core or TUN service failed, resolve that error before testing applications. In Windows, open the network adapter list or Device Manager and look for a newly created virtual adapter. The displayed name varies by release and driver, so do not rely on one exact label. If no adapter appears, or Windows reports a disabled or failed device, the problem is likely earlier in the setup than the profile’s routing rules.

Keep the system proxy setting separate from this test. Some users leave it enabled so proxy-aware applications continue to use Clash, while TUN covers applications that do not read that setting. Others turn it off because they want to test TUN alone. Either can be appropriate. Make a deliberate choice and record it; changing both the system proxy and TUN at once makes it harder to identify which mechanism is responsible for a result.

4. Verify that Windows traffic reaches the proxy

Use a small, repeatable test rather than judging TUN by whether one app opens. First confirm that Clash Verge Rev shows the core running and that the selected profile has a usable node. Then open the app’s connections or traffic view, if available, and generate a new connection from a program that normally ignores the Windows proxy. Look for a connection entry that appears at the time of the test. Its process, destination, rule, and selected policy can help explain what happened. Existing long-lived connections may not be re-routed immediately, so close and reopen the test application.

For a command-line check, run a request from a terminal while watching the Clash connection view. For example, you can use a web request utility already installed on your machine to reach a destination you are authorized to test. The important evidence is not merely that the request succeeds: compare the observed connection and policy with the route you expected. A successful request marked DIRECT confirms reachability, but it does not show that the destination used a proxy node. Conversely, an error may be caused by DNS, the destination, a firewall, or the profile rather than by TUN itself.

You can also compare the reported public IP from a browser or a command-line request with TUN disabled and enabled, but interpret that comparison carefully. A profile can intentionally send some destinations direct, and IP-check sites can use different hostnames, address families, or cached connections. Choose a destination that your rules are intended to proxy, open a fresh session, and verify the matching connection in Clash. The connection log provides more useful context than an IP result alone.

If you want to confirm Windows has an active adapter or route, use the built-in network settings or PowerShell for inspection. For example, Get-NetAdapter lists adapters and their status, while Get-NetRoute can show routes currently known to Windows. These commands are diagnostic, not repair commands: do not delete routes or change interface metrics simply because an unfamiliar entry appears. A route can be required by Windows, a VPN, virtualization software, or the TUN service. If the output is unclear, save it and compare it with the state after disabling TUN normally.

Test more than one kind of application. Try a browser, the app that originally failed, and—if relevant—a command-line tool or launcher. Confirm whether each connection appears in Clash and whether its rule and policy match your expectation. Some applications use cached DNS results, reuse existing sockets, or launch background processes that survive after the main window closes. Fully exit and reopen the application before deciding that TUN did not capture it.

A useful verification record is brief: note the time, application, destination, whether the connection appeared in Clash, the matched rule, and whether it was proxied or direct. This turns “it feels broken” into a specific question. For example, a connection that appears but matches an unexpected rule points toward profile order or policy selection; a connection that never appears points toward capture, service, or application behavior. That distinction makes the next troubleshooting step much more targeted.

5. Troubleshoot safely and restore normal routing

If TUN will not start, check the application’s error message first, then verify whether its required service is installed and running. Confirm that Windows has not blocked the requested operation and that the virtual adapter is present and enabled. Restart Clash Verge Rev after a service change if the app asks you to. If another VPN or TUN-based tool is active, disable it temporarily only when permitted, then retry a single test. Avoid changing several driver, firewall, DNS, and route settings at the same time; each change removes a useful clue.

If TUN starts but no test traffic appears in Clash, verify that you are testing a new connection from an application that would otherwise ignore the system proxy. Check the TUN status, the selected profile, and any routing exclusions or interface settings exposed by your build. A destination excluded from capture, an application using an unusual network path, or a still-open socket can all produce misleading results. Close the application completely, reopen it, and repeat the test with a fresh connection.

If connections appear but use the wrong route, inspect the matched rule and selected policy in the connection view. Rule order matters: an earlier rule may match before the rule you expected. Check whether the policy group has selected a node or a direct option, and whether the profile’s DNS behavior is consistent with the destination you are testing. For a subscription profile, check its provider documentation or use its supported overrides instead of editing generated rules that may be overwritten on the next update.

If Windows loses connectivity, turn TUN off through Clash Verge Rev and wait for the application to release its routes and adapter state. Restore the system proxy to the state you recorded before testing, and temporarily disconnect other proxy or VPN tools that could now be competing. If the connection does not recover, restart the app and then Windows before attempting manual route or adapter repairs. Do not remove a virtual adapter or delete routes while the service is still active unless the application’s recovery instructions explicitly tell you to do so.

For persistent problems, collect the Clash Verge Rev version, Mihomo core version if shown, Windows version, the exact error, whether the adapter appeared, and a short connection-log example with sensitive details removed. Do not post subscription URLs, authentication tokens, private server addresses, or a full configuration file in a public forum. These details make it easier for support or a network administrator to identify a driver, permission, or rule issue without exposing your credentials.

Compared with a basic system-proxy toggle, which can leave command-line utilities and other non-proxy-aware applications untouched, TUN can provide a broader capture path while retaining Mihomo’s per-rule choices. Some all-in-one VPN clients make that path simpler but offer fewer visible controls for inspecting which rule handled a connection. If you want Windows applications to follow a configurable Clash profile rather than relying only on each app’s proxy support, download Clash clients and use the checks above to verify your setup.

Ready to get started?

Choose a compatible client, load your profile, and follow the Windows TUN checks to confirm how your apps are routed.