Configuration October 24, 2026

How to Enable TUN Mode in Clash Verge Rev on Windows

Set up TUN mode in Clash Verge Rev on Windows with clear steps for permissions, the virtual network adapter, and in-app options. Learn how to confirm that traffic is routed through Clash, troubleshoot a TUN startup failure or VPN conflict, and revert the changes if your connection stops working.

Docker Proxy GitHub Acceleration Advanced Config YAML

1. What TUN mode does—and when to use it

If Clash Verge Rev is already handling browser traffic but a terminal, game launcher, desktop application, or background service still connects directly, the gap may be that the application does not use the Windows system proxy. A conventional proxy setting is cooperative: an application must read the proxy configuration or be configured to use a proxy explicitly. TUN mode adds a virtual network interface and lets Mihomo capture and route IP traffic at a lower level, so more applications can follow the rules in your active Clash profile without each one needing its own proxy setting.

That wider coverage is useful, but it is not a magic “VPN” switch. TUN mode does not create a proxy node, make an unavailable server reachable, or guarantee that every program will behave correctly. The profile still decides whether a connection goes through a proxy group, uses DIRECT, or matches another rule. DNS settings, routing rules, Windows firewall policy, and other VPN software can all affect the result. A website that fails in TUN mode may therefore point to a DNS or rule issue rather than a broken virtual adapter.

This guide covers the Windows setup in Clash Verge Rev: preparing permissions, enabling the service or other required elevated operation, turning on TUN mode, checking that traffic is captured, and safely backing out if connectivity becomes unreliable. Menu labels can differ slightly among releases, and some builds expose service installation separately from the TUN switch. Use the labels shown in your installed version rather than assuming every release has an identical layout.

Before changing anything, save your current profile and note how you normally connect. If this is a managed work or school computer, check the administrator’s network policy first. TUN mode changes system-level network behavior; it can be inappropriate on a device that requires a corporate VPN, endpoint security agent, or organization-managed DNS configuration.

2. Check Windows, the profile, and permissions first

Start with a baseline while Clash is not using TUN. Confirm that the active profile loads, that a proxy group has a usable node selected, and that a browser can reach a site you normally use. This gives you a meaningful comparison if enabling the virtual interface changes DNS or routing. If the existing profile already fails in ordinary system-proxy mode, fix that first: TUN adds another layer to troubleshoot and will not repair an invalid subscription, an expired node, or a rule set that sends the destination somewhere unexpected.

Update Clash Verge Rev only from a source you trust, then open its settings and look for the controls related to Service Mode, system service, or TUN. Depending on the build, the service may need to be installed or started before the application can create or manage the virtual adapter. Windows will normally show an elevation prompt when a privileged operation is required. Approve it only when you intentionally initiated the action and the publisher and application are the ones you expect.

If the interface reports that service mode is not installed, use the application’s own install or enable control, then accept the Windows UAC prompt. If it reports that the service is stopped, start it from the same settings page if that option is available. Some versions require restarting Clash Verge Rev after installing the service. Avoid repeatedly clicking a disabled or failing control; first note the exact error, close the application, and reopen it with the appropriate permissions if the application documentation for your release recommends that procedure.

A normal user account can often run the client day to day after the required service has been installed, but the initial setup may require an administrator account. If you do not have administrator rights, do not try to bypass Windows controls or install a driver manually from an unrelated download. Ask the device administrator to approve the supported service or use a non-TUN proxy mode that is permitted on the device.

Also check for other network-capture tools before enabling TUN. Another VPN, a second proxy client with a virtual adapter, security software that filters network traffic, or a virtualization product can compete for routes or DNS. You do not necessarily need to uninstall these tools, but you should know which one is active and avoid starting multiple full-tunnel services at once during your first test. On a laptop that regularly connects to a company VPN, plan to test only when you understand the organization’s rules and can restore the original connection.

3. Enable TUN mode in Clash Verge Rev

Once the profile works in ordinary proxy mode and any required service is ready, enable TUN in the application. In many Clash Verge Rev builds, the control is in the settings area under a section named System or TUN Mode. Turn on the TUN option, apply the change, and allow Windows to approve any prompt that appears. If the client asks you to restart the core, restart it through the application rather than terminating random background processes.

  1. Select the intended profile. Verify the profile name and confirm it is the one you tested. A profile can contain its own TUN, DNS, or route settings, so the behavior may not be identical across profiles.
  2. Check the service state. If the client shows that its service is unavailable, resolve that state before interpreting a TUN startup error. Do not assume the toggle succeeded merely because it changed position.
  3. Enable TUN and apply the change. Watch the client’s status and logs for a successful start, an adapter error, or a permission message. If the application reports failure, record the message before trying again.
  4. Confirm the active mode. Return to the main screen and check that the TUN control or status indicator remains enabled. If it switches itself off, the core may have rejected the configuration or failed to create the interface.
  5. Test one application at a time. Begin with a browser, then test the specific application that previously ignored the system proxy. This separates general connectivity problems from software-specific routing or DNS behavior.

Do not edit the profile just to make the user interface toggle work unless the logs or profile indicate that configuration is the problem. Mihomo versions and profiles can use different TUN options; a copied YAML block may include obsolete fields or values that conflict with the bundled core. If you maintain your own configuration, make a backup and change one relevant option at a time. If the profile is subscription-managed, avoid modifying generated configuration files that may be overwritten during the next update.

