Clash Mode Comparison

Before installing: check the build and download source

On Windows 11, choose the Clash Verge Rev installer that matches your device, install the app, and then import a valid configuration before testing traffic. Installing the desktop interface alone does not provide a proxy subscription or guarantee that a connection will work. The app manages settings and starts the mihomo core; your configuration supplies the proxies, rules, and policies used by that core.

First check whether Windows is running on an x64 or ARM64 device. Open Settings → System → About and look for “System type.” Most Intel- and AMD-based PCs use x64. Windows on an ARM device requires an ARM64-compatible build when one is offered. If the installer does not list an ARM64 option, check the current download information rather than assuming that an x64 package is the right choice for every ARM computer.

Use a download source you can identify and trust. Compare the application name and version shown on the download page with the installer file before opening it. Avoid repackaged installers, unsolicited download links, and files that ask you to enter a subscription token on an unrelated website. A subscription URL can contain account credentials; treat it like a password.

Install the app and complete the first launch

After downloading, open the installer from the folder where your browser saved it, usually Downloads. If Windows asks whether you want to allow the app to make changes, verify the app name and publisher before approving. An administrator prompt can be expected for some installation or service operations, but it is not a reason to approve an installer whose origin you cannot verify.

1. Close other proxy clients if they are actively changing Windows’ system proxy. You do not usually need to uninstall them just to install Clash Verge Rev, but running multiple clients that control the same settings can make later tests confusing.
2. Start the installer and follow its prompts. Keep the default installation location unless you have a specific reason to change it. If Windows Security blocks the file, stop and re-check the download source and file details rather than disabling security controls.
3. When setup finishes, launch Clash Verge Rev from the Start menu. If a Windows Firewall prompt appears, read which network types and app are named. Allowing access on a private network may be appropriate for the way you use the PC; do not enable broader access without a reason.
4. Wait for the main window and check that the interface finishes loading. If it requests a core download or update, use the app’s own available controls and note any error message. A visible window does not yet confirm that a configuration has been imported or that a proxy node is reachable.
5. Find the app’s settings or About area and record the app version and core information if shown. Menu names can change between releases, so use the visible labels in your installed version rather than following instructions written for a different Clash client.

Clash Verge Rev and the mihomo core are separate components. The interface can open while the core is missing, stopped, or unable to parse the active configuration. Conversely, a core problem does not always mean the whole application needs to be removed. Keep that distinction in mind if the window opens but the connection controls or logs report an error.

Understand permission prompts before enabling TUN

For a basic first test, leave TUN disabled and use the client’s system-proxy control if your configuration and Windows setup support it. TUN creates a virtual network interface to capture traffic that may not follow the Windows system proxy. It can require elevated permissions or a service, and it introduces additional variables such as adapter state, routes, and DNS handling. It is not required simply to install the client or test whether a proxy node can connect.

If a prompt refers to installing or starting a service, read the prompt and the app’s explanation. Do not repeatedly approve failed prompts without checking the log or current service status. You can return to TUN later after confirming that the configuration works through the simpler system-proxy path.

Import a configuration or subscription safely

For a beginner, importing a provider’s supported subscription is usually less error-prone than building a full YAML configuration manually. In Clash Verge Rev, open the profile or configuration area and choose the option to add or import a profile. The exact label varies by version. If you received a subscription URL, paste it only into the profile field in the app, give the profile a recognizable name, and save or confirm the import.

If you received a local YAML file instead, choose the app’s file-import option and select the file. Do not rename a random text file to .yaml and assume it is a valid profile: YAML indentation, required fields, and supported proxy types all matter. A subscription can download successfully yet still contain fields or node types that the active core does not support.

1. Confirm that you have the correct subscription or configuration for Clash or mihomo. If the provider supplies several formats, use the format they identify as compatible with your client.
2. Add the URL or file through the profile management screen. For a URL, check carefully for missing characters and avoid adding spaces before or after it.
3. Update the profile if the app offers an update action. Wait for the result and read any import or parsing error instead of repeatedly clicking the button.
4. Select the imported profile as the active configuration. A profile appearing in the list does not necessarily mean it is currently selected.
5. Open the proxy or connections view and check that proxy nodes and policy groups are populated. If the list is empty, investigate the profile import before changing Windows networking settings.

