Lately I have been getting notifications that the 2 databases (malware and phishing URLs) are out of date. When I press the update database button nothing happens. Can anyone help me with this please?
Malwarebytes database updates
Cannot "Clear Data' - nothing happens. Can only clear cache, which achieves nothing. Last update 13th Dec 2018 as displayed in Malwarebytes "Recently Used" Your Apps. It's now 29th Dec 2018. Pressing "Update database" does nothing. I have followed all above instructions. Please help.
Pinging data-cdn.mbamupdates.com [54.230.21.35] with 32 bytes of data:Reply from 54.230.21.35: bytes=32 time=111ms TTL=228Reply from 54.230.21.35: bytes=32 time=108ms TTL=228Reply from 54.230.21.35: bytes=32 time=109ms TTL=228Reply from 54.230.21.35: bytes=32 time=108ms TTL=228
The Protection Updates policy setting determines how often the Malwarebytes client polls our infrastructure servers for updates. Protection Updates are database updates, sometimes called protection rules updates, which are published roughly every hour and used by scans and Real-time Protection features.
Well hello i am using the version 2.2.1.1043 of Malwarebytes, and i tried to instal the latest version but it wouldnt work, so i tried to reinstal the previous version but it shows that the last database update was in 2016 and i would like to have the last one that was available in 2022, how can i do it ?This is the last version that i used to have
I tried and it have the same problem with the database, then i tried to update from the 3.5 version to 4, but it wont work, now i am gonna try to uninstal 2.2 version and mannually instal the 4 version
Well, sort of, yes. That file gives you database version 1893, which is pretty well out of date. I believe the latest database is something like 1979 or something like that. Basically the most recent manual update I can find thus far is too old. Anyone else know if there is a more recent manual update file?
Too bad as I sure do not desire to turn the Internet on a machine I am cleaning and installing Malwarebytes on till I am sure it's clean enough to do so. By allowing me to download the latest update manually, I can assure the computer is clean enough to now turn Internet on and register the product and download latest database.
1. The Home Products Lifecycle page appears to indicate that support for MBAM v2 will cease on the 8-June-2017. Does this mean that all database updates will cease for installed copies of MBAM v2.2.1 - as from that date?
2. I have run a few tests installs of the v3.1 product - and one thing I can't seem to find is any display of the currently installed database version number/date - it just displays "Current". In MBAM v2 the database version info was shown on the tooltip popup from the notification area icon and in the Dashboard display. Where is this info now shown?
When there is an issue with a false positive or bugged database update it was always possible in the past to state the database version you were using when reporting the problem - not sure how you would do this for v3.1 - where is this information now?
1. The Home Products Lifecycle page appears to indicate that support for MBAM v2 will cease on the 8-June-2017. Does this mean that all database updates will cease for installed copies of MBAM v2.2.1 - as from that date
A Malwarebytes staffer may weigh-in with updated facts to the contrary but unless I miss my guess, it is safe to say that users would receive a much more publically published advisory, that supplements the "Life Cycle" information, if those databases were going to terminate soon. Please remember, databases are still being published many times daily for even the consumer version of MBAM 1.75.0.1300.
Re question 2: I was looking for a "Database Version" item - I had assumed the two "Package Version" items referred to program modules not Database updates. Will look at this again on a live system - where I assume the Update Package Version should change multiple times a day if it is in fact the Database version number.
Re question 1: The "End of Life" date in the linked Lifecycle page is shown as the 8th June 2017 for BOTH v1.75 and v2.2.1 (and v3.0.4) - so the implication would be that all these versions cease to get updates as of that date (the "End of Maintenance" date shows as December 2016 for all three). I assumed this was a heavy handed way of forcing everyone onto v3.1 - which is fine if that version is stable and de-bugged for all OS platforms and security package combinations. But could be a problem for those of us still using older OS's and/or combining Malwarebytes v3 with less popular security packages. MBAM v2.2.1 works well on older slower systems and plays happily with most other security packages - I am yet to be convinced about installing v3.1 onto these types of systems - so the June 2017 date is a concern.
The December 2016 date was the "End of Maintenance" date for Malwarebytes Anti-Malware 1.75-2.x which meant we were no longer updating the program or pushing out fixes. You still would get database updates, now called Update package version in Malwarebytes 3.
If you are using an older version of our software that is past its End of Life date, technical support will be limited to help with upgrade to the latest version, or migration to a comparable Malwarebytes product, if applicable. We will continue to answer common product questions, and any existing self-help resources will still be available. You may continue to use the older product version at your own risk, but ongoing protection updates are not guaranteed.
I just asked our Product Manager and he said Malwarebytes 1.75-2.x will continue to get database updates after the June 8 date for now while we continue to migrate users over to 3.1, but like the End of Life policy states, "ongoing protection updates are not guaranteed". I do not know what date the team will decide to turn off database update for the older Malwarebytes Anti-Malware versions.
OK so to summarize that very comprehensive reply from Celee:1. Database updates WILL continue after the June 8th ("End of Life") date for MBAM v1.75 and v2.2.1 - however there is no guarantee as to how long that will continue.
The database version is just a bunch of random numbers, they have no meaning whatsoever to anyone other then Malwarebytes. The current system of using dates to identify datbase versions makes sense. Why in the world did they move away from it? We are supposed to trust MBAM that we are up to date when we could have used the dated database version to verify. An extremely stupid change imo and not one person from MBAM has commented about it.
If you go to C:/Program Data/Malwarebytes/MBAMservice folder it will show the latest update files and open dbupdate.log and it will list all your updates. My last updated was 30 min ago at 4:30 PM CST.
Phone Man, on MBAM2 I don't have to go to C:/Program Data/Malwarebytes/MBAMservice to see what the latest MBAM update is. All I need to do is mouse over the MBAM icon in the service tray. It will immediately tell me the program version and the database version. It's a lot simpler and faster than what you apparently have to do. I don't understand why MBAM has moved away from this simplicity and speed. Also, I'm very much in agreement with what bru and Doug Cuk have said about the much more obscure and less useful naming of database files in MBAM3. When I mouse over the MBAM icon, I'm told what the latest database file is in a way that's easy to understand. I just did that, and I'm told it's 2017.6.3.4, so I immediately know that I've got the 4th version of the database file created on June 3, 2017. In contrast, telling me that I have "Update package version 1.0.2043" tells me nothing except that in moving to MBAM3, the company has mysteriously chosen obscurity over clarity. I strongly hope they will rethink this decision. 2ff7e9595c
Comments