How to Install Avast on Ubuntu 26.04 and 24.04

Share

To install Avast Business Antivirus on Ubuntu, add Avast’s official APT repository, install the scanner, and activate a Linux license. Avast supports Ubuntu 26.04, 24.04 and 22.04 LTS. Its Linux product uses terminal commands and background services rather than the Windows-style antivirus dashboard.

This guide takes you from choosing the Linux product to your first scan, automatic updates and optional protection for shared files. If you get stuck, leave a comment or contact us.

Before you begin
  • System: this walkthrough uses 64-bit Intel/AMD Ubuntu (amd64) with systemd. Check your release and architecture below before adding the repository.
  • Access: you need a sudo account and an internet connection for packages, activation and virus definitions.
  • License: the scanner packages are publicly downloadable, but scanning requires a valid Avast Linux license. Do not assume a Windows or Mac subscription covers it.
  • Protection: the core package provides on-demand scanning. Continuous monitoring of selected shared folders requires the optional File Server Shield setup.
  • Existing installation: keep your license file and back up any customized Avast configuration before making changes.

1. Get Avast for Linux

Choose Avast Business Antivirus for Linux on Avast’s product page. Check the Linux license, device count, term and renewal details before purchasing. The button opens the product page; the installation below downloads packages through Avast’s repository.

Get Avast Business Antivirus for Linux

Affiliate disclosure: we may earn a commission if you purchase through this link.

Avast is useful when you need to check files stored on an Ubuntu machine or passed to other computers, especially on a file server. It complements system updates, restricted permissions and backups. A successful scan does not guarantee that every file is safe.

2. Install Avast from its official APT repository

Step 1: Check Ubuntu and install the prerequisites
Ubuntu terminal
cat /etc/os-release
dpkg --print-architecture
ps -p 1 -o comm=

Continue on Ubuntu 26.04 (resolute), 24.04 (noble) or 22.04 (jammy), with amd64 architecture and systemd as process 1. These commands identify your system; they do not change it. For another release or architecture, confirm support with Avast before buying or installing.

Ubuntu terminal
sudo apt update
sudo apt install ca-certificates curl gnupg

Read APT’s proposed changes before confirming. This guide does not cover containers or WSL installations.

Step 2: Check for an existing Avast source
Ubuntu terminal
grep -RnsE 'repo\.avcdn\.net/linux-av|deb\.avast\.com' /etc/apt/sources.list /etc/apt/sources.list.d/ 2>/dev/null

No matching output means no matching source was found in those files. If you see an existing Avast entry, inspect and back it up before proceeding. Keep one entry for your actual release; do not layer this one over an older entry with a different signing-key setting.

The next steps create /etc/apt/keyrings/avast.asc and /etc/apt/sources.list.d/avast.list. If those files already exist, back them up and reconcile them first; tee replaces their contents.

Step 3: Download and inspect Avast’s signing key
Ubuntu terminal
sudo install -d -m 0755 /etc/apt/keyrings
avast_key=$(mktemp)
curl -fsSLo "$avast_key" https://repo.avcdn.net/linux-av/doc/avast-gpg-key.asc
gpg --show-keys --with-fingerprint "$avast_key"

Stop if the download or key inspection fails. The expected primary-key fingerprint is 3865 1411 0F1A 8006 7954 37B5 129F B08F BDEC FE35, verified against the key in Appendix H of the official technical guide. Only continue when it matches, then place the public key in APT’s key directory:

Ubuntu terminal
sudo install -m 0644 "$avast_key" /etc/apt/keyrings/avast.asc
rm "$avast_key"
Step 4: Add the source for your Ubuntu release

This block checks the release and architecture before writing the source. Run the complete block in a Bash terminal:

Ubuntu terminal
(. /etc/os-release
case "$ID:$VERSION_CODENAME:$(dpkg --print-architecture)" in
  ubuntu:jammy:amd64|ubuntu:noble:amd64|ubuntu:resolute:amd64)
    printf 'deb [arch=amd64 signed-by=/etc/apt/keyrings/avast.asc] https://repo.avcdn.net/linux-av/deb ubuntu-%s release\n' "$VERSION_CODENAME" | sudo tee /etc/apt/sources.list.d/avast.list
    ;;
  *)
    printf 'Unsupported system for this walkthrough. No source written.\n' >&2
    exit 1
    ;;
esac)

For Ubuntu 26.04, the repository suite is ubuntu-resolute; for 24.04 it is ubuntu-noble; for 22.04 it is ubuntu-jammy. Stop if the block rejects your system. Do not substitute a different release to bypass the check.

Step 5: Install the scanner and license utility
Ubuntu terminal
sudo apt update
apt-cache policy avast avast-license

