End of Life will be exactly 6 months from the End of Maintenance Date for Home applications, and 12 months from the End of Maintenance Date for Business and Technician applications. End of Maintenance for this version will coincide with the Effective Date of the Lifecycle Policy. † The End of Maintenance and End of Life Milestone dates for this product/version were not communicated publicly prior to the Lifecycle Policy effective date. The last supported version for Windows Vista and XP is 3.5.1 which has not yet reached its EoL date: You can find the Malwarebytes Lifecycle info for 2.x on this page. The versioning is different in 3.x vs 2.x so it doesn't display the same number for the database version as it would in 2.x.Īs for the errors with 2.x, it is likely that since it's reached its End of Life date already that the update servers that used to provide the callback to the program that it was up to date (a checkin bit from the server if I recall correctly that would show what the latest DB version number is, and if it matches what's installed the program says that you have the latest version so they probably took that response offline since it doesn't apply to 3.x). To check the current database version you need to check the Settings> About tab, the database version is the third value listed as illustrated below: In order to terminate Malwarebytes via Task Manager you need to first disable the self-protection module located under Settings> Protection. However, I have not tested this with the v3.5.1 install so I don't know. But the "unable to access update server" still persists and now I'm asking WHY?Īlso note my point (2) on why I stay away from v3. Now, after trying and uninstalling v3.5.1, and reverting to v2.2.1 the program DB is v2019.02.23.02 as we speak. Before running the Support Tool the program DB was v2019.02.23.01. This is NOT the case with v2 which has saved my many days in case of MBAM v2 my screencaps in this thread. In case of MBAM crash and when I need to shut down program under Task Manager, mbam.exe process CANNOT be killed off (the process is locked somehow) and, unable to shut down the service, a new session of MBAM cannot re restarted. No DB version shown (only "up to date" status displayed even at taskbar icon level) Ģ. However, recalling from my negative experience with earlier v3.x versions I've decided to revert to v2.2.1 instead.ġ. Upon initial impression v3.5.1 seems to run OK. But you're wrong with the DB updates (see below). But instead of generating and submitting a log I clicked "Repair" which prompted the subsequent update to v3.5.1. However, accessing the site below shows the OK prompt:Ĭan someone tell me what's going on here? Is this an MBAM server problem? Can someone thought so, so I downloaded the Support Tool to check. To summarize, whenever I do a manual check for DB update, on instances when "no updates found": should've been displayed, MBAM now shows "unable to access update server" instead, which is misleading. (previously all DB updates were successful without any buggy messages like what is discussed here). But now every time the same actions is performed, the program only shows "unable to access update server" and it only occurs since Feb 23. ![]() Previously, when manually updating the DB, if there are no updates on the server the program would display "no updates found" then displays the most current DB version. (By contrast, with MBAM v3 there's no DB version being displayed, only "up to date" which is annoying) The "unable to access update server" message still pops up, but the program DOES update the DB with the progress bar moving, even from the v2.2.1's bundled DB dated 2016. So I uninstalled MBAM v3.5.1 completely and reinstalled v2.2.1 again (with valid license of course). Before submitting your reply, be sure to enable "Notify me of replies" like so:Ĭlick "Reveal Hidden Contents" below for details on how to attach a file: Please attach the file in your next reply. Upon completion, click a file named mbst-grab-results.zip will be saved to your Desktop. You will be presented with a page stating, " Get Started!"Ī progress bar will appear and the program will proceed with getting logs from your computer Place a checkmark next to Accept License Agreement and click Next You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Once the file is downloaded, open your Downloads folder/location of the downloaded fileĭouble-click mb-support-X.X.X.XXXX.exe to run the program ![]() NOTE: The tools and the information obtained is safe and not harmful to your privacy or your computer, please allow the programs to run if blocked by your system. ![]() If you haven’t already done so, please run the Malwarebytes Support Tool and then attach the logs in your next reply: Endpoint Detection & Response for Servers
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |