Ubuntu 26.04 LTS, codenamed Resolute Raccoon, was released on 23 April 2026, and the first point release, 26.04.1, followed on 27 August 2026. With that point release, Canonical opened the official LTS-to-LTS upgrade path, so any fully updated Ubuntu 24.04 LTS system can now move to 26.04 with a single command. This guide walks you through the whole process safely: backup, pre-flight checks, the upgrade itself, and the verification steps that confirm everything survived.
This tutorial is for Ubuntu 24.04 LTS (Noble Numbat) servers and desktops. You do not need to upgrade right now — 24.04 stays in standard support until 2029 — but if you want the newer kernel (Linux 7.0), GNOME 50 on desktop, and support until 2031, this is the clean way to get there.
Prerequisites
- An Ubuntu 24.04 LTS system, fully updated
- Sudo access (or root)
- At least 10 GB of free disk space on the root partition
- A stable internet connection — the upgrade downloads roughly 2–4 GB of packages
- A backup or snapshot you can restore from if anything goes wrong
- For remote servers: SSH access, and a terminal multiplexer such as tmux so a dropped connection cannot kill the upgrade
Step 1: Back up before you touch anything
Release upgrades are reliable, but they rewrite hundreds of packages and your boot configuration. Never run one without a way back. On a VPS, take a snapshot from your provider's panel first — it is the fastest restore. On a physical machine or a VM without snapshots, back up your data and configuration with rsync:
sudo rsync -aAXv --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} / /path/to/backup/
This copies the whole filesystem, excluding virtual directories that should never be backed up. Alternatively, install Timeshift for a simple system snapshot you can roll back to from a live USB:
sudo apt install timeshift -y
sudo timeshift --create --comments "Before 26.04 upgrade"
Timeshift creates a restorable snapshot of your system files. Confirm the backup or snapshot actually exists before continuing — a backup you never verified is not a backup.
Step 2: Fully update Ubuntu 24.04
The upgrade tool refuses to run on a system with pending updates, so bring 24.04 completely up to date first:
sudo apt update
sudo apt upgrade -y
sudo apt dist-upgrade -y
sudo apt autoremove -y
apt update refreshes the package lists, apt upgrade installs available updates, and dist-upgrade also handles packages that need dependencies added or removed. Reboot if the update installed a new kernel, so you are running the latest 24.04 kernel before the upgrade starts:
sudo reboot
Step 3: Check disk space and your current version
Confirm you are actually on 24.04 and that you have enough free space. The upgrade needs room for the downloaded packages plus their unpacked replacements:
lsb_release -a
df -h /
lsb_release -a should report Ubuntu 24.04 LTS (noble). If df shows less than about 10 GB free on /, free space first — remove old kernels with sudo apt autoremove --purge, clear the package cache with sudo apt autoclean, or delete large files you no longer need.
Step 4: Install the upgrade tool and confirm the LTS path
Install the release upgrader and make sure your system is configured to offer LTS releases only:
sudo apt install update-manager-core -y
cat /etc/update-manager/release-upgrades
Look for this line in the output:
Prompt=lts
Prompt=lts means the system only offers upgrades to the next LTS release — exactly what you want. If it says Prompt=normal, you would be offered interim releases instead; change it to lts with a text editor. Then check whether the new release is available:
sudo do-release-upgrade -c
The -c flag only checks; it does not start the upgrade. On a fully updated 24.04 system you should see a message that a new release, 26.04.1 LTS, is available. If it says no new release was found, re-run Steps 2 and 4 — an out-of-date package list is the usual cause.
Step 5: Start the upgrade inside tmux (remote servers)
If you are upgrading over SSH, run the upgrade inside tmux. If your connection drops mid-upgrade, the process keeps running and you can reattach. The upgrade tool also starts a fallback SSH daemon on port 1022 as a safety net, but tmux is the layer you control:
sudo apt install tmux -y
tmux new -s upgrade
You are now inside a tmux session named "upgrade". Run everything from here. If you get disconnected, reconnect and reattach with:
tmux attach -t upgrade
Step 6: Run the upgrade
Start the release upgrade:
sudo do-release-upgrade
The tool fetches the new release metadata, calculates which packages change, and shows a summary of how many packages will be upgraded, installed, and removed. Read it, then confirm. The download phase takes a while — typically 15–30 minutes on a decent connection. You will be asked a few questions along the way:
- Restart services automatically? Choose Yes on a server you can afford to briefly restart services on; choose No if you want to restart them by hand afterwards.
- Configuration file changes: when a package you modified has a new default config, you are asked whether to keep your version or install the maintainer's. Keep your version if you customised the file (for example Nginx or SSH configs); install the new one only if you never edited it. You can diff them at the prompt before deciding.
- Remove obsolete packages? Choose Yes at the end — these are packages that no longer exist in 26.04 and keeping them only adds clutter.
Do not close the terminal or reboot while the upgrade is running. When it finishes, it asks you to reboot.
Step 7: Reboot and verify the new release
Reboot when prompted:
sudo reboot
After the system comes back, confirm the upgrade landed:
lsb_release -a
uname -r
cat /etc/os-release
You should see Ubuntu 26.04.1 LTS (Resolute Raccoon), kernel 7.0, and VERSION_CODENAME=resolute. Next, update the package lists for the new release and clear out anything left over:
sudo apt update
sudo apt upgrade -y
sudo apt autoremove -y
sudo apt autoclean
Step 8: Check your services and re-enable third-party repositories
The upgrader disables third-party repositories and PPAs during the upgrade, because their 24.04 (noble) packages do not exist for 26.04 (resolute). Check what was disabled and re-enable each one only if it provides a resolute build:
grep -r "^deb" /etc/apt/sources.list.d/
sudo systemctl --failed
systemctl --failed should report no failed units. If a service failed, check its logs with journalctl -u servicename. Then check your important services individually — Nginx, MySQL, Docker, or whatever this machine runs — and confirm each one is active:
sudo systemctl status nginx
sudo systemctl status mysql
Re-enable a PPA or third-party repo by editing its file under /etc/apt/sources.list.d/, changing noble to resolute, then running sudo apt update. If the vendor has no resolute build yet, leave it disabled and check again in a few weeks — running a repo for the wrong release is worse than not having it.
Verify it worked
lsb_release -areports Ubuntu 26.04.1 LTSuname -rreports a 7.0 kernelsystemctl --failedreports zero failed units- Your web server, database, and other services respond normally — test them in a browser or with curl
sudo apt updatecompletes with no repository errors
Common issues and fixes
"No new release found"
Your system is not fully updated, or the upgrader is not installed. Run sudo apt update && sudo apt upgrade -y, install update-manager-core, and confirm Prompt=lts in /etc/update-manager/release-upgrades. Then check again with sudo do-release-upgrade -c.
Not enough free disk space
Free space with sudo apt autoremove --purge and sudo apt autoclean, remove old kernels, and check for large files with sudo du -sh /* 2>/dev/null | sort -h. The upgrade needs roughly 10 GB free.
Upgrade interrupted or aborted halfway
Do not panic and do not reboot mid-upgrade unless the tool tells you to. If the process died, fix the package state first:
sudo dpkg --configure -a
sudo apt --fix-broken install
sudo apt update && sudo apt upgrade -y
Then re-run sudo do-release-upgrade. If the system will not boot, restore the snapshot or backup you made in Step 1.
SSH connection dropped during the upgrade
Reconnect and reattach to tmux with tmux attach -t upgrade. If SSH itself is unresponsive, the upgrader runs a fallback SSH daemon on port 1022 — connect with ssh -p 1022 user@your-server and check whether the upgrade is still running.
A service fails to start after the upgrade
Read its logs with journalctl -u servicename --since "1 hour ago". The usual causes are a configuration file the new version rejects, or a missing package that was removed as obsolete. Compare the current config with the .dpkg-dist or .ucf-dist copy left beside it, and reinstall anything that was dropped.
Conclusion
Upgrading Ubuntu 24.04 LTS to 26.04 LTS is straightforward once the groundwork is done: a verified backup, a fully updated system, enough free disk, and the upgrade run inside tmux if you are remote. The official LTS-to-LTS path has been open since the 26.04.1 point release, so there is no need for workarounds. Verify the release, check your services, and re-enable third-party repositories one by one — and you are on a supported release until 2031.
Need help upgrading a production server without downtime, or planning the move across a fleet of machines? XpertBees handles server setup, upgrades, and ongoing maintenance for businesses — reach out and we will plan the upgrade around your uptime.