Check that both packages have a candidate from repo.avcdn.net, with a package version for your Ubuntu release. Stop and fix any repository or signature errors before installing:

Ubuntu terminal
sudo apt install avast avast-license

The package starts downloading virus definitions after installation. The scanner may remain unavailable until that download finishes and a license is in place. Do not add the REST API or File Server Shield packages unless you need their functions.

3. Activate your Linux license

Step 1: Obtain the license file

If Avast supplied license.avastlic, save it in your Downloads folder and skip the activation-code command. If you received an activation code, use the license utility below. Replace the placeholder with your own code; do not post it in a comment or screenshot.

Ubuntu terminal
avastlic -o "$HOME/Downloads/license.avastlic" -c YOUR_ACTIVATION_CODE

Ensure the Downloads folder exists, or choose another existing output folder. Follow any customer-information prompts. Avast limits how often some codes can retrieve a license, so keep the resulting file safely. The code is entered on the command line and may remain in your shell history.

Step 2: Install the file and start Avast

If a license already exists at the destination, save a secure backup before replacing it. Adjust the source path if you saved the new file elsewhere:

Ubuntu terminal
sudo install -o root -g avast -m 0640 "$HOME/Downloads/license.avastlic" /etc/avast/license.avastlic
sudo avast -l
sudo systemctl enable --now avast.target
sudo systemctl restart avast.target

The license check should finish without an invalid, missing or expired-license error. The file permissions let the Avast service read the license without making it readable to every local user. If the check fails, resolve the license problem before scanning.

4. Update definitions and run your first scan

Step 1: Confirm definitions are available
Ubuntu terminal
sudo systemctl start avast-vpsupdate.service
systemctl status avast-vpsupdate.service --no-pager
scan -V

The update job can take time on its first run. Check its result, then confirm scan -V reports a definitions version. The update service is a one-shot job: being inactive after a successful completion is normal.

Step 2: Scan a readable folder

Start with Avast’s installed documentation. This checks that the command-line client can reach the licensed scanning service:

Ubuntu terminal
scan -a /usr/share/doc/avast
printf 'Scan exit status: %s\n' "$?"

The -a option shows clean files as well as findings. [OK] means no threat was detected in that file; [ERROR] means it could not be fully scanned. The exit status is 0 for no infection found, 1 for an infection found and 2 for a scan error. A finding takes precedence when a run contains both findings and errors.

For your own files, replace the example directory with an existing folder you intend to inspect, such as a shared-files directory. The scanner service must be able to read the files and traverse their parent directories. Running the client with sudo does not by itself change the service’s access rights.

This on-demand command reports findings; it does not automatically clean or delete your files. If something is flagged, avoid opening or sharing it, preserve the report and investigate before deleting anything.

5. Keep Avast updated

Program packages and virus definitions update separately. For the installed packages:

Ubuntu terminal
sudo apt update
sudo apt install --only-upgrade avast avast-license

If you also installed File Server Shield, include avast-fss in that upgrade command. Review the proposed changes before proceeding. To inspect the definition-update schedule:

Ubuntu terminal
systemctl list-timers --all avast-vpsupdate.timer

The current package schedules definitions updates every three hours. Streaming updates can supplement that schedule. If the timer is absent or disabled, inspect the service logs and confirm avast.target is enabled.

6. Optional: monitor Samba or NFS shared files

Install File Server Shield only when you need continuous monitoring of selected folders. It scans files after writes and can move infected files into its quarantine directory. It is separate from a scan you start manually.

Step 1: Install the optional shield

Back up important shared files first and plan a maintenance window. This package changes the scanner to run as root so it can monitor files; enabling it can affect files used by other people.

Ubuntu terminal
sudo apt install avast-fss
sudo cp -a /etc/avast/fss.conf /etc/avast/fss.conf.before-guide
sudoedit /etc/avast/fss.conf

Use a different backup filename if that backup already exists. In the existing [MONITORS] section, add the real shared directory, for example:

File Server Shield configuration example
[MONITORS]
SCAN = "/srv/shared"

Replace /srv/shared with an existing directory you actually share. Do not duplicate the section if it is already present. Do not monitor the entire root filesystem as a starting configuration.

Step 2: Start the shield and inspect its logs
Ubuntu terminal
sudo systemctl enable avast-fss.service
sudo systemctl restart avast.target
systemctl status avast-fss.service --no-pager
sudo journalctl -u avast-fss.service -n 30 --no-pager

Check that the service is active and the logs show no configuration errors. Threat detections are recorded in /var/log/avast/fss.log; the default quarantine is /var/lib/avast/chest. After later configuration edits, restart avast-fss.service. Bind mounts and container namespaces need additional care; consult the shield’s manual before relying on monitoring in those layouts.

