v2rayN v6.45 Release Notes: What's Fixed and Should You Upgrade?

v6.45 is mainly a stability and experience update — no major UI changes, and everyday operation stays consistent with the previous version. The main changes are as follows:

• Fixed occasional subscription update failures: some users previously saw no response or a timeout error when tapping "Update Subscription" under certain network conditions. This has now been fixed, and update success rates have improved noticeably.
• Improved node speed test accuracy: the testing logic has been adjusted to reduce cases where a node showed abnormally low or high latency, so results now better reflect real-world performance.
• Fixed the system proxy toggle status not syncing: in some cases, the system proxy was actually on, but the main window/tray icon didn't refresh to show it, making it easy to think it wasn't working. This has been fixed.
• Reduced memory usage: optimized parts of the background-running logic, lowering memory usage after long periods of runtime.

Here's some guidance based on the changes above, depending on your situation:

• If you've experienced "occasional subscription update failures" or "status display not syncing": upgrade is recommended — this update directly fixes both of these frequently reported issues.
• If you haven't run into any noticeable issues: upgrading is fine but not required — staying on your current version won't cost you any functionality, so feel free to upgrade next time it's convenient.
• If you're installing for the first time: the version on the download page is already the latest one — no extra steps needed.

To make the upgrade decision more concrete, here's a closer look at how these changes actually show up in real use, instead of just saying "a bug was fixed":

• Subscription update failure scenario: this previously showed up mainly when switching networks (e.g., a laptop moving from a work network to a home network and immediately updating a subscription) — the request would hang with no response, requiring a manual restart to recover. After this update, requests in this scenario will correctly return a failure message after timing out, instead of hanging indefinitely.
• Skewed speed test results scenario: on the old version, during periods of heavy network fluctuation, test results could occasionally show an obviously unreasonable number, like "1 ms" for a node. The new version filters out these outliers, making test results more reliable.
• Status display out-of-sync scenario: this mainly happened after waking from sleep — the tray icon still showed "disconnected" even though the network was actually working. The new version now proactively refreshes the status display after the system wakes up.

If you're not sure what version you have installed, check the current version number in the client's "About" section or title bar, and compare it against the latest version listed on our download page. If yours is behind, just do the overwrite install described above — the whole process won't affect your saved subscription settings or node list, and you won't need to reconfigure any system proxy options.

Yes. Since v2rayN is a portable app, the overwrite install process is reversible — if you run into anything you're not comfortable with after upgrading (rare, but the occasional environment-specific compatibility issue can't be ruled out), just download the old version's zip and extract it over your existing folder the same way to roll back. Your subscription and node configurations will still be preserved. If you're especially cautious about your configuration, it's worth making a backup copy of your entire install folder before upgrading — you probably won't need it, but it removes any worry in an edge case.

Based on actual feedback, v6.45 is a routine, fix-focused update that doesn't change any workflows or the interface layout. Rollback requests are very rare — most users won't notice anything different after upgrading, aside from the fact that the fixed issues simply no longer occur.

If you're still seeing the same issue after upgrading to v6.45, or you run into something new, first work through the general steps in Connection Troubleshooting to rule out network or subscription issues. If you've confirmed it's a software-level problem, record the exact steps you took and what you observed (screenshots or error text are helpful) — that kind of detail helps pinpoint the issue far more effectively than a vague "it doesn't work."