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). 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 2: I was looking for a "Database Version" item - I had assumed the two "Package Version" items referred to program modules not Database updates. 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? In MBAM v2 the database version info was shown on the tooltip popup from the notification area icon and in the Dashboard display. 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". Does this mean that all database updates will cease for installed copies of MBAM v2.2.1 - as from that date?Ģ. The Home Products Lifecycle page appears to indicate that support for MBAM v2 will cease on the 8-June-2017. I have multiple Malwarebytes (Anti-Malware) licences - but I have been holding off on allowing the upgrade from v2 to v3 - basically waiting for the v3 product to become fully debugged and stable before swapping over.
0 Comments
Leave a Reply. |