Clash Verge Rev on Windows 11: Pick Nodes and Switch Policy Groups Step-by-Step (2026)

What this guide is (and is not)

This is a type-2 workflow tutorial for people who open Clash Verge Rev daily on Windows 11. It assumes your profile loads, outbound lists are visible, and you mainly need a repeatable method to measure delay, compare servers, and switch policy groups while working or streaming.

It is not a fresh install walkthrough. If you still need SmartScreen steps, subscription import, or the system proxy versus TUN decision, read Clash Verge Rev on Windows 11: first install first. Migrating from Clash for Windows? Our CFW → Verge Rev migration guide covers port parity and override habits that affect how groups appear after import.

For vocabulary that spans every client—rules, proxy-groups, subscriptions—keep the Clash tutorial open in another tab. Mac users looking for the same mental model in a menu-bar client should compare notes with ClashX Pro on macOS: latency tests and policy groups; the engine behavior is shared even when the GUI differs.

Clash Verge Rev labels shift between releases—Proxies, Outbounds, or localized Chinese group names from your provider. Screenshots age fast, so this guide describes capabilities—latency sweep, group expansion, selector clicks—rather than pixel coordinates. When your exact string differs, map it to the behavior: refresh delays, pick a member, climb nested groups.

Why latency tests exist in Clash Verge Rev

Subscription providers ship dozens of hostnames. Human-readable names like “Tokyo Lite” or “US-01” rarely encode real-world performance on your ISP path. A latency test asks the Mihomo core to open lightweight HTTP probes—commonly a 204 generator or vendor-specific URL—through each candidate and record round-trip time in milliseconds.

Those numbers help you pick a plausible default when you do not have a lab full of metrics. They do not guarantee streaming bitrate, game tick stability, or SSH comfort, because the probe host is not your game server or Netflix edge. Treat the readout as a ranking hint, not a promise.

If your profile author disabled tests or wrapped nodes in groups you cannot expand, the UI will not magically add tests—you inherit what the YAML allows. For how url-test, fallback, and nested structures behave under the hood, see the proxy-groups guide after you finish the click-path basics here.

Know your surfaces: dashboard versus Proxies panel

Clash Verge Rev on Windows 11 is dashboard-first rather than tray-first like macOS ClashX Pro. The home view summarizes proxy mode (Rule, Global, Direct), active profile, and sometimes the current outbound name. That summary is useful for a glance but incomplete for deep tuning.

The Proxies page in the sidebar is where daily node work happens. It mirrors the proxy-groups tree from your subscription: expandable selectors, nested pools, and leaf nodes with latency columns after a test. Beginners often hunt for a latency button on the dashboard; if you only see a single highlighted server, open Proxies and expand the group your rules actually reference.

The system tray icon may expose quick toggles—enable proxy, open the main window—but full group trees usually live in the main UI. If clicks do nothing, verify Clash Verge Rev runs elevated helpers when TUN is on, and that no other VPN client stole the routing table. When only Microsoft Store apps misbehave despite a green latency badge, revisit UWP loopback exemptions before you blame node choice.

Step-by-step: run a batch latency test

Exact labels vary by Verge Rev version, but the sequence is stable across Mihomo-backed clients on Windows:

1. Stabilize the session. Wait until your subscription finishes updating. If nodes flicker between empty and populated, fix fetch first—subscription link refresh guidance explains HTTP 429 and stale URLs better than random reimports.
2. Open Proxies and find the group you route through. Many Chinese templates expose 节点选择 (Node Select) or an English Proxy selector at the top. That is where manual picks matter. Testing a buried pool your rules never reference wastes time.
3. Trigger the latency sweep. Look for a global test icon, Test All, or a speedometer on the group header. Some builds place the action top-right on the Proxies toolbar; others tuck it beside each expandable group.
4. Let timeouts finish. Dead nodes show as unreachable, dash placeholders, or extremely high milliseconds. Do not assume the client froze—large lists take time on hotel Wi-Fi or corporate networks. Partial results still rank faster servers ahead of slow ones.
5. Re-run after network changes. Wi-Fi handoffs, sleep, VPN toggles, and Hyper-V virtual switches invalidate earlier numbers. A thirty-second retest before video calls saves grief.

