HOW TO UPDATE CLASH VERGE REV AFTER DOWNLOADING THE LATEST VERSION
You just downloaded the newest Clash Verge Rev installer, but your old version won’t vanish on its own clash verge 官网. These steps will replace every trace of the old client, inject the fresh build, and keep your proxy rules intact—without losing a single subscription or latency test.
PRE-UPDATE CLEANUP: REMOVE OLD FILES WITHOUT LOSING CONFIG
DELETE THE APP DATA FOLDER INSTEAD OF THE SHORTCUT
Open File Explorer, paste %appdata%clash-verge into the address bar, and hit Enter. Shift+Delete the entire folder—this erases cached maps, stale logs, and leftover tun drivers that can cause conflict loops.
BACK UP YOUR PROFILES.JSON BEFORE UNINSTALL
Inside the same %appdata%clash-verge folder, copy profiles.json to your desktop. This single file holds every subscription, rule-set, and DNS override you’ve ever added; reinstalling without it means rebuilding from scratch.
KILL THE TUN DRIVER MANUALLY IF THE UNINSTALLER HANGS
Press Win+X, open Device Manager, expand “Network adapters,” right-click “Clash Verge TUN,” and select Uninstall device. Check “Delete the driver software” to prevent ghost adapters from blocking the new install.
EXTRACT THE NEW INSTALLER TO A TEMP FOLDER FIRST
Right-click the downloaded .exe, choose “Extract here” with 7-Zip, and inspect the contents. Look for a file named version.txt—if it matches the release notes you expected, proceed; if not, redownload from the official GitHub mirror.
REPLACE THE OLD CORE BINARY WITHOUT REBOOTING
After extraction, copy clash-windows-amd64.exe (or clash-windows-arm64.exe) to %appdata%clash-vergeresourcesstaticbin. Overwrite the existing file, then launch Verge—it will auto-detect the new core without requiring a full reinstall.
RESTORE YOUR PROFILES.JSON TO THE NEW INSTALL LOCATION
Paste the backup profiles.json into %appdata%clash-verge again. Open Verge, click the gear icon, and verify every subscription loads—if one fails, check the subscription URL for typos or expired tokens.
FLUSH DNS CACHE TO PREVENT STALE ROUTE CONFLICTS
Open Command Prompt as admin and run ipconfig /flushdns. This clears any cached IP mappings that could route traffic through the old core’s tun adapter instead of the updated one.
REAPPLY SYSTEM PROXY SETTINGS MANUALLY
Go to Windows Settings > Network & Internet > Proxy, toggle “Use a proxy server” off, then back on. Enter 127.0.0.1:7890—this forces Windows to rebind the proxy port to the new core.
RECONFIGURE FIREWALL RULES FOR THE NEW EXECUTABLE
Open Windows Defender Firewall, click “Allow an app through firewall,” find Clash Verge in the list, and remove it. Then add the new clash-windows-amd64.exe (or arm64) with both private and public network access checked.
VERIFY THE CORE VERSION IN THE LOG TAB
Launch Verge, switch to the Log tab, and look for a line like “Clash core v1.18.0 started.” If the version doesn’t match the release notes, repeat the core binary replacement step—your overwrite may have failed.
RESET LATENCY TESTS TO REFLECT NEW NODE PERFORMANCE
Click the globe icon, select all nodes, and press Shift+T to retest latency. Old results are cached in the profiles.json and can mislead you into thinking the update didn’t improve speeds.
RE-ENABLE TUN MODE IF IT DISABLED ITSELF
Go to Settings > General, toggle “TUN Mode” off, wait 5 seconds, then toggle it back on. This reinitializes the virtual network adapter and prevents DNS leaks caused by stale driver states.
REAPPLY CUSTOM RULE-SETS FROM LOCAL FILES
If you use custom rule-sets (e.g., direct.txt, proxy.txt), re-add them in the Rules tab. The update may reset the file paths, so browse to the exact location again to avoid silent rule failures.
REBOOT IF THE TUN ADAPTER STILL SHOWS “UNIDENTIFIED NETWORK”
After all steps, restart your machine. Windows sometimes holds onto old adapter metadata until a full reboot, which can block the new core from binding to the network stack.
POST-UPDATE TROUBLESHOOTING: FIX COMMON GLITCHES IN 60 SECONDS OR LESS
FORCE A CORE RELOAD WITH