Skip to Content
DocsOperationsUpgrade & MigrationUpgrade from 25.10 to 26.04 LTS

Upgrading from 25.10 to 26.04 LTS

Note

This article has been initially checked against the Ubuntu 26.04 LTS April 2026 release notes. The 25.10-to-26.04 upgrade path should still follow the official release upgrader prompt.

Warning

Ubuntu 25.10 reached end of life in July 2026 and no longer receives security updates. Users still on 25.10 should upgrade to 26.04 LTS as soon as possible; if the upgrader cannot handle the now-EOL release directly, follow the official EOL upgrade guidance.

Ubuntu 25.10 is an interim release with only 9 months of support. Its support window has now ended, so upgrading to 26.04 LTS as soon as possible is recommended.

Interim Release vs. LTS

Feature25.10 (Interim)26.04 (LTS)
Support period9 months5 years standard, Pro/ESM until 2038
Security updatesUntil July 2026 (ended)Standard until April 2031, Pro/ESM until 2038
Update frequencyNew version every 6 monthsNew LTS every 2 years
StabilityNewer package versionsLong-term tested and verified
Warning

Be sure to complete a full data backup before upgrading. Although upgrading from 25.10 to 26.04 spans fewer versions and carries relatively lower risk, third-party software incompatibilities may still occur.

Pre-Upgrade Preparation

1. Confirm Current Version

lsb_release -a # Should display Ubuntu 25.10 cat /etc/os-release

2. Fully Update the Current System

sudo apt update sudo apt upgrade -y sudo apt dist-upgrade -y sudo apt autoremove -y

The 25.10 system must be updated to the latest state; otherwise, the upgrade tool may refuse to run.

3. Install the Upgrade Tool

sudo apt install update-manager-core -y

4. Check Upgrade Policy

cat /etc/update-manager/release-upgrades

Ensure Prompt is set to normal or lts:

# If it's normal, you can upgrade directly to the next version # If it's lts, you need to change it to normal (since 25.10 is not an LTS) sudo sed -i 's/^Prompt=.*/Prompt=normal/' /etc/update-manager/release-upgrades

Note: When upgrading from an interim release, Prompt must be set to normal because the upgrade path is 25.10 -> 26.04, which requires detecting “the next version” rather than “the next LTS.”

5. Back Up Important Data

# Back up personal data rsync -avz /home/ /backup/home/ # Back up system configuration sudo tar czf /backup/etc-backup.tar.gz /etc/ # Export installed package list dpkg --get-selections > ~/packages-25.10.txt # Record current kernel uname -r > ~/kernel-25.10.txt

6. Handle Third-Party Sources

# List third-party sources ls /etc/apt/sources.list.d/ # Interim version PPAs may not have packages for 26.04 # It is recommended to disable them in advance for f in /etc/apt/sources.list.d/*.list; do sudo mv "$f" "$f.bak" done # For .sources format files for f in /etc/apt/sources.list.d/*.sources; do [ -f "$f" ] && sudo mv "$f" "$f.bak" done

Performing the Upgrade

Command-Line Upgrade

# It is recommended to use screen to prevent connection interruption screen -S upgrade # Start the upgrade sudo do-release-upgrade

Upgrading via SSH

# Allow the backup SSH port sudo ufw allow 1022/tcp # Run in screen/tmux screen -S upgrade sudo do-release-upgrade # If disconnected, reconnect screen -r upgrade # Or connect via the backup port ssh -p 1022 user@server-ip

If No New Version Is Found

# Use the -d parameter (development channel) sudo do-release-upgrade -d # Check network curl -s https://changelogs.ubuntu.com/meta-release | grep -A5 "26.04"

Choices During the Upgrade

  1. Confirm upgrade - Review the list of packages to install, upgrade, and remove, then confirm
  2. Configuration file conflicts - If you have modified configuration files:
    • Keep the local version (keep the local version currently installed) - recommended as first choice
    • Use the new version (install the package maintainer's version) - if you want the new default configuration
  3. Delete obsolete packages - Recommended to select Yes
  4. Restart - Restart after the upgrade is complete

Post-Upgrade Steps

1. Verify Version

lsb_release -a # Distributor ID: Ubuntu # Description: Ubuntu 26.04 LTS # Release: 26.04 # Codename: resolute uname -r cat /etc/os-release

2. Change Upgrade Policy Back to LTS

After upgrading to LTS, it is recommended to change the policy back to lts to avoid accidentally upgrading to the next interim release:

sudo sed -i 's/^Prompt=.*/Prompt=lts/' /etc/update-manager/release-upgrades # Verify grep Prompt /etc/update-manager/release-upgrades # Should output: Prompt=lts

3. Full Update

sudo apt update sudo apt upgrade -y sudo apt autoremove --purge -y sudo apt clean

4. Check System Health

# Check for broken packages sudo dpkg --audit sudo apt --fix-broken install # Check for failed services systemctl --failed # Check disk space df -h # Check logs for errors sudo journalctl -p err --since "1 hour ago"

5. Restore Third-Party Sources

# View disabled sources ls /etc/apt/sources.list.d/*.distUpgrade 2>/dev/null ls /etc/apt/sources.list.d/*.bak 2>/dev/null # After confirming third-party sources support 26.04, restore them one by one # Note: The version codename may need to be updated from questing (25.10) to resolute (26.04)

6. Check Kernel

# View installed kernels dpkg --list | grep linux-image # Remove old kernels sudo apt autoremove --purge # If you need to manually remove a specific old kernel sudo apt remove --purge linux-image-x.x.x-xx-generic

Differences from a Direct LTS Upgrade

Upgrading from 25.10 has several key differences compared to upgrading from 24.04 LTS:

  1. Smaller software version differences - 25.10 package versions are closer to 26.04, with less change
  2. Lower upgrade risk - Fewer versions to span, fewer compatibility issues
  3. Different Prompt setting - Must use normal instead of lts
  4. Third-party source compatibility - 25.10 PPAs may already have packages compatible with 26.04
  • Short support periods mean frequent upgrades increase risk
  • Must upgrade every 6 months
  • Missing the upgrade window means you cannot skip versions (e.g., you cannot go directly from 25.04 to 26.04)
  • LTS versions are always recommended for production environments
Last updated on