tylerg

I was just confused as to why an 5-year unsupported version of Malwarebytes receives working database updates (works on other computers). I was merely insinuating that the problem could be due to other factors.

Thank you AdvancedSetup. I will speak to management about letting us purchase a Nebula license for Malwarebytes v4.

Just to clarify, everything points to this version indeed getting database updates in 2023. Please do not reply with the arbitrary 'unsupported' before reading the whole post.

Malwarebytes Anti-Malware Corporate 1.80.2.1012, but issue replicates itself on Free (License-less) MBAM 1.75. This issue occurs: On Corporate: Corporate 1.80.1 downloaded and updated to 1.80.2, so program updating works. Database updating results in the title error. On Free: Attempts to update to Malwarebytes v4, then throws up the same error. I should disclose that database updating worked as of Jan 6, 2023. Both Free and Corporate had updated to a Jan 2023 database successfully, so this is not an instance of unsupported software looking for a dead host. This problem had also appeared for dozens of others (on this forum as well) while this version of the program was the primary supported version (before Malwarebytes v2) I have ruled out AV interference. Problem also occurs when Avast is disabled. Hosts file is not the issue either. We run offline Windows Vista machines, offline and online Windows 7 machines and online Windows 10 and 11 machines. Problem occurs on an online Windows 7 machine. Updating to Malwarebytes v3 or v4 is not an option, as archaic rules only let us use either v1 or v2. Since v2 does not receive database updates, we are limited to using v1 (which does receive database updates as of Jan 2023) This is not a serious problem either, as actual malware detection was identical across both v1 with Jan 2023 databases and the latest v4.