Ubuntu 26.04.1 na wetin, and why server no download?

Wetín Ubuntu point release be

An Ubuntu point release, like 26.04.1, na the release wey you already get, with every update wey dem publish since launch join inside fresh installation media. E no be new version. The archive wey e install from no change, and the suite name for your apt sources no change too. So, server wey dem install and patch already no get anything to download when point release appear.

Two things dey happen that day. Dem rebuild the media: new ISO files and new cloud images, wey dem build from the archive as e be that week. And the version string change: lsb_release -a begin report 26.04.1 LTS where e report 26.04 LTS before.

Everything else don already dey your system. Ubuntu dey publish fixes continuously into the -security and -updates pockets of one suite, resolute for 26.04 and noble for 24.04. Point release na snapshot of that update stream. No separate destination dey wey you need move go.

Wetin make your patched server no get anything to download

Na one small package dey hold the point number. Run this:

lsb_release -a
dpkg -S /etc/lsb-release

dpkg -S answer base-files: /etc/lsb-release. The base-files package dey release the files wey hold your version string, so when dem publish one point release, new base-files dey enter the -updates pocket and your next sudo apt upgrade go install am. Na that one package be the complete visible effect of point release for machine wey dey run. You don install everything else inside am weeks ago as ordinary updates.

One common way wey machine fit fall behind dey. The default /etc/apt/apt.conf.d/50unattended-upgrades dey enable -security origin for its Allowed-Origins block and leave the -updates line commented out. So machine wey dey use automatic updates alone go take security fixes but skip the rest. That machine go continue report older point number for months. E correct to do so because e truly no get those packages. Open the file and check which lines get comment: how unattended upgrades dey configured for Ubuntu explain that block line by line.

When de next point release land

Learn the pattern, no be the date. The first point release for an LTS dey come some months after the original April release, and the ones wey follow am dey come roughly every six months, as each interim release dey come out. Dates fit change. Canonical announce say the first 26.04 point release go come at the beginning of August 2026, then dem move am later. This one dey happen normally and e no be warning sign. Get the date from the Ubuntu release cycle page or the 26.04 LTS release notes, instead of any article, including this one.

Why 24.04 no dey show 26.04 until the first point release

Because upgrade prompt dey configured to wait, and you fit read that configuration for your own box.

cat /etc/update-manager/release-upgrades

[DEFAULT]
# never  - Never check for, or allow upgrading to, a new release.
# normal - Check to see if a new release is available.
# lts    - Check to see if a new LTS release is available.
Prompt=lts

The comments for the shipped file long pass this excerpt, and e worth reading everything. Prompt=lts na the default for an LTS install, and e get two jobs: e limit the offer to LTS releases, and e send the check go another list.

Dem name that list for a second file:

cat /etc/update-manager/meta-release

URI point to https://changelogs.ubuntu.com/meta-release, and URI_LTS point to https://changelogs.ubuntu.com/meta-release-lts. With Prompt=lts, the upgrader reads the LTS list, and the new LTS no dey show there as upgrade target until e get first point release. Fetch the list and check am yourself:

curl -s https://changelogs.ubuntu.com/meta-release-lts | tail -40

Each release na one block of Dist:, Version:, Supported: and UpgradeTool: lines. The upgrader need that block before e fit offer anything. Canonical talk the same rule plainly for the 26.04 LTS release announcement: users of 24.04 LTS go get automatic upgrade when 26.04.1 release.

So for 24.04 server before that point:

sudo do-release-upgrade -c

Checking for a new Ubuntu release
No new release found.

That result healthy; e no mean say anything don break. When the path open, the same command go name the release, and the same message go show for the login banner:

New release '26.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

Notice the version wey e name. You no dey upgrade to 26.04, then upgrade again to 26.04.1. You upgrade once and land for the current state of 26.04.

Two other things fit make that check return empty: Prompt=never, wey some provider images set, and proxy or mirror wey no fit reach changelogs.ubuntu.com. Another message, Please install all available updates for your release before upgrading, mean say the check succeed and the upgrader want a fully patched starting point. when do-release-upgrade report say e no find new release explain the remaining causes. When the path open and you ready, the 24.04 to 26.04 upgrade itself na separate job with its own preparation.

The -d flag point the same check to the development list, na so people dey move before the path open. The wait get reason: na the period wey dem dey fix upgrade blockers wey early users report. For server wey you rent and depend on, na good reason to let the wait do its work.

Wetin hardware enablement kernel mean for VPS

An LTS dey ship one kernel for im whole lifetime, the GA (general availability) kernel, and e dey offer another rolling track wey dem call HWE (hardware enablement). HWE track dey come through point releases, and na the only part of point release wey truly get new code instead of just repackaging wetin you already get.

24.04 na the example here. E ship with kernel 6.8 and e go keep 6.8 for GA track throughout the full five years of standard support. HWE track start from the second point release: 24.04.2 bring the 6.11 kernel from Ubuntu 24.10, and 24.04.3 bring 6.14 from Ubuntu 25.04. As of August 2026, na this pattern dem don establish, and 26.04 follow the same structure.

The track wey you dey use show for package name:

