Cant upgrade to the next lts 24.04.2 to 24.04.4

Ubuntu Version:
24.04.02

Desktop Environment (if applicable):
VM command line
Problem Description:
Describe what you’re trying to do and what happens instead.
When I try to get updates or upgrade to the next lts, I get no upgrades available.

Example:

root@xxxxx:~# apt update && apt upgrade
Get:1 Index of /ubuntu noble-security InRelease [126 kB]
Get:2 Index of /ubuntu noble-security/main amd64 Components [21.5 kB]
Get:3 Index of /ubuntu noble-security/restricted amd64 Components [212 B]
Get:4 Index of /ubuntu noble-security/universe amd64 Components [52.2 kB]
Get:5 Index of /ubuntu noble-security/multiverse amd64 Components [208 B]
Fetched 200 kB in 1s (143 kB/s)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
All packages are up to date.
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@xxxxxx~#

Relevant System Information:
I access the vm thru putty.

What I’ve Tried:
sudo apt dist-upgrade

Thanks
I appreciate the help.

I see a number of problems…

  • firstly we’re some time away from Ubuntu 24.04 LTS reaching the 4th point release; that’s expected early 2026; but that was probably a typo
  • your listing shows either you’ve removed items OR your sources aren’t completed; with many sources disabled for some reason, and this would explain your issue…

I see only noble-security without mention of noble-updates for example… I’d thus ensure you have noble-updates source enabled on that system.

Next, though this is less of a problem, but there are cases where apt upgrade will NOT install all updates; as there are times where packages need to be removed in order for the upgrades to be applied; which is why apt full-upgrade exists (you do mention apt dist-upgrade which will achieve this though*). This though is not your issue currently as you have “0 not upgraded” listed, your issue is sources disabled most certainly.

An example of what I see on my questing box is

Get:13 http://security.ubuntu.com/ubuntu questing-security/restricted amd64 Components [212 B]
Get:14 http://security.ubuntu.com/ubuntu questing-security/multiverse amd64 Components [212 B]
Get:15 http://archive.ubuntu.com/ubuntu questing-updates/main amd64 Components [208 B]
Get:16 http://archive.ubuntu.com/ubuntu questing-updates i386 Contents (deb) [11.2 kB]
Get:17 http://archive.ubuntu.com/ubuntu questing-updates amd64 Contents (deb) [136 kB]
Get:18 http://archive.ubuntu.com/ubuntu questing-updates/universe amd64 Components [212 B]

ie. I’m seeing not just security, but also updates as I have them enabled, so I can apply upgrades on my questing or 25.10 system.


FYI: If you purposely disabled all updates excluding security, then of course you’ll not get all upgraded packages, which will include the package base-files which is what will update your release version details, ie.

 base-files | 13ubuntu10.3   | noble-updates   | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x

contains the detail that reports a 24.04 system as 24.04.3

Also a Ubuntu 24.04 LTS system is a noble or 24.04 release, the point release detail just shows upgrade level & is mostly relevant in relation to new ISOs

As usual, this point release includes many updates and updated installation media has been provided so that fewer updates will need to be downloaded after installation.

Welcome to Ubuntu Discourse :slight_smile:

Just to add to what @guiverc already mentioned, let’s see the output of the following commands:

inxi -r
inxi -S

Please highlight the output and wrap with code tags either by using the </> icon in the composer or pressing Ctrl + E on the keyboard.

Thanks

Thanks for the answer
Here is the output
<
root@xxxx:~# inxi -r
inxi: command not found
root@xxxx:~# inxi -s
inxi: command not found
root@xxxx:~#

Thank you for the answer,

I sort of remember after the installation, having issues * not able to upgrade* so i did set up a source to get it. I have other VMs that have upgraded to 24.04.03 and keep getting updates. How could I fix it so that It gets all the updates?

You mentioned a release (24.04) but didn’t give product details (ie. Server, Desktop etc)

If a desktop system, opening Software Sources and simply selecting the Ubuntu Software tab should let you see the various components; ie. main, universe, restricted, etc. I always check that first. However if you click the Updates tab you’ll have various options there which can be enabled or disabled by click. On my system I have security updates, recommended updates, and even unsupported updates all enabled… You’ll likely find you have only the Security updates having a tick there; thus click to enable what you want.

If you’re using a Server system (you did mention VM command line so it maybe you’re using a Server install), I’ll provide my own file as an example… I’d actually vim /etc/apt/sources.list.d/ubuntu.sources but use whatever text editor you have installed (vi maybe isn’t the easiest for younger users)


# Automatically generated by Calamares on 2025-06-04.
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of Lubuntu.
## Ubuntu distribution repository
##
## The following settings can be adjusted to configure which packages to use from Ubuntu.
## Mirror your choices (except for URIs and Suites) in the security section below to
## ensure timely security updates.
##
## Types: Append deb-src to enable the fetching of source package.
## URIs: A URL to the repository (you may add multiple URLs)
## Suites: The following additional suites can be configured
##   <name>-updates   - Major bug fix updates produced after the final release of the
##                      distribution.
##   <name>-backports - software from this repository may not have been tested as
##                      extensively as that contained in the main release, although it includes
##                      newer versions of some applications which may provide useful features.
##                      Also, please note that software in backports WILL NOT receive any review
##                      or updates from the Ubuntu security team.
## Components: Aside from main, the following components can be added to the list
##   restricted  - Software that may not be under a free license, or protected by patents.
##   universe    - Community maintained packages.
##                 Software from this repository is only maintained and supported by Canonical
##                 for machines with Ubuntu Pro subscriptions. Without Ubuntu Pro, the Ubuntu
##                 community provides best-effort security maintenance.
##   multiverse  - Community maintained of restricted. Software from this repository is
##                 ENTIRELY UNSUPPORTED by the Ubuntu team, and may not be under a free
##                 licence. Please satisfy yourself as to your rights to use the software.
##                 Also, please note that software in multiverse WILL NOT receive any
##                 review or updates from the Ubuntu security team.
##
## See the sources.list(5) manual page for further settings.
Types: deb deb-src
URIs: http://archive.ubuntu.com/ubuntu
Suites: questing questing-updates questing-backports
Components: main universe restricted multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

## Ubuntu security updates. Aside from URIs and Suites,
## this should mirror your choices in the previous section.
Types: deb deb-src
URIs: http://security.ubuntu.com/ubuntu/
Suites: questing-security
Components: main universe restricted multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

Please NOTE I’ve provided my file ONLY AS EXAMPLE, as I’m using questing or 25.10, but I’m hoping you can use it to help you see what you need to change…

Key is the UPDATES bit of the file

Types: deb deb-src
URIs: http://archive.ubuntu.com/ubuntu
Suites: questing questing-updates questing-backports
Components: main universe restricted multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

Do you have noble-updates listed on yours?? Whilst you may NOT want backports and most probably also not deb-src too, and other stuff I have (my box isn’t a server!) but I’ve used my current desktop file here as example only.

Add whatever your system needs; be it a home machine, enterprise/production server etc… ie. adjust yours to get what you need only.

1 Like

Need to install it then.

sudo apt install inxi

Thank you
That helped me fix the problem.

1 Like

Thanks for all the help.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.