![]() ![]() ![]() In a small number of cases, a reboot or restart of the Malwarebytes service might be required to re-enable the protection modules. The majority of Malwarebytes 3 users with automatic updates enabled recovered from this situation automatically. Simultaneously, we resumed normal database update deployment. We then fixed the issue on the database processing pipeline and published an updated database package with version number posted to our servers at 8:49AM ET. Upon confirming the issue, we immediately paused updates (at 7:31AM ET) to prevent further corrupted updates from being sent out to any Malwarebytes 3.x customers. We have also confirmed that this problem only affected 64-bit packages starting with Update Package Version published at 5:04AM ET, which was validated by our telemetry. Malwarebytes Anti-Malware 2.x users were not impacted by this incident.ĭuring the investigation, we identified that the root cause of the problem was by a database publish processing error that caused certain Malwarebytes 3 incremental database packages to be built incorrectly, causing the symptoms mentioned above. On May 19, 2017, we received reports from Malwarebytes 3.x users that Malware and Web Protection modules disabled themselves and any attempted scans stopped almost immediately after starting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |