@fadege Could you provide a screenshot with details, especially if that warning is shown for the CMS core or for a 3rd party extension, and what the tooltip shows which you get when you hover over the "1 Problem" badge? Without this information it is not possible to know what the database problem is. Thanks in advance.

@richard67 Thanks. The warning is for a CMS core extension: "System Information" (com_admin, extension_id 2, type component, client Administrator). Third-party extensions (Akeeba Backup) and "Joomla CMS" (files_joomla) show "No Problems".

Tooltip of the "1 Problem" badge (backend language Italian, translated):

• Database update version (4.0.0) does not match System Information version (6.2.0).
• 5 database changes were checked.
• 45 database changes did not alter table structure and were skipped.

Columns in the list: Database Version 6.2.0-2026-09-15, Manifest Version 4.0.0.

@fadege The CMS core is the "Joomla CMS" record, whis is ok. The 2nd record with the problem should not be there for the core, so either it is a 3rd party extension which unfortunately uses the same name as the core com_admin, or something else is wrong with that site.

@richard67 Thanks. I checked the database of this site directly (read-only SELECT on #__extensions):

• com_admin exists once (extension_id 2, type component, client_id 1, protected = 1, locked = 1, enabled = 1).
• Its manifest_cache shows: author "Joomla! Project", authorUrl "www.joomla.org", creationDate "2006-04", copyright "(C) 2006 Open Source Matters, Inc.", version "4.0.0", description "COM_ADMIN_XML_DESCRIPTION".
• There is no other extension with the name or element com_admin (265 rows in #__extensions in total).
• #__schemas has extension_id 2 = 6.2.0-2026-09-15, the same as extension_id 247 (files_joomla).

So it does not look like a 3rd-party extension using the same name. Is there anything else I should check on this site?

@fadege Hmm, I remember now. In very old times, the core used the "com_admin" extension for the database schema. Later that was changes to the "files_joomla" extension. The latter could be a remainder from a long update history. I think you can just delete the record with extension_id = 2 from the #__schemas table, then it should be all ok.

@fadege Hmm, I remember now. In very old times, the core used the "com_admin" extension for the database schema. Later that was changes to the "files_joomla" extension. The former could be a remainder from a long update history. I think you can just delete the record with extension_id = 2 from the #__schemas table, then it should be all ok.