On this page
The installer has finished downloading, but reinstalling Clash Verge Rev reports that it cannot uninstall the old version or write a file. Record where the wizard stopped and whether the old app is still running before taking the next step.
First identify whether uninstalling or overwriting failed
The official v2.5.10 release fixes the Windows installer's failure to prompt for a running app to close before reinstalling or overwriting it. This article covers files held open by the old app; an uninstall failure alone does not establish that this defect is the cause.
Separate the failure stages
| What you see | What to check first |
|---|---|
| The installer has not finished downloading, or the in-app download is stuck | Resolve the download, cancellation or cache issue first; installation has not reached the stage covered here |
| The wizard fails while uninstalling the old version, or a file is in use during overwrite | Record the installation path and check whether the old app has fully exited |
| The old app has exited, but a permission, path or other error remains | Keep the first error and investigate that cause instead of repeatedly accepting the same prompt |
Why can the old version fail to uninstall before the new one is installed?
Official PR #8519 explains that the old installer script checked for the running app using a bare executable name and did not detect file use as intended. The fix passes the executable's full path in the installation directory so the check corresponds to the actual installation.
The timing also changed. The old workflow could invoke the previous uninstaller before checking for a running app when extracting the new version's files. Uninstalling could already have failed because files were in use. The fix checks the relevant reinstall-page branches earlier, before uninstalling or proceeding with an overwrite.
This article applies to the Clash Verge Rev Windows NSIS EXE installer. The fix is separate from updating the Mihomo core, refreshing subscriptions or reinstalling the system service. It does not directly cover standalone MSI files, portable packages, macOS or Linux installation errors.
Save your work and fully exit before running the official installer
Choose a time when you can interrupt network access. Save your work, record the current configuration, mode, node and necessary traffic-routing settings, and keep recoverable copies of your configuration and persistent overrides. Work on the installation you actually use, with only one installer running at a time.
The verified stable release containing this fix is v2.5.10. There is no need to downgrade from a later stable release with evidence of the same fix. Use the official Release in the references to choose an EXE for your Windows architecture and existing installation method; a download-page title or core version does not identify the installer's actual version.
Retry once in this order
Exit the old app and confirm its installation directory
Close the failed installer first. Save your configuration in the app, stop the proxy or traffic-routing mode you need to interrupt, then fully exit through the system tray. Closing the main window may leave the app in the tray; confirm that you are updating the installation directory you have been using.
Run a stable EXE that contains the fix
Confirm that no other install or uninstall process is active, then run the official installer for the correct architecture. Keep the existing installation location and read the version and reinstall options shown by the wizard.
Respond to a running-app prompt
If the wizard still detects a running instance, save any remaining work before deciding whether to let it close the app. If you cannot interrupt it yet, cancel and return later. Repeatedly accepting the prompt is not a way to bypass files that are still in use.
Wait for installation or uninstallation to finish
Let the current wizard finish before starting the app. If it fails again, record the earliest error, the stage and the target path. Avoid switching between several installers and retrying them at the same time.
The cannot-uninstall message is a general failure message in the installer script. A nonzero result from the old uninstaller or a main executable that still exists can trigger it. Cancelling the old uninstaller also has its own return path, so returning to the selection page does not always mean the same file-in-use failure occurred.
Verify the original path, app version and configuration after installation
Reopen Clash Verge Rev from your usual entry point and check the running version and program directory. A desktop shortcut may still open another, older installation. Confirm the original configuration, persistent overrides, mode and node selection instead of relying only on the wizard's completion page.
Reactivate the configuration that previously worked, restore system proxy or TUN as needed, and make a new real request. Check the connection record and actual exit in the client, then confirm that the task succeeds. Installing the files and restoring proxy connectivity are separate results to verify.
Complete these checks before closing the investigation
- The install or uninstall process has ended, with no error or running-instance prompt still awaiting a response.
- The app starts from the intended directory, and its full application version contains this fix.
- The original configuration and persistent overrides work; mode, node and necessary traffic-routing settings have been checked.
- A new real request uses the expected exit, and normal use has recovered.
- After a normal exit and reopen, the same installation starts with the expected configuration.
This article was checked against the official release, merge notes and fixed installer source. It does not include installation testing on a real Windows client. Website checks cannot replace installation and connectivity checks on your device.
If it still fails, recover according to the first error
The app has exited, but uninstalling or writing files still fails
Cancel this attempt and keep the error text, installer version and target path. Check for another app instance or installation process. If the message specifically identifies a permission or path problem, address that error rather than continuing to attribute it to running-app detection.
You cannot close the app you are using yet
Cancel installation, preserve the working state and choose a time when network access can be interrupted. If Windows must be restarted to clear a lingering state, save all work first. After restarting, run one installer before opening the old app.
Uninstallation finished, but the new version was not installed successfully
Keep your configuration backup and error record, then restore the app with a stable installer from the same trusted source, matching the architecture and installation location. Do not turn a program-file error into lost configuration by manually deleting the data directory.
The new version starts, but the original configuration no longer works
Save the current state separately, then restore your own known-working configuration and previous selections. If the app must be rolled back, use a verifiable official version and matching backup, ensuring that old and new programs do not compete for the only data directory.
When reporting the problem, include the Windows version, original and target app versions, EXE architecture, reinstall choice, failure stage, whether the app had fully exited, and the first error. Redact usernames and other private path details; do not upload complete configuration packages containing subscription tokens or node passwords.
References
- Clash Verge Revv2.5.10 stable release: Windows reinstall and overwrite prompt fix
- Clash Verge RevPR #8519: running-app detection path, timing and reproduction
- Clash Verge RevFixed commit f149604: running-instance checks in the installer
- Clash Verge Revv2.5.10 Windows NSIS script: reinstall, install and uninstall branches
- MicrosoftWindows Restart Manager: full file paths required to register resources
- Clash Verge RevOfficial issue #8555: cannot open a file for writing during installation
