How to Compare Joomla Files After a Failed Update
Preserve evidence before replacing files
Record the exact update error and preserve relevant PHP, web-server, and Joomla logs. Take a backup or snapshot of the failed state when practical. File comparison is diagnostic; it should explain what differs before anything is overwritten.
Identify the exact target release
Confirm the Joomla version you started from and the version the update intended to install. Obtain the official package for that exact target release from Joomla's official distribution channel and verify its published checksum when available.
Separate core files from site-specific files
Focus on paths that belong to the official Joomla package. Expect legitimate site-specific files such as configuration.php, uploaded media, logs, caches, extensions, and templates to differ. Do not delete a file merely because it is absent from a clean core package.
Use hashes or recursive comparison
Compare relative paths, sizes, and cryptographic hashes between the failed site and a clean copy of the exact target release. Deliberately exclude known writable and site-specific locations and save the difference report. This is more reliable than visually browsing hundreds of files.
Interpret differences carefully
A missing expected core file can indicate incomplete extraction. A changed core file can reflect a partial update, local modification, or compromise. An unexpected file is not automatically malicious or obsolete; identify its owner before removing it.
Check the database too
A failed update can leave files and schema at different stages. When Administrator remains usable, open System → Maintenance → Database. Joomla documents that normal updates apply schema changes automatically and that this screen detects structural mismatches after incomplete updates.
Prefer supported recovery
If comparison shows a partial core update, follow Joomla's supported update/recovery path or restore the known-good pre-update backup and retry after fixing the cause. Hand-copying selected files can leave an internally inconsistent installation even if the homepage loads.
Re-test the consistent site
After restoration or a clean update, verify the Joomla version, database structure, Administrator, frontend, extensions, template overrides, scheduled tasks, and logs. Keep the comparison report with the incident record.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.