Fresh install
Use system information to choose the right package
The interface edition, CPU architecture and file format address three different things. The edition determines menus and workflows; the architecture determines whether the program can run; and the format determines which installer handles it. Two packages with the same file extension aren’t necessarily interchangeable, and file size doesn’t tell you which package suits your device.
If you download a package and transfer it to another device, use the system information on the target device. If the installer reports an architecture or format mismatch, go back and select the package under the correct platform tab. That’s more effective than changing the extension or trying a different extraction tool.
In-place upgrade
Back up your configuration before replacing the app
Before updating, note the current client, interface edition and installation source. If export is available, save your subscriptions and manually entered configurations first. If you’ve customized routing or DNS, check that the backup includes those settings too. Keeping only a subscription link may let you retrieve the nodes again, but it won’t restore locally added rules or notes.
Disable the system proxy or disconnect, then fully quit the old client. After launching the new version, check that your groups, nodes and ports are as expected before reconnecting or enabling startup at login. Store backups containing subscription URLs or node credentials in a secure location; don’t include their full contents in screenshots or logs.