Select a usable policy before testing

After selecting the profile, open the proxy group or policy selector and choose a node or automatic selection group if one is available. A group may initially be set to a default option that is unavailable, or it may need time to load its choices. A node name is only a label; it does not prove that the server is online or that the configuration fields are correct.

Keep the operating mode in Rule for ordinary use unless you have a specific reason to change it. Rule mode sends connections according to the active rules and selected policy groups. Global mode is useful as a temporary comparison when troubleshooting, while Direct mode bypasses proxy routing for traffic handled by the core. None of these modes determines which device traffic is captured: that depends on the system proxy, TUN, or another capture method.

Enable the proxy and verify traffic in stages

Once the configuration is active and a usable policy is selected, enable the system proxy from the client’s main control or settings area. The wording and location can vary by release. Then test one browser request and inspect the client’s connections or logs. Change one setting at a time: if you enable the system proxy, switch modes, change nodes, and turn on TUN together, a failure becomes much harder to diagnose.

1. Check that Clash Verge Rev reports the core as running and that the active profile is the one you imported.
2. Confirm that the chosen node or policy group has a selection, then run a latency or connectivity test if the client provides one. A latency result is useful but does not guarantee that every website or protocol will work.
3. Enable the system proxy. Open a fresh browser tab and visit a site that should follow the selected policy. If the page does not load, check the connection list and logs for a matching request or error.
4. Turn the system proxy off when you finish testing if you do not want it active. Confirm that Windows proxy settings return to the state you expect, especially before starting another proxy client.

System proxy and TUN solve different capture problems. The system proxy asks compatible applications to send traffic through a local proxy endpoint. Some programs ignore that setting. TUN can capture more device traffic, but it may affect local-network access, DNS, or routes and needs its own troubleshooting. First establish a successful basic connection, then enable TUN only if your use case requires it.

Troubleshoot installation and startup problems

If the installer will not start, note the exact Windows message and check whether the file finished downloading. A browser may have saved an incomplete file, and Windows may block an installer from an unverified source. Re-download from a source you trust and compare the file details. Do not bypass a security warning merely because a download page says the file is safe.

If the app window disappears after launch, check the notification area near the clock; some clients can remain running in the tray. Also open Task Manager and see whether the application is still present. A hidden window, an app process that exits, and a running UI with a stopped core are different situations and call for different checks.

• Profile import fails: Check for a mistyped or expired subscription URL, a network error, or a configuration format unsupported by the active core. If the provider offers a refresh or replacement URL, obtain it through the provider’s normal account channel.
• The core reports a parse error: Keep the full error text and identify which profile was active. YAML indentation errors, unsupported fields, and incompatible node types can prevent startup. Do not delete the configuration before saving a copy.
• The app opens but no traffic is proxied: Confirm that the profile is selected, the core is running, the system proxy is enabled, and a policy has a usable selection. Then inspect whether a request appears in the connections list.
• Another client stops working: Check whether both apps are controlling Windows’ system proxy or trying to use the same local port. Exit one client normally and test again before editing ports or deleting settings.
• TUN fails to start: Check the app’s service or TUN status and the exact error in its logs. Close the client, restart Windows if a previous service operation is pending, and retry only after identifying the relevant permission or service issue.

Before reinstalling, save any configuration files you created and record the app version, core version, Windows version, and a timestamp for the failure. If the application offers an option to open its data directory or logs, use that rather than guessing a folder path from instructions for another release. Redact subscription URLs, credentials, and personal information before sharing diagnostics. Reinstalling the interface is unlikely to fix an expired subscription or a policy that selects an unavailable node.

When the basic setup is stable, you can review the wider range of supported clients and their platform options on the client download page. Keep your first troubleshooting pass simple: verify the installer, the active profile, the core status, the selected policy, and the traffic-capture method in that order.