Before downloading: check these three things separately
Identify your operating system first, then check the architecture it reports, and finally confirm the OS version and dependencies required by the package. “64-bit” describes the word size; it doesn't distinguish x64 from arm64. The same architecture may also use different package formats on different operating systems. Built-in system information is more reliable than a device's age, appearance or product listing.
On a shared computer, work computer or managed phone, also check the local installation policy. Even if the package matches the architecture, account permissions, administrator policies or work-profile restrictions may block installation. Confirm what's allowed first; don't disable protections or keep trying different packages.
Before updating: separate the app from its settings
The installer updates the app, while personal settings may be stored in a separate data directory. Before updating, use the client's backup or export feature to save subscription groups, manually added nodes and custom routing rules. If you need to back up the data directory, quit the client first to avoid copying files while they're being written.
A subscription URL can only restore the entries provided by the subscription; it won't restore all your local changes. Make a note of the current version, installation channel and data location too. Backups may contain connection credentials, so keep them somewhere access-controlled and don't share them publicly in screenshots or logs.
First launch: test with a minimal configuration
First, make sure the main window opens normally. Then follow the subscription import guide to add a configuration and select an entry. For the first connection, leave custom routing and DNS settings out. Check the client's connection status and test access in a regular app. Once the basics work, add extra settings one at a time.
If the app won't open, start with the system requirements and installation messages. If it opens but can't read the configuration, check that the subscription imported successfully. If the configuration appears but won't connect, check the selected node, connection logs and client mode. This order helps distinguish installation issues from configuration problems and makes it easier to roll back one step at a time.