Software updates and subscription updates are different
Before disabling automatic updates, identify what you want to stop. This guide changes the client’s preference for checking for new software versions. It does not stop your provider’s node subscription from refreshing, and it does not roll back an already installed version.
The instructions cover the actively maintained Clash Verge Rev v2.5.6 official release on Windows 11, for x64 or ARM64, using the English interface. The app must already be installed and able to open Settings. These steps do not apply directly to the original Clash Verge, Clash for Windows, or other clients. To confirm the running version, find Verge Version in the Verge Advanced Setting group.
Automatic checking is enabled by default in this version. Disabling it pauses subsequent automatic checks; it does not freeze every update-related action. If your aim is to avoid interruptions during work, first read the downloaded-update limitations below. Turning off notifications is not a reason to leave an old version unmaintained indefinitely.
Open Miscellaneous, turn the switch off, and save
Note the current switch state so you can restore it later. Follow the menu names below; there is no need to reinstall the app, select a different node, or change the system proxy.
- Open the Settings page.
- Find the Verge Basic Setting group, then select Miscellaneous to open its settings dialog. Verge Basic Setting is a group heading; Miscellaneous is the entry to open.
- Turn off Auto Check Update. Leave the other options unchanged, including test URLs, logs, and connection settings.
- Select Save and wait for the operation to finish. Do not simply toggle the switch and dismiss the dialog.
- Open Miscellaneous again and confirm that Auto Check Update remains off. If saving produced an error, keep the error message and check the actual state rather than treating the switch’s color as proof of success.
After a successful save, you do not need to restart Clash Verge Rev, its proxy core, or Windows. Subsequent automatic checks use the new preference, and the background updater reads it when entering later checking rounds. Taking effect does not mean an active network request is immediately cancelled.
Miscellaneous requires Save. Its dialog does not behave like settings that submit immediately when you choose an option. If saving fails, do not assume every part of the state has automatically reverted. Recheck the selection, resolve the error, and confirm the result.
Why an update prompt can still appear
In v2.5.6, this preference affects automatic checks in the interface and subsequent background check-and-download rounds. Turning it off does not guarantee that an already running download stops, and it does not delete an update package already cached locally.
| What you see | What disabling automatic checks means |
|---|---|
| Later automatic searches for a new version | The normal automatic flow stops after you save the disabled setting; manual checking remains a separate action. |
| A download started before the change | Cancellation is not guaranteed. A continuing download does not by itself show that saving failed. |
| An installation prompt at startup for a downloaded update | The cached update can still trigger confirmation. Later does not delete that cache. |
| A subscription card still refreshes its nodes | That uses the subscription’s own update settings, not the software update-check switch. |
If the next startup asks to install an update already downloaded, choose Later if you want to keep using the current version for now. This version keeps the cache and continues normal startup, so a later launch may ask again. Install Now consents to the installation process; do not select it merely to dismiss the prompt.
The presence or absence of a prompt is not a sufficient check of whether the setting was saved. First reopen Miscellaneous and check the saved switch, then distinguish an existing cached update from a new check. This guide does not cover deleting the update cache, forcibly cancelling downloads, blocking update domains, or changing the installer’s behavior.
Check manually and restore automatic checking when needed
With automatic checking off, you can still open Settings, find Verge Advanced Setting, and select Check for Updates. This manual entry can still initiate a check; compare the result returned by the client with the official Release page. Checking the version and agreeing to download and install it are separate actions; read the prompt before deciding.
A check error does not prove that you have the latest version, nor does it show that disabling the preference failed. Keep the exact error and consult the project’s official Release page. Do not use an unknown mirror, bypass certificate checks, or disable security software to suppress a warning. This preference does not require edits to subscriptions, ports, or firewall settings.
To restore automatic checking, return to Miscellaneous, enable Auto Check Update, select Save, and reopen the dialog to confirm. Enabling it does not mean a new version is installed immediately, and it does not guarantee that the next check runs at once. Use the manual entry if you want to check now. There is no need to delete the configuration directory or reset the other Miscellaneous settings.
Keep track of security fixes even with automatic checking disabled. Set aside time to read official release notes and check manually. This guide only changes the checking preference; it does not make older versions permanently safe or recommend ignoring fixes for known problems.
Official sources and version scope
- Clash Verge Rev v2.5.6 release
- Official documentation: automatic update checks
- Pinned source: miscellaneous settings and saving
- Pinned source: basic settings entry
- Pinned source: version display and manual checks
- Pinned source: automatic query control
- Pinned source: background updates and cached installation prompts
- Pinned source: saving preferences and error boundaries
Version numbers, filenames, and interface labels can change. Confirm them in the linked project documentation before making changes.