Updated July 2026 · 6 min read
Install on Windows
The release page carries an x64 installer and a portable archive, and they store data in different places. This is which to take, and what to check on first launch.
Installer or portable build
A normal 64-bit Windows machine wants the x64 setup file. Click through and it is done in under a minute, usually launching itself at the end. ARM hardware needs its own architecture, and the wrong one will not start.
The portable build is an archive you unpack and run. Profiles and config stay in its own folder, which suits an external drive. In exchange it does not register itself for autostart, and service mode becomes a manual step.
What blocks the installer
SmartScreen often steps in and calls the program uncommon. That reflects download counts and signing, not a damaged file: expand the details, choose to run it anyway, and move on. Downloading again changes nothing.
Some security suites flag the write into the program folder, and most are false positives. Add the target folder as an exception first, then check the executable is still there: a quarantined file shows up as a missing file at launch.
Do not keep both builds on one machine. Their data folders are separate, so the setting you changed may belong to the copy that is not running.
Three checks on first launch
Look for the tray icon in the notification area, since it is your only way back once the main window is closed. The interface takes a few seconds to paint on the first run: that is the frontend loading, not a freeze.
Then open the Logs page. A running core produces a steady stream, including lines about listening ports. An empty page, or nothing but errors, means mihomo never started. A completely white window is a separate WebView2 problem covered elsewhere.
Leave TUN off until a profile loads
TUN hands every packet on the machine to the core. With no usable node yet, the browser, your chat apps and Windows Update all go down together, which looks exactly like a broken network adapter.
Do it the other way round: import the subscription on the Profiles page, pick a node with a sane latency, turn on the system proxy and confirm pages load. Service mode and TUN come last, so a failure points at one step.
What is the project?
Clash Verge Rev is a Tauri-based GUI for Mihomo with profile management, system proxy, TUN mode, rule editing and WebDAV backups.