7. Review the reporting settings

Avast’s configuration includes telemetry, threat-reporting, reputation-query and streaming-update options. Check your organization’s requirements before scanning confidential files:

Ubuntu terminal
sudoedit /etc/avast/avast.conf

The shipped configuration documents the options under [OPTIONS]. To disable telemetry and threat reporting, uncomment or set the following existing keys there, keeping only one active value for each key:

Optional reporting configuration
[OPTIONS]
TELEMETRY = 0
STATISTICS = 0
COMMUNITY = 0

This leaves reputation queries and streaming updates unchanged. It does not make Avast offline or establish a no-data-sharing configuration. Review man avast for the other network features. Apply a configuration change with:

Ubuntu terminal
sudo systemctl reload avast.service

8. Fix common Avast problems

Issue 1: APT reports a missing repository or signature error

Confirm the Ubuntu codename, source entry and readable signing key. A duplicate source can cause a conflicting Signed-By error. Back up an older entry before removing or replacing it. Do not use trusted=yes or disable signature verification to force installation.

Ubuntu terminal
cat /etc/apt/sources.list.d/avast.list
gpg --show-keys --with-fingerprint /etc/apt/keyrings/avast.asc
sudo apt update
Issue 2: The scanner cannot connect or reports no license
Ubuntu terminal
sudo avast -l
systemctl status avast.socket avast.service --no-pager
sudo journalctl -u avast.service -n 50 --no-pager

Check the license path and its permissions, then read the journal for the actual failure. The core service can be inactive until a scan connects through its socket; that alone is not proof of a broken installation. An expired or wrong-product license needs resolving with Avast.

Issue 3: Failed to load VPS or definitions never update
Ubuntu terminal
sudo journalctl -u avast-vpsupdate.service -n 50 --no-pager
sudo systemctl start avast-vpsupdate.service

Check network access, free disk space and the error in the update log. After a successful update, retry scan -V. Avoid adding a second cron job over the systemd timer.

Issue 4: Files return permission errors

The default scanner service runs as the avast account. Private home directories may prevent it from reaching files even if the client runs with sudo. Use a dedicated scan folder with narrowly scoped read and directory-traversal access, or ask your administrator to grant access to the intended shared directory. Do not make your whole home directory world-readable.

9. Remove Avast without deleting quarantine or backups

Step 1: Remove the installed packages

Save the license, customized settings and any quarantine files you need first. Removing Avast stops its protection. Check which components are installed:

Ubuntu terminal
dpkg-query -W -f='${binary:Package} ${Status}\n' 'avast*'

For the core setup in this guide:

Ubuntu terminal
sudo apt remove avast avast-license

If installed, remove avast-fss and avast-rest too. Review APT’s removal list before confirming. Package removal and subscription cancellation are separate; manage billing through your Avast account.

Step 2: Remove the dedicated repository and key

Only remove these files if they are the dedicated source and key created or reconciled for this guide:

Ubuntu terminal
sudo rm /etc/apt/sources.list.d/avast.list
sudo rm /etc/apt/keyrings/avast.asc
sudo apt update

Keep /etc/avast and /var/lib/avast until you have reviewed retained configuration, license and quarantine data. Do not run a recursive cleanup against those directories just to remove the program.

Helpful resources

Avast technical documentation and signing key | Avast Business support

Frequently asked questions

Is Avast for Ubuntu free?

The current Linux business scanner requires a valid license to scan. Public access to its package repository does not make the product free. Check that the license you choose covers the Linux product.

Does Avast for Linux have a desktop dashboard?

This guide uses the Linux scanner service and the scan command-line utility. Do not expect the Windows-style consumer antivirus dashboard or install a Windows executable on Ubuntu.

Does installing Avast automatically protect every file in real time?

The core package supports scans you request. Continuous monitoring requires the optional avast-fss package and configured directories. Installing the core scanner alone does not configure File Server Shield.

Can Avast scan files that will be used on Windows computers?

You can scan accessible files stored on Ubuntu before sharing them with another computer. This is useful for shared-file workflows, but a clean scan is not a guarantee that a file is harmless.

Why does sudo scan still report permission errors?

The scanning service reads the files, not the scan client. Elevating the client does not automatically give the service permission to traverse a private directory or read its contents.

Does uninstalling Avast cancel my subscription?

No. Removing packages stops the installed software; it does not cancel billing. Review or cancel the subscription separately through your Avast account.

View Avast for Linux licensing

More Ubuntu security guides: Ubuntu antivirus options | Set up Bitwarden for your passwords.