This article below by MB:
https://support.malwarebytes.com/hc/en-us/articles/360039579393-Windows-XP-and-Vista-compatibility-with-Malwarebytes-AdwCleaner
hints that "Versions before 8.0 may still work on a Windows XP", emphasis (mine ) put on "may"... FWIW, I have local records kept that indicate that the XP_EoS version of Malwarebytes AdwCleaner is/was v6.047 :
There doesn't exist a GUI button to update the "database", only an "option" to use the "local" or the "server" one:
I did perform a quick scan with the default setting of "server"; I had to open the log file to, sadly, find out that only the extremely outdated "local" database was used for the scan:
# AdwCleaner v6.047 - Logfile created 26/04/2023 at 00:25:03
# Updated on 19/05/2017 by Malwarebytes
# Database : 2017-05-19.1 [Local]
# Operating System : Windows Vista (TM) Home Premium Service Pack 2 (X86)
# Username : (redacted)
# Running from : (redacted)\adwcleaner_6.047[XPEOL].exe
# Mode: Scan
# Support : https://www.malwarebytes.com/support
I don't have an XP machine available currently to check whether v7.4.2 does, indeed, launch there ; that version does launch under Vista SP2 x86 - incidentally, it offers to update the app to v8.4.0, but that offer should be declined, as (consistent with the article I linked above) that one doesn't launch under Vista (so why offer it in the first place? ) ...
Like its predecessor, v7.4.2 has a default setting of "Automatically using the cloud database if available":
I performed a second scan with v7.4.2, its log file now reads that it used a "database" from Oct 10th 2022, i.e. a stale one from 6 1/2 months ago (!) :
# -------------------------------
# Malwarebytes AdwCleaner 7.4.2.0
# -------------------------------
# Build: 10-21-2019
# Database: 2022-10-10.1 (Cloud)
# Support: https://www.malwarebytes.com/support
#
# -------------------------------
# Mode: Scan
# -------------------------------
# Start: 04-26-2023
# Duration: 00:00:35
# OS: Windows Vista (TM) Home Premium
# Scanned: 32074
So, I don't know what to make of that , certainly can't answer whether that is considered as "definitions still provided for it" ; "use at your own risk" would be my advice ...