Perhaps I skipped the dodgy updates, because being free, I don’t having it running in the background updating all the time, and only use it on-demand. Trust lost is trust hard to re-gain, and this news has hardly helped.īut the free version in my VM, at least seems ok for now. But on my main host PC, something has just stopped me from letting MB come anywhere near it. In my VM, I trusted the later versions, but let it expire to “Free” only, and this has been fine and continues to be. The signature-updates worked fine until recently, and then started to fail, and just sit there and do nothing. It was very buggy at the time, and I removed it all and stuck with the original software for many months, re-instating Anti-Exploit and Anti-Malware as separate installs. My honest view on this….I lost a lot of trust in MB when they made the big change that took away Anti-Exploit beta, and rolled the whole thing into one larger package.
Now You: Were you affected by the issue? (via Neowin) Malwarebytes reacted quickly to the issue but it still took them two tries to get it right. Some users thought that Malwarebytes had been compromised, especially since some protective modules would not stay on or could not be turned on at all. If it is not, check for updates to install the most recent update package version and restart the computer afterwards to complete the installation.
In short: make sure that the update package version is at least version. The client could not process it correctly which caused the high resource usage on customer devices and protection issues. Malwarebytes CEO Marcin Kleczynski published an official statement on the issue on the Malwarebytes forum. Kleczynski explained that a malformed protection update caused the issue.
Malwarebytes staff suggests that users turn of Web Protection, run a check for updates and restart the PC afterward if the issue is not resolved automatically.
0 kommentar(er)
