Steps
- Read the target release notes and check minimum system requirements and security notices before downloading.
- Exit v2rayN completely and verify that both the UI and core processes have stopped. Copy the entire old folder as a backup.
- Extract the new release to an empty folder. Prefer the built-in backup and restore workflow; do not merge every old binary into the new build.
- Test subscription refresh, one TCP site, DNS and proxy cleanup. Delete the old folder only after the new build is stable.
Why this matters
Overwriting loaded DLLs or cores can produce a mixed installation that launches but behaves unpredictably. Separate folders provide an immediate rollback.
How to verify
The version is updated, groups and routing survive, the core starts, and closing v2rayN leaves no unintended system proxy behind.
Things to watch
Backups contain credentials. Keep them off public cloud shares and issue trackers, and retain at least one protected offline copy.