For an initial test, keep the configuration simple. Use a known working proxy group and a small number of applications, and avoid changing DNS strategy, rule providers, and routing mode at the same time. If the test fails after several simultaneous edits, it becomes difficult to tell whether the cause was adapter creation, DNS resolution, a profile rule, or the selected proxy. A controlled change is easier to reverse and produces more useful log evidence.

4. Verify the virtual adapter and traffic path

A successful toggle is only the first check. In Windows, open Settings → Network & internet → Advanced network settings, or run ipconfig in Command Prompt, and look for a virtual adapter associated with the TUN driver. The exact adapter name depends on the build and driver. Its presence is useful evidence that an interface was created, but it does not prove that every connection is being captured or that the profile selected the route you intended.

Next, open Clash Verge Rev’s connection list or logs and generate a fresh request from the application you want to test. Look for a new connection entry and inspect its destination, matched rule, and selected policy or proxy group. The important question is not simply whether the connection appears, but whether it follows the intended decision. A matching DIRECT rule may be correct for a local service; a proxy rule may be expected for an application you deliberately routed through a relay. Do not infer success from a single public IP-check page alone.

Use a repeatable test. With TUN disabled, note whether the target application fails or bypasses the system proxy. Enable TUN, restart that application so it opens new connections, and repeat the same action. Some programs keep connections alive for a long time; an already-open socket may continue using its original path until the application reconnects. A browser refresh may not be enough if it reuses a background connection, so fully close and reopen the application when testing.

For command-line checks, compare DNS resolution and connectivity rather than treating one command as a complete diagnosis. For example, you can inspect the adapter list and routing table with Windows tools:

ipconfig /all
route print
Get-NetAdapter

Run Get-NetAdapter in PowerShell. The output may include disconnected physical interfaces or unrelated virtual adapters, so identify the TUN interface by its name and status rather than assuming the newest item is the correct one. route print can help reveal whether Windows has routes associated with the virtual interface, but route output is technical and must be interpreted alongside the client’s logs and the actual application test.

If the browser works but a particular program still connects directly, check whether that program uses a separate network stack, has its own proxy setting, or maintains persistent connections. Confirm that the corresponding traffic appears in the Clash connection list and inspect the matched rule. If there is no entry, investigate whether TUN started correctly and whether Windows or another network filter is intercepting traffic. If an entry appears with an unexpected policy, review rule order and the selected group rather than changing the adapter first.

DNS deserves separate attention. A page may resolve successfully but connect through an unexpected route, or the application may fail before a connection reaches the proxy because its resolver uses a different path. Compare a hostname-based request with a known IP-level test only when you understand the security and certificate implications; connecting directly to an IP is not a valid substitute for normal HTTPS verification. In the Clash logs, check whether DNS requests and subsequent connections correspond to the same test, and avoid sharing logs publicly if they contain hostnames or other sensitive details.

5. Troubleshoot failures and restore normal networking

When TUN will not start, begin with the simplest causes: the service is not installed or running, the application lacks permission for the requested operation, a required driver is unavailable, or another VPN or filtering tool has claimed a conflicting route. Read the exact error shown by Clash Verge Rev and its core logs. A generic “failed” message is less useful than the first concrete error near the time you enabled TUN. Restarting Windows may clear a stale adapter state, but it should not be the first response to an unknown profile error or a blocked service installation.

If the interface starts but internet access stops, disable TUN from the Clash Verge Rev settings and wait for the application to restore the previous routing state. Then check whether ordinary Windows connectivity returns. If it does, enable TUN again only after confirming that the profile, service, and selected proxy are healthy. If access does not return, turn off Clash’s system proxy as well if it was enabled, disconnect any competing VPN in the normal supported way, and inspect Windows network settings for a stale proxy or route. Avoid deleting adapters or resetting all network settings as an early fix; those steps can disrupt other applications and make the original cause harder to identify.

A VPN conflict often appears as intermittent access, a connection that works only when one tool is disabled, or a route that changes after the system resumes from sleep. Test with only one network-capture product active, following your organization’s policy. If you must use a corporate VPN, ask its administrator whether Clash TUN is supported and which client should own the default route. Do not attempt to defeat a required security tunnel by changing route priorities or disabling endpoint protection.

For a clean rollback, switch off TUN in Clash Verge Rev, stop the core, and verify that the TUN status is no longer active. If you enabled a service specifically for this test and no longer need it, remove or disable it using the client’s supported service controls; do not manually delete Windows service entries or driver files. Restore the proxy setting you recorded before testing, reconnect your usual VPN if appropriate, and test a normal website plus one local or work resource. A reboot is reasonable if Windows still shows a stale interface or the route table did not recover, but verify connectivity afterward rather than assuming a restart fixed it.

Keep a short troubleshooting record: Clash Verge Rev version, Windows version, profile name, whether service mode was active, the exact error, and which VPN or security tools were running. Redact subscription URLs, credentials, private hostnames, and personal data before sharing logs with support. This record makes it easier to tell a reproducible driver issue from a profile-specific rule or an environment conflict, and it prevents repeated trial-and-error changes that leave the machine in an uncertain state.

Some one-click VPN clients are simpler for a single browser session, but they can offer fewer controls when one application should use a proxy while another stays direct, and they may not capture programs that ignore system proxy settings. Clash Verge Rev adds profile-based routing and Mihomo connection visibility, while TUN extends that routing to more Windows applications; the trade-off is that service permissions, DNS, and competing adapters need deliberate checks. If that balance fits your setup, you can choose a Windows client and follow the relevant setup guide below.

Download Clash clients →

Ready to get started?

Choose a compatible client, then review the setup steps before enabling system-level routing on Windows.