Ah, ok, that helped to clarify.
To restated what I'm seeing -- you have an Ubuntu 22.04 that you recently update to 24.04. The new 24.04 is now showing after the asset is rescanned.
The re-scanning of the asset may not scan all of the information upon each and every scan. To ensure the asset is fully rescanned, manually trigger a re-scan of the one induvial asset. If you allow the asset to be re-scanned based on a scan target's schedule, the OS version may not be scanned. It *should* be scanned every time, but a schedule scan may only scan it 1x per day. Manually scanning will force a 100% re-scan of everything on that asset.
See if that helps. Then, after it's scanned, it shouldn't take long to re-sync and update the cloud with the new OS version.
Please keep us posted how things go for you.
Tim N.
Lansweeper Employee