Reading and sorting latency results responsibly

Once numbers appear beside node names, ask what they measure. A 40 ms entry to a Google static endpoint is not automatically better than an 80 ms node whose provider peers cleanly with the SaaS you use. Use sorting as a first pass, then validate with the application you care about.

Watch for these patterns on Windows 11 laptops and desktops:

• Clustered results. If five servers report 42–48 ms, any may be fine; chasing single-digit differences is seldom worth it.
• Suspicious zeros or stale dashes. Cached successes or failed UI refreshes occasionally lie. Run a second test or switch away and back.
• Protocol skew. Shadowsocks, VMess, Hysteria, and Trojan behave differently under packet loss. A “slow” label on one protocol might reverse on another path.
• Wi-Fi versus Ethernet divergence. Desktops on wired LAN and laptops on 6 GHz Wi-Fi will not share identical rankings—each machine should run its own sweep.

When url-test groups run their own health loop in the background—often labeled 自动选择 (Auto Select)—your manual sort view might not match the engine’s current pick. Check which group your rules target; nested designs often send traffic through a parent selector you forgot to open.

Manually picking a node (selector workflow)

In Clash vocabulary, manual control lives in select groups inside proxy-groups. The UI maps them to rows you can click in the Proxies panel.

Practice this loop until it is muscle memory:

1. Expand the policy group until you see individual nodes or child groups—not just the parent label on the dashboard.
2. Click one entry; the row should show a check mark, highlight, or radio-style indicator depending on your theme.
3. Confirm the dashboard or group header shows the same outbound name you clicked.
4. Load a representative site or app instead of assuming ping equals happiness.
5. If traffic ignores your pick, open Logs or Connections and verify which group name the rule referenced—then adjust that parent group, not a decorative sibling.

Templates frequently ship parallel selectors for Streaming, Telegram, Microsoft, or region-specific tags. They exist so you can pin awkward domains to stable nodes. Skim your YAML occasionally in the profile editor; providers rename groups during updates, and stale mental models cause “I clicked Proxy but YouTube still buffers” reports when the streaming rule pointed to a different selector the whole time.

Switching between policy groups (Node Select vs Auto Select)

Users search for policy group switching because subscriptions expose more than one meaningful selector. Two names appear constantly in East Asian profiles:

• Node Select / 节点选择: a pure select group. You choose the member; it stays until you change it or the profile reloads.
• Auto Select / 自动选择: usually url-test. The core periodically probes members and switches to the current winner based on tolerance settings in YAML.

Rules rarely say “use the node with the greenest latency badge.” They say “send this domain to group X.” If group X is Auto Select, your manual pick inside a child pool may never execute. When you want sticky control—for banking, RDP, or debugging—route through Node Select or duplicate the profile with a simplified tree. When you want hands-off resilience, nest a url-test pool beneath a small set of manual region choices so you toggle continents, not thirty hostnames.

The proxy-groups guide walks those YAML patterns if you outgrow pure GUI editing. On Android, the same concepts appear with different chrome; see Clash for Android: latency tests and node switching if you need cross-device consistency.

Auto groups versus manual groups in daily use

url-test and fallback groups feel like magic until they override you mid-session. The UI may still display members, but Mihomo periodically re-selects based on health probes and tolerances defined in YAML.

Symptoms that confuse new Verge Rev users:

• You picked “Singapore-02” yet logs show “Auto Select → US-West” because the matched rule referenced the auto group, not your manual selector.
• Latency looks perfect while Auto Select flaps every few minutes, dropping voice calls—tighten tolerance in YAML or switch the rule target to a stable select group.
• Global mode bypasses nuanced selectors entirely; everything exits through one outbound until you return to Rule mode on the dashboard.

