On this page
When the progress bar stops, find out whether the app is still downloading or the installer has taken over. Once installation starts, wait for the result. If it is still downloading, keep the original configuration and a working connection before deciding whether to cancel or use the official installer, so you can verify the completed upgrade.
A stalled update download: what progress, cache and cancellation mean
Save the progress, waiting time, first error, and what changed after cancellation. If the installer has started, wait for the result without forcing it to stop. If downloading is still in progress, follow the official-installer procedure below.
At this review, the latest official stable release is v2.5.8. The old updater must first finish this upgrade before it can use the new implementation; reopening the old window cannot load the fix. There is no need to downgrade to test the next update.
What v2.5.8 fixes, and what needs a separate check
Official issue #8172 reports a Windows upgrade from v2.5.6 to v2.5.7: already downloaded content was downloaded again, transfers were slow, and Cancel did not stop them. A maintainer linked the cache reuse and cancellation fixes. The v2.5.8 release published on 10/9/2026 lists all three fixes; this does not establish that every stuck update has the same cause.
Identify the stage
| Observed pattern | How this version handles it | What to check |
|---|---|---|
| A completed download starts over | v2.5.8 checks that the cached version matches the current update and verifies the installer signature before reusing it. | A version mismatch or failed verification still triggers a new download; downloading again is not always a defect. |
| Slow download or stalled progress | The updater tries the manifest address, another mirror, then GitHub. The first pass checks for a source that is too slow and switches away from it. | Switching sources is a recovery attempt. It does not guarantee access on every network or a quick completion. |
| Cancel only closes the window | v2.5.8 invokes actual cancellation during preparation and downloading. | Once installation has started, cancellation cannot be promised. Do not repeatedly launch updates or forcibly terminate the installer. |
| Installation failure or service error | This is outside the download fixes described here. | Keep the installation error and full version, then follow the official installation and service guidance for your platform. |
In the fixed source, the first download pass checks progress every 30 seconds and switches sources when the increase is less than 1 MiB. After all sources fail on that pass, the second pass checks only for stalls. This is not a promise to fix a download within 30 seconds, and GitHub is not always tried first.
The new version still distinguishes Cancel from closing the window: Cancel invokes the backend, while closing the window only hides it. Cancel only during preparation or downloading, wait for the operation to end, then retry. Closing the window during installation does not stop installation.
Record the progress when the download stops, the time already spent waiting, the first error, and whether installation is still running. Opening the project home page in a browser only proves that the page is reachable, not that the corresponding installer or addresses redirected to during the download are reachable. Do not open multiple updater windows at once to speed things up.
Retain an independent backup and upgrade with the official installer
Open Backup Settings under the advanced Verge settings, create a local backup, then export the pre-upgrade record from the backup history. Save it outside the application data directory. Creating a record alone does not save an independent copy; separately save external configuration files and resources you manage. Keep backups and subscription credentials on your own device.
If the installer has started, wait for the result and keep any errors; do not force it to stop. If downloading continues despite Cancel, first make sure you have the official installer. If obtaining it requires your current proxy, keep that working connection until the download is complete. Then stop the system proxy or TUN normally, fully quit the app, and upgrade manually using the official procedure.
Complete one upgrade while retaining settings
Confirm version and system architecture
Record the full app version, OS, architecture, current Profile and proxy mode, and retain the exported pre-upgrade backup. If the installer is open, wait for its result. In v2.5.8, the system-log text Installing update v also indicates entry into installation handling. Older versions may not show it, and its absence does not prove that downloading is still in progress.
Choose an installer from the official Release
Open the official v2.5.8 Release linked below and choose the package for your system and architecture using the official installation guide. On macOS, also check the minimum system requirement. A historical installer backed up by this site is not evidence of this fix version.
Install normally and restart
After the download finishes, upgrade using the normal platform installation method, retaining your data and installation location. Package-manager users should keep the corresponding official channel; do not mix portable builds or installation directories. Do not execute the temporary cache file pending_update.bin, bypass signature verification or clear application settings to force an update.
Check the running version and original settings
After launch, confirm the version actually running is v2.5.8. Check the original Profile, nodes, rules and proxy mode, then verify normal access with a new HTTPS request. Quit normally, restart and check again.
If the official installer download itself fails, keep the working client and backup, record the first network error on that download path and follow the official guidance. If you already have the installer but installation fails, stop downloading repeatedly and investigate the installation stage. Do not disable security software or use an unverified package to bypass the problem.
Verify this upgrade, then check the next real update
Checks for this upgrade
- Full running version is v2.5.8, and the original configuration loads normally
- Nodes, rules and proxy mode are correct; a new HTTPS request succeeds
An up-to-date message verifies only the version check; it does not demonstrate that you have tested cache reuse or download cancellation. Wait until a genuine official update is available, then observe one update. A complete cache matching the version with a valid signature should be reusable. If you need to cancel, do so only during preparation or downloading, and confirm the operation has ended before retrying.
If a source switch, signature failure or version mismatch causes another download, save the error and stage first. Progress resetting to zero alone does not establish a cache reuse failure. After successful installation, restart normally and verify the new version; a closed window is not proof that an upgrade finished.
Restore configuration and report update failures
If configuration is actually damaged, preserve the current data first. Import the previously exported pre-upgrade file into the backup history, then select that record and run Restore Backup. Importing only adds a record; it does not apply it automatically. After restoration, check subscriptions, rules, proxy mode and a real request again.
Prefer restoring configuration already verified to work. If you must roll back the application version, first check the official security advisory and backup compatibility. Do not assume a backup made by a new version can be read by an older one, or copy an old-version suggestion from an issue without checking it. If no working configuration is available, normally stop proxy interception and check ordinary networking; pause work that requires the proxy.
If the problem persists, report the full version, system and architecture, target update version, stalled stage, wait time, state after cancellation, first error and result after a normal quit and restart. Redact subscription tokens, private addresses and backup contents. Do not attach installers or credentials. Describe observed download and installation results separately, and do not label an untested fix as verified.
References
- Clash Verge RevClash Verge Rev v2.5.8 fixes for cache reuse, slow sources and download cancellation
- Clash Verge RevRepeated downloads, slow transfers and ineffective cancellation: report and maintainer reply #8172
- Clash Verge Revv2.5.8 implementation of cache verification, source switching and cancellation stages
- Clash Verge Rev DocsOfficial Clash Verge Rev installation guide and system requirements
- Clash Verge RevConfiguration files included in v2.5.8 backup archives
- Clash Verge RevWindows service security advisory to check before rolling back
- Clash Verge Revv2.5.8 local backup import, restore, and configuration reload
- Clash Verge Revv2.5.8 backup export, restore confirmation, and automatic restart