Microsoft recently released the classic second Tuesday of the month patch, an update that has reached Windows 10 and Windows 11, and to no one’s surprise is giving troublealthough at the moment it seems that they only affect the latter operating system, since no cases of the same error have been reported with Windows 10.
I put you in situation. When you install this update, Windows 11 gives rise to a bug that causes the Malwarebytes security solution to identify Google Chrome as malware, and therefore proceed to block it. The browser will be listed in the task manager, but we will not see anything on the screen.
Does this problem have a solution? Yes, but it’s more of a “fix”, in quotes because for those who have been using Malwarebytes and who opted for the paid option it doesn’t really fix anything, as they have no choice but to uninstall said antivirus solution. This is the only one that really works in all cases.
A Malwarebytes employee confirmed that they are investigating the issue, and provided other possible solutions that seem to work in certain cases. These go through configuring Google Chrome as the default browser, disabling the Google Chrome application protection box in the protected applications section, which we can reach through the route “Settings > Security > Exploit Protection > Protected Applications”.
Some users say that directly disabling exploit protection works too, but by doing this we’re generally giving up an important Malwarebytes security feature, so it’s best to limit it to Google Chrome. Obviously you can also temporarily change browser to weather the storm until Microsoft fixes this problem.
Microsoft hasn’t said when it plans to fix this bug, but we imagine that the solution should arrive soon and that it will do so in the form of a patch. If the basic configuration solutions do not work for you, I would recommend you temporarily resort to another browser, since of all that we have seen, it is the fastest and easiest option, and we can also consider it the “least bad”.
It goes without saying that this problem does nothing more than show that Microsoft still has not settled the account it has pending with the Windows 11 updates, since they continue to arrive with important problems that in the end They affect the user experience significantly.
