How to set up automatic system updates in elementary OS
Keeping elementary OS updated protects your computer against newly discovered security problems and ensures that core components receive bug fixes. Automatic maintenance is especially useful when the system is used for everyday work, study, banking, or storing personal documents.
Updates in elementary OS come from more than one source. Debian and Ubuntu-based system packages are managed through APT, while many graphical applications are delivered as Flatpaks through AppCenter. These two channels can have different settings, so enabling one does not necessarily update everything installed on the computer.
The best arrangement for most people is to install security updates automatically, allow normal application updates through AppCenter, and review larger feature or kernel changes before restarting. This gives you protection without allowing an unattended process to interrupt a presentation, download, or long-running task.
The steps below suit a typical home computer in Australia, whether it is connected through an NBN service in Brisbane, a university network in Melbourne, or a mobile hotspot while travelling between regional towns. Menu names can vary slightly between elementary OS releases, but the underlying tools remain familiar.
What automatic updates cover
APT handles the operating system itself and many traditional Linux packages. This includes libraries, hardware support, networking tools, desktop components, and security fixes. When unattended upgrades are enabled, elementary OS can download and install approved packages in the background according to its configured schedule.
AppCenter may also offer Flatpak applications, which are packaged separately from the base system. Applications such as creative tools, communication clients, and utilities can therefore have their own update cycle. Open AppCenter and select the Updates view to see whether application updates are waiting. If an application was installed from another source, such as a downloaded .deb file or a third-party repository, its update behaviour depends on that source.
Automatic updates usually do not mean that every update is installed without limits. The system can be configured to accept security updates while leaving optional packages for manual review. Kernel and low-level hardware updates can be installed automatically, but the new version normally becomes active only after a restart.
Check the existing update settings
Start by opening System Settings and looking for the Updates or System section. Depending on the elementary OS release, you may see controls for checking for updates, downloading them, installing security fixes, or displaying notifications. Read the wording carefully: a setting that checks for updates is different from one that installs them.
Then open AppCenter and inspect its Updates page. If there is a pending update, install it and note whether the application is a Flatpak or a system package. This quick check prevents a common misunderstanding in which the operating system is current but several graphical applications remain outdated.
You can also inspect the system from Terminal without changing anything. Run:
apt list --upgradable
This lists packages with available upgrades. To refresh the local package information first, use:
sudo apt update
The update command downloads current package lists; it does not install software. If the result includes many packages, that is not automatically a problem. A computer that has been switched off for several weeks may simply be catching up.
Enable updates with graphical tools
If your version of elementary OS exposes an automatic update switch in System Settings, enable security updates first. Look for options referring to downloading or installing security updates automatically. Leaving notifications enabled is worthwhile because it tells you when a restart or manual action is needed.
AppCenter is the safest graphical route for applications supplied through the elementary ecosystem. Open it periodically, select Updates, and apply the available changes. Some releases show an automatic update preference in AppCenter or system settings; if that control is present, it can be enabled for a computer that is regularly connected to a reliable network.
The graphical settings are designed for ordinary desktop use, but they may not expose every APT option. If the automatic controls are missing, greyed out, or unclear, use the command-line method below rather than editing configuration files at random. Before changing anything, record your elementary OS version in System Settings so that instructions for another release are not accidentally applied.
Configure unattended upgrades from Terminal
Install the package that provides automatic installation of approved updates:
sudo apt update
sudo apt install unattended-upgrades
On many Ubuntu-based systems, the following command opens the standard configuration prompt:
sudo dpkg-reconfigure --priority=low unattended-upgrades
Choose the option to download and install stable updates automatically. This enables the normal APT periodic mechanism and is generally preferable to creating a custom script. The package uses repository rules to determine which update origins are trusted.
You can check the periodic settings with:
cat /etc/apt/apt.conf.d/20auto-upgrades
A typical configuration contains settings similar to these:
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
The value 1 represents a daily interval. These lines tell APT to refresh package information and attempt unattended upgrades daily; they do not guarantee that a package will be installed if it is held back or requires an unusual manual decision.
Use sudo only for commands that genuinely need administrator access. Avoid copying a complete configuration from an unrelated Linux guide, because repository names and package policies can differ between elementary OS releases. A backup of a file before editing is sensible:
sudo cp /etc/apt/apt.conf.d/50unattended-upgrades \
/etc/apt/apt.conf.d/50unattended-upgrades.backup
Choose security coverage and restart behaviour
The default unattended-upgrades policy normally permits updates from the operating system’s security and regular update repositories while rejecting unknown sources. Review /etc/apt/apt.conf.d/50unattended-upgrades if you need to understand the allowed origins. Do not enable a random third-party repository simply because it offers a newer version of a package.
Automatic upgrades can occasionally remove obsolete dependencies or install a new kernel. They generally do not restart the computer without an explicit configuration choice, which is helpful if the machine runs overnight backups or is used as a small home server. The trade-off is that a security fix may not be active until the next reboot.
Check for a reboot requirement with:
test -f /var/run/reboot-required && echo "Restart required"
Save work and restart when convenient if that message appears. On a laptop used for remote work in Perth or Adelaide, it is sensible to reboot before an important meeting rather than leaving several kernel updates inactive for weeks.
Automatic upgrades can also fail when a package manager is already busy. Do not run AppCenter updates and a large Terminal upgrade at the same time. Wait for one process to finish, then try again. If an interrupted installation is reported, the usual repair command is:
sudo dpkg --configure -a
sudo apt -f install
Manage Australian network and data limits
Most fixed NBN connections have enough monthly allowance for regular updates, but automatic downloads may still be inconvenient during evening congestion or while using a backup connection. A household in Sydney or Canberra might share one connection across several devices, so scheduling updates outside school, work, or streaming hours can reduce contention.
Mobile broadband requires more care. A prepaid SIM in a 4G router, a phone hotspot, or a regional wireless service may impose a data cap. Before enabling large Flatpak updates, open AppCenter and check their size. If necessary, disable automatic downloads temporarily, mark the connection as metered where the desktop offers that option, and update while connected to unlimited NBN or workplace internet.
APT’s periodic jobs are usually daily rather than tied to a precise clock time. If you need predictable maintenance, a systemd timer or a small scheduled task can run a controlled update, but advanced scheduling should be tested carefully. A laptop that is asleep at the scheduled moment may not perform the task until it wakes, and a command requiring sudo can pause if it needs a password.
Do not switch off security updates permanently to save a small amount of data. A better compromise is to allow security packages automatically and handle large application updates manually. For Flatpaks, this command shows and applies available updates when you choose:
flatpak update
Verify that updates are working
After enabling automatic maintenance, inspect the update history rather than assuming it worked. APT logs can be viewed with:
grep " upgrade " /var/log/dpkg.log
The unattended-upgrades log is commonly found at:
sudo less /var/log/unattended-upgrades/unattended-upgrades.log
Look for successful package installations, repository errors, or messages about packages being kept back. A package may remain pending because it requires a dependency change, conflicts with a held package, or comes from a repository that is temporarily unavailable.
For a wider view of resource use during an update, the System Monitor guide explains how to inspect CPU, memory, disk, and network activity in elementary OS. This is useful when an older laptop appears slow while AppCenter downloads or unpacks several packages.
If a repository returns a 404 error, check that it supports your elementary OS release before changing anything. Remove obsolete third-party sources through Software & Updates or the relevant repository configuration, then run sudo apt update again. Never ignore repeated signature or authentication warnings: they may indicate a broken source or a security problem.
Flatpak applications can be checked separately:
flatpak remote-ls --updates
If an application refuses to update, identify whether it came from AppCenter, Flathub, or a manually added remote. Third-party software advice can vary widely, so treat general Android and Linux software sites such as Android app news as background reading rather than as a substitute for checking the package source on your own computer.
Keep a simple maintenance routine
Automatic updates work best with occasional human review. Once a month, open AppCenter, apply remaining application updates, check whether a restart is waiting, and remove software you no longer use. This routine is short enough for a home desktop and helps prevent a large backlog from building up.
Keep at least one recent backup before major upgrades. Personal files in Home are usually unaffected by package updates, but a backup protects against hardware failure, mistaken commands, and unrelated problems. An external drive, a trusted NAS, or a reputable cloud service can all be useful, with encryption considered for private documents.
For most elementary OS installations, the practical balance is clear: enable unattended security updates, allow AppCenter to manage supported applications, avoid untrusted repositories, and restart when the system requests it. Check the logs occasionally and pause large downloads when using mobile data. With those habits, automatic maintenance stays quiet in the background while your system remains protected and ready for daily use.
