Steps
- Record the v2rayN and active-core versions and compare them with the latest release notes.
- Back up configuration and stop the service, then use Check for updates to update each core you actually use.
- Restart and read the first log lines to confirm the loaded version and executable path.
- Test TCP, DNS and any UDP or TUN workflow you depend on. Keep logs and roll back from backup if a regression appears.
Why this matters
A new UI can generate settings an old core does not understand. Keeping a combination tested by the project avoids silent option loss and startup failures.
How to verify
Logs show the expected core version, existing profiles connect and the core updater no longer reports the previous build.
Things to watch
Never replace an executable while it is running, and avoid third-party 'optimized core' downloads.