FAQs (Windows Focus)
Covers empty proxy menu, TUN network issues, wrong architecture downloads, WebView2 UI problems, antivirus blocking, silent/autostart issues, lingering system proxy, subscription selection errors, UWP loopback limits and more.
More Q&A and Notes
Beyond installation, UI and permission‑related issues, many scenarios involve network environment, subscription quality and routing setup. Evaluate experience by need: web browsing cares about latency/TTFB; streaming depends on bandwidth/stability. Typical references: 1080P ≈ 5 Mbps, Netflix 4K ≈ 15 Mbps; peak‑hour bandwidth is more representative. If “network only works when Clash is on”, it’s likely lingering system proxy—disable manual proxy under Windows Settings → Network & Internet → Proxy. For UWP apps (Microsoft Store) not proxied, enable loopback in the in‑app UWP tool and save.
Subscription not selectable and socket permission errors are often due to system services—restart Host Network Service via net stop hns / net start hns. Autostart failures can stem from legacy entries or permission mismatches—toggle auto‑start once under admin and non‑admin to clean up; for very old versions, uninstall all and reinstall the latest. If UI doesn’t show or only tray appears, check WebView2 installation/enabling; restoring Windows Update or using a fixed_webview2 build helps. If service mode is blocked by antivirus, disable or uninstall the blocker to avoid driver‑level interference.
TUN issues are commonly multiple NICs or routing conflicts—remove redundant NICs and check routes. Allow verge‑mihomo core through the firewall; service mode can start TUN without admin. Overall: keep subscriptions/rules updated, combine auto/manual groups, enable system proxy or TUN as needed, and troubleshoot by permissions, components, services and network environment for stable, secure operation.
CauseCore communication failed.
FixTurn Windows Firewall off, then on again.
CauseMultiple NICs/subnets conflict with rules.
FixRemove redundant NICs in Network settings; see related issues.
CauseWrong architecture package.
FixMost users should download x64, not arm64.
CauseTauri depends on WebView2; if removed/disabled, UI won’t show.
FixCheck if Edge/WebView2 are disabled; reinstall WebView2; or use a fixed_webview2 build.
CauseAntivirus (e.g., 360, Kingsoft) blocks service‑mode install.
FixDon’t use these antiviruses or fully exit during installation.
CauseWindows Update disabled.
FixEnable updates; if still failing, use a fixed_webview2 build.
NoteCurrent versions don’t support Windows 7—upgrade to Win10/11.
CauseStartup entries cleaned or conflicting; permission states mismatch.
FixToggle auto‑start once under admin; then under non‑admin to remove extra entries.
If multiple processes due to naming/path differences, uninstall old versions and reinstall latest.
CauseSystem proxy left enabled.
FixWindows Settings → Network & Internet → Proxy → disable “Use a proxy server”.
SymptomLog error: An attempt was made to access a socket in a way forbidden by its access permissions.
FixStart services:
net stop hns
net start hnsOr restart Host Network Service in Services.
CauseUpgrading from very old versions breaks installed path detection.
FixUninstall all existing Clash Verge Rev, reinstall latest.
CauseUWP sandbox prevents localhost access; local proxy port unreachable.
FixClash Settings → UWP Tool, check apps to allow loopback, click Save Changes.
NotePWSH variable defaults to 127.0.0.1, not ideal for other hosts.
FixCreate user env var CLASH_VERGE_REV_IP with desired IP; restart app and copy PWSH variable.
SymptomSystem shows proxy ON with correct port, but app shows OFF.
FixInstall the latest version; or check registry:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ConnSystem & Components
Ensure system version and components (WebView2, service mode) are healthy.
Quick Commands & Tools
- Host Network Service：net stop hns / net start hns
- UWP loopback: allow in the in‑app UWP tool
- Proxy lingering: Windows Settings → Proxy → disable manual proxy