Take that with lots and lots of salt, though it makes some sense in that one of the suggestions from Malwarebytes is to change Chrome to be your default browser. Interestingly, there’s a claim that Malwarebytes isn’t the only antivirus vendor affected, and an ESET user reckons they have encountered it – and that the problem is caused by having any other Chromium browser set as your default (such as Microsoft Edge). It’s worth a shot, though, seeing as this is a workaround which won’t hinder your level of security with Chrome (turning off exploit protection certainly does). However, a couple of reports in the customer support thread suggest that this didn’t make any difference. There is one other workaround suggested by Arthi, and this is to set Chrome as your default browser in Windows 11 (if it isn’t already, obviously).
That should be soon enough, given that the cure is already in beta as mentioned. If that makes you uncomfortable, the only other path is to uninstall the Windows update (KB5027231) and live without it until the security company provides a full fix. Obviously that still isn’t ideal, as Malwarebytes will no longer be protecting Chrome against exploits. Then find Google Chrome in the list of apps and turn off the protection slider.
To do this, go to Settings, and the Security tab, and under Exploit Protection, click the ‘Manage Protected Applications’ button. That is to turn off Chrome as a protected app in Malwarebytes. Some people have simply turned off Malwarebytes Exploit Protection, but that leaves you vulnerable as you might imagine, and there’s a more targeted fudge as provided by another staff member at the company, Arthi. The good news is that if you don’t want to switch to the beta of Malwarebytes – and let’s face it, most folks won’t (beta software may well have problems of its own) – there is a workaround which has been successfully applied according to numerous reports. A further update to that post notes that there is a fix now in the beta of Malwarebytes 4.Īnalysis: There is a fudged workaround, too
0 kommentar(er)
