1. What TUN mode changes on Windows
If Clash Verge Rev can proxy a browser but misses traffic from a terminal, game launcher, update service, or desktop application, TUN mode may be the missing piece. A conventional system proxy asks each application to respect Windows’ proxy settings. Some applications do; others use their own networking stack, ignore proxy variables, or open connections before the system proxy is enabled. TUN mode takes a different route: Mihomo creates a virtual network interface and, when routing is configured successfully, Windows sends selected traffic through that interface for Clash to process.
This does not mean every connection is automatically sent to a proxy node. TUN captures traffic; your active profile’s rules and the selected policy groups still determine whether a connection uses a proxy, goes directly, or is rejected. It also does not make an unreliable node faster. The practical benefit is broader coverage for applications that do not cooperate with the normal Windows proxy setting, while retaining the rule-based routing and connection controls in your Clash profile.
On Windows, TUN setup often depends on more than a switch in the main window. Clash Verge Rev may need to install or start its Service Mode component with elevated privileges so the Mihomo core can create the virtual adapter and adjust routes. The exact setting names and prompts can vary between releases. If a control is missing or disabled, first check the application version and service status rather than repeatedly clicking the switch or editing unrelated profile fields.
Before changing anything, save your current profile or note how to restore your normal Windows network settings. If the computer is managed by an employer or school, confirm that virtual adapters and route changes are permitted. Do not try to defeat endpoint security or organizational VPN requirements. TUN mode is a network configuration feature, and another VPN, firewall, or device policy can intentionally restrict it.
2. Check Service Mode, permissions, and existing network software
Start with Clash Verge Rev closed or in a stable, idle state, and make sure the profile you intend to use is already selected. Open the application’s settings and look for the service or core-service section. In builds that expose a Service Mode installation control, install or enable the service and approve the Windows User Account Control prompt only when it clearly comes from Clash Verge Rev. Then check that the interface reports the service as installed or running. Labels differ between builds, so use the status shown by your version rather than relying on a button name from an older screenshot.
Service Mode is relevant because a normal desktop process does not always have the permissions needed to create a TUN interface or adjust system routes. If the service is missing, stopped, or unable to communicate with the core, the TUN option may be unavailable or appear to turn on without capturing traffic. Running the entire client as administrator can be useful as a short diagnostic, but it is not a substitute for a correctly installed service. Close the client afterwards and return to the normal launch method; avoid leaving every application elevated as a permanent workaround.
Before enabling TUN, note any other software that can install a virtual adapter or change routes. Examples include a corporate VPN, another personal VPN, virtualization tools, endpoint security clients, packet-capture drivers, and older proxy clients. You do not necessarily need to uninstall them. Instead, record which one is connected, and test Clash with only one network-tunneling product active where your organization’s policy permits. Two tools can compete to become the default route, install overlapping DNS filters, or apply firewall rules that make the result look like a Clash failure.
Also inspect the Windows network state before the change. Open PowerShell and run Get-NetAdapter to list active and disconnected adapters. You can use ipconfig /all to record the current addresses and DNS servers, and route print to review the route table. These commands are for observation; do not delete adapters or remove routes simply because their names look unfamiliar. A virtual adapter may be created only after TUN starts, and its name may be generated by the core or driver rather than matching the client’s branding.
- Confirm the selected Mihomo profile loads without a parse or update error.
- Check that Service Mode is installed and running if your build provides it.
- Save the current state of any work, school, or other VPN connection before testing.
- Keep a way to reopen Clash Verge Rev and turn TUN off if connectivity changes.
3. Enable TUN and verify the virtual adapter
Open the TUN settings in Clash Verge Rev and enable the feature. Depending on the release, the controls may be grouped under general settings, network settings, or a service-related panel. If the application asks to install a driver, create a service, or approve a network change, read the prompt and verify its publisher before accepting. Once enabled, give the core time to start and check for an explicit running or healthy status. A highlighted switch alone is not conclusive: the core can still fail to initialize the adapter or apply routes.
Many builds expose options such as a network stack, automatic route management, interface detection, or strict routing. Keep the defaults for the first test unless you have a specific reason to change them. Automatic route management is generally intended to direct captured traffic through the TUN interface; interface detection helps the core choose the active physical network adapter. Strict-routing behavior can affect how traffic that does not match expected routes is handled, so changing it may alter connectivity beyond the application you are trying to test. Treat these as network controls, not as performance sliders.
If your build supports editing the profile’s Mihomo configuration directly, a minimal TUN section may look like this:
tun:
enable: true
stack: mixed
auto-route: true
auto-detect-interface: true
dns-hijack:
- any:53
This example is not a universal replacement for the application’s own TUN controls. A Clash Verge Rev version may manage some settings through its interface, and a profile may already include a TUN block or DNS behavior. Do not create duplicate keys or paste the example into a subscription that is regenerated and overwrites local edits. If you do edit YAML, make a backup, keep indentation consistent, reload the profile, and inspect the core log for parsing errors. Follow the options supported by the Mihomo version bundled with your client.
After TUN reports that it is active, use Get-NetAdapter again and look for a newly present or newly active virtual interface. Then run route print and compare it with the baseline you recorded. The exact route entries depend on your profile, Windows version, and network, so do not expect one fixed address or interface name. What matters is that the adapter is operational and the client has not left the machine with an obviously broken default route.
Now test a small number of different applications rather than assuming that a successful browser page proves everything. Open a site in your usual browser, try a command-line request such as curl -I https://example.com, and check the Clash connection view or logs for the corresponding connections. The command tests whether a request completes; the Clash connection record helps confirm whether the request was actually captured and which rule or policy handled it. A browser working through the ordinary system proxy before TUN was enabled is not, by itself, evidence that TUN is functioning.
4. Understand DNS, routes, and profile behavior
DNS is a frequent source of confusing results. A page may fail to load even though the TUN interface exists because Windows, the active profile, and the core are not using the DNS path you expect. Conversely, a cached DNS answer may make one site appear healthy while new connections fail. If only domain names fail but a known reachable IP-based test behaves differently, inspect the profile’s DNS configuration and the Mihomo logs before changing Windows adapter DNS settings. Avoid copying DNS addresses from an unrelated tutorial: a value appropriate for one network can break another.
The profile still decides the route for captured traffic. A rule near the top of the rule list may send a domain to DIRECT, while a later rule sends another connection to a proxy group. TUN does not override that policy. When one application works and another does not, check the connection log for the exact destination, the matched rule, and the selected policy. This is more useful than changing the whole profile to a catch-all proxy rule, which can send local services, corporate resources, or nearby devices through a route that was never intended for them.
Pay attention to local network access as well. Printers, file shares, development servers, smart devices, and internal portals may depend on routes to private address ranges or local DNS names. Some profiles include rules for private networks; others do not, and custom rules may take precedence. If a local resource stops working after TUN is enabled, first check whether its connection is being captured and which rule handles it. Add or adjust a narrow, understood rule only if the profile’s design calls for that change. Do not disable all routing protections just to make one local address reachable.
Keep a simple before-and-after record: whether the client’s system proxy is on, whether TUN is active, which profile is selected, and which test application succeeds. This helps distinguish three separate mechanisms. The Windows system proxy can serve applications that honor it; TUN can capture eligible IP traffic through a virtual interface; profile rules decide how Mihomo handles the captured connection. Testing these mechanisms separately prevents a common false diagnosis in which a working proxy setting is mistaken for a working TUN route, or a profile rule is blamed for a driver that never started.
5. Troubleshoot a disabled switch, lost connectivity, or VPN conflict
If the TUN switch is disabled or immediately turns itself off, check the service status and core logs first. A missing service, a failed elevation prompt, a stopped core, or a profile validation error can prevent initialization. Restart Clash Verge Rev normally after correcting the service state. If an update has changed the available controls, consult the documentation for that specific release instead of combining instructions for different forks or versions. A clean, valid profile is a better diagnostic starting point than a configuration containing several experimental TUN, DNS, and routing overrides.
If the switch stays on but no virtual adapter appears, verify that the bundled TUN driver is available and that Windows security software has not blocked its installation or startup. Check Device Manager for an adapter or driver warning, but do not manually remove a device unless you know it belongs to this client and understand the impact. Rebooting may be necessary after a driver or service installation. If the driver still fails, capture the relevant Clash core log and Windows error details; repeated reinstalls without identifying the failure can leave stale services or adapters behind.
If connectivity disappears immediately after activation, turn TUN off from Clash Verge Rev and wait for routes to restore. If you cannot reach the client normally, disconnect from the current test network only when safe, then reopen the application and disable TUN. Check the active profile, selected policy group, core status, route table, and DNS behavior before trying again. Avoid running broad commands that reset every Windows network component as an early fix; they can erase working VPN, Wi-Fi, or enterprise configuration while leaving the original cause untouched.
For a VPN conflict, test one tunnel at a time where permitted. Some VPNs intentionally block other virtual adapters or install routes that take precedence over Clash. If the other VPN is required by your employer, do not bypass its controls; ask the administrator whether concurrent tunneling is supported. When personal VPN software is involved, compare behavior with it disconnected, then reconnect it and check which adapter owns the default route. If TUN works alone but not alongside the VPN, that points to route or policy interaction rather than a general failure of the Clash profile.
If only one application is affected, use Clash’s connection log to see whether its traffic appears. If it does not, the application may use a separate network boundary, a protected service, or a route not covered by the current TUN setup. If it appears but fails, inspect the matched rule and DNS result, then test a different policy group without changing unrelated settings. Retest after each change and record what changed. A controlled one-variable-at-a-time process is faster to reverse and more informative than toggling TUN, DNS, system proxy, and several profile rules together.
Compared with basic proxy toggles that depend on every application honoring Windows settings, TUN can provide broader coverage through a virtual adapter, while Clash’s connection view and profile rules make it possible to inspect and direct traffic instead of treating the entire computer as one undifferentiated tunnel. Other VPN clients may be simpler for a single, all-or-nothing connection, but offer fewer rule-level controls for mixed local, direct, and proxied traffic. If you want to compare compatible clients for your Windows setup, view the downloads.
Ready to get started?
Choose a compatible client, then follow the setup guide to configure your Windows proxy and TUN options.
Find a compatible client and learn how to configure Windows TUN mode and proxy routing.
Free Download