Glossary
Glossary of terms
Installer windows and system settings speak a special language in which every other word sounds official and slightly threatening. In reality, the ideas behind them are fairly simple. Here we explain them briefly so that next time you'll understand what you're agreeing to.
Half of all software misunderstandings begin when someone read the word “free” but missed the word “trial.”
How this section works: the definitions are brief and skip the technical details. Terms are grouped by meaning, not alphabetically.
Installation and types of programs
- Installer
- A file that copies a program into the right folders, creates shortcuts and adds entries to the system settings. Its screens are usually where the extra offers hide.
- Portable version
- A version of a program that runs from its own folder without a full installation. It's easy to carry around and easy to remove, but it usually has to be updated by hand.
- Startup apps
- The list of programs that launch automatically when you turn on the computer or sign in. The longer the list, the longer the computer takes to get going after you turn it on.
- Potentially unwanted program
- A program that isn't technically malicious but gets installed without clear consent, shows ads, changes browser settings or gets in the way. It often comes bundled with another install.
Licenses and updates
- License
- The terms under which the developer allows you to use a program: whether you can use it for free, on how many computers, for what purposes and for how long.
- Open source
- A program whose source code is published and available to study. The license determines what exactly you're allowed to do with it. Being open source doesn't automatically mean free or safe.
- Trial version
- A program you can use for a limited time or with limited features so you can decide whether it's worth buying.
- Security update
- A fix that closes a vulnerability found in a program or system. It's worth installing promptly rather than waiting until someone takes advantage of the vulnerability.
Permissions and verification
- Administrator rights
- The authority to change system settings, install programs for all users and touch other people's files. A program needs them during installation and maintenance, but not for everyday work.
- Restore point
- A saved state of system files and settings that you can return to after a failed install or update. It doesn't replace a backup of your personal files.
- Checksum
- A short string calculated from a file's contents. If the developer publishes it on their website, you can compare it with the checksum of the file you got and make sure it hasn't been altered or corrupted.
- Digital signature
- A mark the developer uses to confirm that a file was released by them and hasn't been changed since it was signed. The system often shows the publisher's name when you run it; a missing signature is a reason to take a closer look.
Read next
- Comparisons
How free, trial, open source and paid software differ, how an installer compares to a portable version, and which updates to install right away.
- Tools
Built-in system tools that help keep programs in order: the list of installed apps, startup apps, updates, recovery options and account permissions.
- Guides
Step-by-step guides: how to install a program carefully, update it, review startup apps and uninstall it without leftovers. Plus our article catalog.
- Security
Risks when looking for software: fake download sites, pirated versions, installers with bundled extras and fake update notifications in your browser.
- Questions
Answers about this reference, about installing and updating programs, and about keeping a home computer from turning into a storage room of forgotten apps.
Sources
- Documentation from operating system and software developers (general principles)
- Softoban editorial materials
These recommendations are written in general terms as of the date they were prepared. Installer windows, menu items and the names of system tools vary and change with updates, so check your system's help and the program developer's documentation rather than relying on how things looked last time.