![]() ![]() Over the next few weeks, we'll be actively working on a permanent solution to re-enable the setting and completely resolve the conflict between Google Chrome and Anti-Exploit. To confirm this update, simply visit your policy page and check for the changes under Protected Applications in Exploit settings. We have a temporary fix in place to automatically resolve the conflicts with Google Chrome and we'll be deploying this today, June 15th, 2023, from 18:30-20:30 UTC.Īs part of this fix, we'll be migrating the policies to disable "Google Chrome" in the Protected Applications section of Exploit settings. If you want to get a beta version of this build early, you can follow the beta instructions above. Next week, we're targeting to release another update that will both re-enable anti-exploit protection for Chrome and ensure the conflicts are fully resolved. Open Malwarebytes -> look for the Settings gear in the top right -> About and look for these: You can verify you've got the right update package version by doing this: This patch will automatically roll out to Windows 11 users only via Update package version 4 when the product checks for updates - by default this check is performed on an hourly basis. This is only meant to be a temporary fix so that users are able to launch Chrome again. The temporary fix will automatically disable anti-exploit protection for Chrome as suggested in the knowledge base article we published yesterday. We have released a temporary fix to automatically resolve conflicts with Chrome in Malwarebytes 4 Premium and Teams. Thanks for your patience as we work through this. More on that as soon as it's ready.įor now, continue to use the same KB from earlier: We've got a policy change in testing right now and we're targeting to release this tomorrow. If you do not want to use the beta build, you can continue to use the same KB from earlier: To verify you're on the correct beta build, go back to Settings -> About and look for these: Then, go to About -> Check for updates and follow the updating prompts ![]() Open Malwarebytes -> look for the Settings gear in the top right -> General -> scroll down and enable beta updates We've got a fix ready via a beta build as well as we're working on something a bit more automated and we'll share that tomorrow. Want to share an update on where we're at with this issue and what you can do right now to resolve the issue. Endpoint Detection & Response for Servers ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |