v2rayN 7.23.4 is now available on this site, covering every architecture on Windows, macOS, and Linux — grab it from the download page. If you're on an older version, you can check for updates right in the app, or upgrade manually using the steps below. It's only a minor version bump, but the core and several frequently reported issues got real fixes, so we'd recommend upgrading soon.
What's New in This Update
- Core upgrades: the built-in Xray and sing-box cores have been updated to their latest stable versions, improving connection stability on weak networks and noticeably reducing handshake failures.
- Fixed subscription auto-update not working: fixed an issue where scheduled subscription updates silently failed to run, mostly affecting users who had "Launch at startup" enabled.
- Improved desktop-edition tray menu: the right-click menu is more responsive, and routing-mode status now displays more accurately — previously it would occasionally show a mode that didn't match what was actually active.
- Better log window performance: fixed stuttering in the log window after long uptimes — you can now scroll through history smoothly.
- Various UI polish and translation fixes, including updated descriptions for some settings.
Is This Update Worth Installing?
If things are working fine for you and you haven't run into subscription or connection issues, there's no urgent need to upgrade right away — the core upgrades are more of an incremental improvement than a dramatic change. But you should upgrade soon if any of this applies to you: you rely on scheduled subscription updates; you're often on weak or unstable networks; you depend on the tray menu's routing-mode status (e.g. you frequently switch between Global and Bypass Mainland); or you've recently run into log-window stuttering or occasional subscription update failures.
What Do the Xray and sing-box Cores Actually Do?
v2rayN itself is just a "shell" — the actual work of establishing connections and encrypting traffic is done by the bundled core engine. Most modern clients bundle both the Xray and sing-box cores, letting you switch depending on the protocol or use case. Xray has more mature support for the earlier VMess and VLESS protocols with broad compatibility; sing-box is a newer implementation that performs better with certain newer protocols and multiplexing scenarios. Day to day, you don't need to worry about which core is being used — the client picks automatically based on your node type. This update mainly upgraded both cores to their latest stable versions, fixing low-level connection issues without touching any settings you'd need to adjust yourself.
How to Upgrade
- In-App Upgrade: in the main menu, choose "Check for Updates" → select v2rayN, and restart when prompted after the download finishes. All your settings and nodes are preserved — this is the easiest way.
- Manual Upgrade: grab the new archive from the download page and extract it over your existing folder (config files live in the
guiConfigsfolder and won't be lost when overwriting). Good for when the in-app update check fails, or if you're using the portable build and don't want it checking online. - Confirming the Upgrade Worked: once upgraded, open "About" on the main screen to check the version number and confirm it shows 7.23.4 — the core version numbers will be updated too.
guiConfigs folder was accidentally deleted or overwritten during extraction — normally it should be preserved intact. For other issues, see the full troubleshooting guide.
What's Coming Next
Based on community feedback, the next release will focus on improving the multi-subscription management interface and further reducing memory usage. We'll add the new version to this site as soon as it's released, and post an update to this article — follow our blog for the latest news.
Can I Keep Using the Old Version?
If your setup is simple and the current version is running stably, sticking with the old version for a while poses no real risk — v2rayN's core connection features stay consistent across minor releases. That said, staying on an old version indefinitely means missing out on core-level compatibility and security fixes, and if your provider updates their protocol details, an older core might fail to recognize the new parameters. The general advice: you don't need to chase every minor release, but check for updates periodically so you don't fall so far behind that a future upgrade means jumping several versions at once.