On this page
Download from GitHub Releases, not a file-sharing site's “all-in-one edition”
To install Clash Verge Rev on Windows, start on the project's GitHub Releases page. It shows the project name, version tag, release date, change notes, and original assets together. A file-sharing link, forum attachment, or “portable all-in-one edition” from search results cannot prove that a similarly named file was not repackaged.
The client only runs Mihomo, reads configurations, and manages the system proxy; it does not include working nodes. After installation, you still need to import your own subscription or local YAML. Keeping “client” separate from “subscription service” makes it clear which side to inspect when something fails.
x64, ARM64, and WebView2 answer three different questions
Choosing a Windows installer
| File label | When to use it |
|---|---|
| x64 | The vast majority of Intel- or AMD-based Windows 10/11 computers |
| ARM64 | Windows devices with an ARM processor |
| fixed WebView2 or bundled WebView2 | Managed environments that cannot install WebView2, or where the standard package explicitly reports that the component is missing |
| portable | Users who understand the impact of data directories, permissions, and service mode |
Open “Settings > System > About” and inspect System type; do not guess architecture from the computer's brand or appearance. Intel and AMD generally use x64, while Snapdragon and other ARM devices use ARM64. With a mismatched architecture, Windows often says, “This app can't run on your PC.”
Typical users should start with the standard installer. WebView2 is an interface dependency already present on most Windows 10/11 systems. Consider a bundled release only if the standard installer explicitly reports WebView2 missing and the system cannot install it separately.
When SmartScreen appears, recheck the source instead of disabling protection
After double-clicking the installer, SmartScreen may say that Windows protected your PC. This is not a signal to disable security; it is a reminder to compare the download page, version, and filename again. If any of the three differ, stop installation and redownload from the project Release.
Managed computers may also require administrator approval. Do not seek a cracked portable package to bypass restrictions or permanently disable antivirus software. Having an administrator approve the current program, or installing on a personal device, is cleaner than replacing system files.
Make only necessary choices during installation
Quit the old proxy client
Exit the old Clash process and VPN from the tray so they do not compete for ports or the system proxy after installation.
Run the installer matching your architecture
The default installation location is usually sufficient; do not add an unfamiliar localization patch.
Launch from the Start menu
Give the interface and core a few seconds to initialize.
Open the About screen
Record the client version and Mihomo core version; both matter during troubleshooting.
Use the built-in language option for Chinese; do not install a third-party localization patch
After the client opens, go to Settings on the left, then Interface Settings, and select “Simplified Chinese” from the Language menu. This localization changes only interface text, not node protocols or configuration formats. Separate localization patches from the internet are unnecessary and may overwrite files required for automatic updates.
After changing the language, confirm that the core keeps running and the settings and log screens open normally. If the window crashes, stays blank, or repeatedly restarts the core, no subscription is involved yet; investigate the installer, WebView2, old data, or security software.
The window is blank and reports missing WebView2
Install Microsoft WebView2 Runtime; in restricted environments, use the corresponding bundled build from the Release.
The interface works, but the core repeatedly fails to start
Inspect logs for port conflicts, stale configuration, and security-software blocking.
It exits immediately after opening
Confirm that the system version is supported, then retest with a stable installer for the same architecture.
Update and enable the subscription on the Profiles screen
Open the Profiles screen, paste the complete HTTPS subscription address, and save it. A name in the list means only that the client remembered the address. Only a successful manual update, changed update time, and policy groups and nodes appearing on the proxy screen prove that the returned content was parsed.
If the provider offers several formats, choose one compatible with Clash or Mihomo. Do not paste the token-bearing raw link into an unfamiliar online converter. For client error, certificate, or parsing failures, preserve the status code and error text and ask the subscription provider to confirm the format.
Four signs that the configuration truly works
- Profiles shows a new update time
- The current configuration is selected
- Policy groups and nodes appear on the Proxies screen
- Logs do not repeatedly show parse or download failed
For the first connection, pin one node; do not rush to enable TUN
Open Proxies and click a working node in the primary selection group. Keep the mode on Rule, then enable System Proxy. Visit a familiar website in the browser and open Connections to inspect the request. If you can see the target, matched rule, and outbound route, the Windows system proxy was configured successfully.
Do not use an automatic benchmark group or enable TUN in the first test. If the browser fails, you then need to inspect only three links: the system proxy, node, and rule. Expand traffic capture only after ordinary requests are stable.
- The page opens, and Connections contains a record
- The installer, core, configuration, and system proxy now form a complete path.
- The page fails, and Connections has no record
- The browser did not pass through the client; inspect the System Proxy toggle and Windows proxy settings.
- A record exists and shows DIRECT
- The rule sent this request directly; inspect the rule instead of reinstalling the program.
- The record uses a node but shows timeout
- Switch to another verified node; the installer is usually not the cause.
Installation, import, and connectivity failures require different fixes
If the installer will not run, return to system architecture, system version, and file source. If the interface opens but the subscription fails, inspect HTTP status, format, and token. Only when the configuration is valid but pages will not open should you inspect nodes, the system proxy, and rules. Separating errors by stage avoids immediately clearing cache or resetting Windows networking.
This app can't run on your PC
Recheck System type and use the matching x64 or ARM64 package.
Profile update shows 401 or 403
The subscription credential is invalid or the server refused access; sign in to the service panel again and generate a link.
Profile updates successfully, but Proxies is empty
Confirm that the response is a Clash/Mihomo configuration rather than a web page or format for another client.
Browser requests do not enter Connections
Confirm that the current client controls the Windows proxy address, and quit the old client.
At this point, downloading, installation, built-in Chinese, subscription import, and the first connection each have visible results: the installer came from the project Release, the About screen shows the version, the interface switched directly to Chinese, Profiles has an update time, and the browser request appears in Connections. For future client updates, continue selecting the correct architecture and stable-release asset; there is no need to reinstall a so-called localization patch.