What Changed, and Should You Upgrade Right Away

  • Fixed an issue in certain scenarios where switching routing modes required restarting the client to take effect;
  • Improved batch speed test responsiveness, eliminating noticeable lag when there are many nodes;
  • Improved subscription update failure messages, now more clearly distinguishing between "network issue" and "subscription address invalid";
  • Fixed a rare issue where the "launch at startup" setting stopped working after a system restart.

Updates to this type of client mostly come from ongoing work by the open-source community: users run into issues during everyday use and file reports, and maintainers verify and fix them in later releases — a fairly typical open-source workflow. That's why the items listed above are all specific behavior fixes, rather than vague marketing language like "across-the-board experience improvements" — every one of them maps to a real, previously existing issue, not a feature invented out of thin air. If you're currently running into any of these (like a mode switch not taking effect, or unclear subscription update failure messages), we recommend upgrading soon; if everything's working fine for you right now, feel free to upgrade at your own pace — this update doesn't involve any breaking changes that require reconfiguration, and the upgrade process itself is lightweight.

Will Upgrading Wipe My Configuration? Here's How It Works

No, it won't. Your subscription address, added nodes, routing mode, and other settings are all stored in a local configuration file, kept separate from the client program itself — a normal installation of the new version won't clear any of it. That said, to be safe, we still recommend exporting a configuration backup from settings before upgrading, especially if you've manually tweaked a fair number of custom rules — while it's extremely rare for an overwrite install to wipe your configuration, backing up costs almost nothing and can save you the time of reconfiguring if something does go wrong. The process itself is straightforward: just grab the latest installer from the download page and install it following your system's standard process — the new version will install over the old one and keep your existing configuration. After installing, open the client and confirm your subscriptions and node list still show up normally, and you're good to keep using it.

A Few Common Questions Before and After Upgrading

Do I need to uninstall the old version first? No — the new installer will install directly over the old one, no manual uninstall needed, and your configuration won't be lost. What happens if the network drops during the upgrade? The installation process itself doesn't need an internet connection — only the step of getting the installer from the download page requires network access, and you can install offline once the download finishes. Is upgrading the same for the portable and installer versions of Windows? Basically yes — for the portable version, just replace the old version's folder with the new one (remember to copy your config directory over first); for the installer version, just run the standard install process to overwrite the old one.

Once the upgrade is done, it's worth spending a minute on a quick check: open the client and confirm your subscription still shows up correctly, manually click connect to see if you can get online, and check that the routing mode is still the one you had set before (it shouldn't have changed under normal circumstances, but it doesn't hurt to double-check). Once you've confirmed all three, you can keep using the new version with confidence.

What If You're Not Ready to Upgrade Yet, or Want to Know About New Versions Right Away

The old version won't suddenly stop working just because a new one is released, but if you're currently running into any of the issues covered in this article, sticking with the old version means those issues will keep happening — and future releases will likely keep including this fix too, so the longer you wait, the more you fall behind. If you're not planning to upgrade for now, we recommend at least confirming the old version can still connect normally and that subscriptions still update fine — if both check out, there's no real risk to holding off in the short term. To find out about new releases as soon as they're published, besides checking back on this release notes section periodically, you can also keep an eye on the client's own "check for updates" feature (if it has one), or just bookmark the download page — we always keep the version number shown there in sync with what's currently available, so you can compare it against your locally installed version anytime. If you're not sure what version you're currently on, most clients show the version number under "About" or in the main window's title bar; and if you're several versions behind, there's no need to upgrade one version at a time — just update straight to the latest, since it already includes all the fixes from every version in between.

One more thing worth mentioning: v2rayNG and v2flyNG each publish their own releases on their own schedule, with content that doesn't always sync up — so you can't use v2rayN's release notes to guess whether the other two need upgrading too. We recommend checking the latest version number for whichever client you're actually using on the download page and upgrading as needed — there's no need to worry that updating one means the others need to follow; all three are maintained independently on their own schedules, and using them together causes no compatibility issues.