Keep daily driving on Rule unless you are debugging. Use Global briefly to confirm whether a failure is rule-related or node-related, then revert. That toggle pair is documented more deeply in our Mihomo Party mode article for Windows users who juggle multiple GUIs.

Latency looks good but browsing fails—quick triage on Windows 11

This shape confuses everyone: numbers glow green in the Proxies column, yet Edge or Chrome spins. Before swapping nodes again, walk the stack:

• System proxy / TUN: If Clash Verge Rev is paused or Windows revoked helper permissions, no node selection helps.
• DNS and fake-ip: Misaligned DNS modes produce half-working sites. Match settings to what the profile documents.
• Browser DoH: DNS-over-HTTPS in Chrome or Edge can bypass the resolver path your rules assumed. Disable temporarily to validate.
• Rule order: An earlier DIRECT match still wins. Logs show the actual chain.
• WinHTTP versus user proxy: Some CLI tools read WinHTTP while browsers use the system proxy Clash sets—align both when testing developer workflows.

These failures are orthogonal to latency testing; they are why power users keep log tabs visible. When intermittent timeouts persist after node changes, graduate to Clash Verge Rev on Windows 11: log panel debugging instead of endless re-tests.

Staying aligned with subscription updates

Node lists change when providers add regions or retire hosts. Refresh schedules live separately from latency probes—tuning one does not replace the other. If catalogs feel stale despite green health checks, read how to set subscription auto-update in Clash Verge Rev before you blame Auto Select.

Community energy in 2026 clusters around open-source Mihomo stacks with frequent core updates. Whether you stay on Verge Rev for polish or explore alternatives, the mental model stays constant: rules first, groups second, nodes third. For context on maintained clients, read Clash ecosystem in 2026.

Workflow checklist before important calls or streams

Compress the entire article into a preflight you can repeat on any Windows 11 PC:

• Subscription refreshed within the last day (or whatever cadence your provider expects).
• Dashboard confirms active profile, Rule mode, and proxy integration enabled.
• Latency sweep completed on the Proxies page after the latest network attach.
• Correct selector updated—not just the fastest leaf in an unrelated pool.
• Spot-check the target app (browser, Teams, game launcher) instead of assuming ping equals happiness.

Rituals beat superstition. Once the checklist passes, ignore minor millisecond jitter unless symptoms return.

Common questions

Does Clash Verge Rev test UDP latency? Most built-in probes focus on HTTP reachability through each proxy. Real-time apps depend on UDP paths the UI may not surface. Validate voice or games with their own connection meters.

Why do two PCs on the same Wi-Fi see different rankings? Radio conditions, background apps, Hyper-V virtual adapters, and per-machine DNS settings diverge. Each host should run its own sweep.

Should I always pick the top row after a test? Only if stability matches your task. Some users intentionally pick the second or third entry when the fastest node is overloaded shared hosting.

Can I switch groups from the tray only? Tray menus are version-dependent and often limited to toggles. Use the main Proxies view for full selector trees and batch latency tests.

Why does Auto Select ignore my manual pick? Because url-test groups manage their own winner. Change the rule target to a select group or adjust YAML if you need sticky outbound control.

Choosing tools that stay understandable

Some traditional Windows proxy utilities hide group logic behind opaque wizards or rebuild routing silently when subscriptions update, which makes “fastest server” myths hard to debug on Windows 11. Clash-style clients surface proxy-groups explicitly in the Proxies panel so you can see which selector your rules hit and why a latency table disagrees with real traffic.

That transparency—paired with rule logs and YAML you can diff—cuts support loops when providers shuffle hostnames weekly. If you want a maintained client stack across Windows, macOS, and Linux with the same conceptual map, grab a current build from our download page and compare workflows side by side: download Clash when you are ready to standardize on tooling that still evolves with the Mihomo core.