Check these three things before installing
You don't need to decipher the entire filename. Check the package format, system architecture, and purpose to avoid most download mistakes.
Know the difference between archives and installers
ZIP is an archive that must be extracted before installation. DMG is a mountable disk image; APK is an Android app package; DEB and RPM packages must be opened with a compatible system package installer. “Download complete” in your browser only means the file was saved, not installed.
If double-clicking opens an archive utility or text editor, return to your downloads folder and check the full file extension and your system's default app. Changing the extension doesn't change the file format or make a package for another platform work.
Check the system architecture, not just the chip specs
“64-bit” isn't specific enough: x64 and arm64 are both 64-bit architectures, but they're not interchangeable. When installing in a virtual machine, check the system running the client—not the host machine's model.
A universal package doesn't work on every system. It lets one Android APK support multiple app architectures, but the minimum Android version, app signature, and device management policies can still prevent installation.
First installs and upgrades
For a first install, choose a package that matches your platform and import your configuration after launching the app. Before upgrading over an existing install, check which client you have, where it came from, and where its configuration is stored. Desktop and Classic WPF are separate editions, not simply newer and older versions of the same installation.
Before switching packages, disconnect normally and quit the client. After restarting, check your subscription groups and selected server, then confirm that the system proxy or connection status is as expected. Once everything checks out, remove the old installation directory.