uname -r
apt list --installed 2>/dev/null | grep -E '^linux-(generic|virtual|image|kvm)'

linux-generic na GA track. linux-generic-hwe-24.04 na the rolling one. Desktop installs dey default to HWE, while server installs dey default to GA. But provider images for VPS fit use another narrower option, like linux-virtual or cloud-specific linux-kvm. Check instead of assuming, because the default depend on who build your image.

For rented virtual hardware, hardware enablement mostly no concern you. Your server dey see virtio devices, plus the paravirtualised network and disk interfaces wey the hypervisor present. Those drivers don dey stable inside the kernel for over a decade. New laptop need HWE. VPS almost never need am. Wetin newer kernel actually give you here na kernel features: newer io_uring and eBPF work, or filesystem fix wey you get specific reason to want. wetin new for Linux kernel 7.1 na the way to decide whether any of those things worth the churn.

The cost na reboots and risk. HWE meta package dey pull new upstream kernel roughly every six months, so you accept kernel jump and reboot on that schedule. Out-of-tree modules wey DKMS build, especially ZFS, fit fail to build against the new version, and you fit discover am during boot. Each kernel still leave the previous one behind, and na so small /boot fit full up. Read how to remove old kernels from full /boot and how to choose which kernel your VPS go boot before you need dem, instead of waiting until after.

To move to HWE track, na one command and one reboot:

sudo apt install --install-recommends linux-generic-hwe-24.04
sudo reboot

uname -r after reboot suppose report the newer version. No remove the previous kernel until you don boot the new one and check your services. If the new kernel no boot, recovery na to select the older entry from boot menu, and that entry must still dey there. If e no dey, you don enter how to recover VPS wey no boot after kernel update territory.

Another -edge variant of the HWE package dey take the next kernel before the point release. Na for testing. Leave am alone for server.

The normal answer for rented server na GA kernel: one kernel version for five years, with security fixes backported to am throughout the whole period and no scheduled version jump. Move to HWE when you fit clearly name the feature wey you need.

Fresh install wey you do today no be the same as one wey you do last month

Images dey rebuild more often than point releases dey happen. Ubuntu dey publish cloud images wey get serial stamp, and each provider dey refresh im Ubuntu templates according to im own schedule. So two servers wey you create six months apart from the same menu entry fit boot different kernel versions and start with different package versions. None of dem wrong.

This matter pass as e dey sound. Runbook wey talk say make you run five commands after installation dey quietly assume starting state wey no longer dey exist. Check lsb_release -a and uname -r for every box instead of trusting the label wey you click, then define the end state for code so the starting state no go matter again. one first Ansible playbook for VPS na the smallest useful version of that.

Move for point release now, or make you wait?

• If you don already dey on 26.04, no place dey to move go. Continue to take updates, and the point number go follow by itself.
• If you dey on 24.04, standard support go reach April 2029, so waiting no cost much. The first point release na opportunity, no be deadline.
• Upgrade one copy first. Take snapshot of the server, or rebuild the same stack for throwaway VPS, run the upgrade there, and measure how long e take.
• If na newer kernel you want instead of newer release, HWE track go give you that for 24.04 without any LTS upgrade.

The wider question of which release you suppose use dey covered for LTS versus interim releases for server.

Wetin to check for your own box

lsb_release -a
uname -r
grep -v '^#' /etc/update-manager/release-upgrades
sudo do-release-upgrade -c

Healthy result suppose look like this: lsb_release -a go report your release together with the current point number, uname -r go match the kernel track wey you mean to use, Prompt=lts dey present, and the check either find nothing or name the release wey e go offer. Anything wey different deserve make you understand am before upgrade, instead of during the upgrade.

FAQ

I need do anything when point release like 26.04.1 come out?

No, as long as the server already dey on that release and e dey receive updates. Point release dey put updates wey dem don already publish inside new installation media. Running machine dey receive the same content through apt upgrade as dem publish am, and version string for lsb_release -a dey change when base-files package update. No separate release dey to move go, and no need reinstall.

Why my server still dey report older point number after apt upgrade?

Most times, na because automatic updates dey limited to security fixes. Default /etc/apt/apt.conf.d/50unattended-upgrades dey enable -security origin and leave -updates line commented out, while base-files package wey carry version string dey come through -updates. Run sudo apt update && sudo apt full-upgrade by hand and check whether base-files dey for the list. If e dey listed as kept back, something dey pin or hold am.

Why dem no dey offer 26.04 for my 24.04 server?

Because Prompt=lts inside /etc/update-manager/release-upgrades na the default for LTS, and e dey check LTS list for https://changelogs.ubuntu.com/meta-release-lts. The new LTS no dey show as upgrade target until the first point release. Until then, sudo do-release-upgrade -c dey print No new release found., and that one correct. The wait deliberate: na the period wey dem dey use fix upgrade problems wey early users find.

I suppose install HWE kernel for my VPS?

Most times, no. Hardware enablement dey support hardware wey new pass the release, while VPS dey present virtio devices wey their drivers don dey inside kernel for years. GA kernel dey stay for one version throughout the LTS life, with fixes backported to am. Use HWE kernel when you fit name the kernel feature wey you need, and accept say you go then get kernel jump and reboot roughly every six months.