[German]Malwarebytes has updated its software to fix the deactivation of Windows Defender under the Windows 10 May 2019 Update (V1903). That's the good news. The bad news: This issue has been reported in April 2019 – it took until July 2019 to fix that.
Malwarebytes improved for Windows 10 V1903
Users of Windows 10 version 1903 found that Malwarebytes (Premium) was not compatible. I wrote about it in the German blog post Windows 10 V1903: Malwarebytes deaktiviert den Defender. Normally, Malwarebytes works well alongside Windows Defender – even though the software can act as a virus protection.
When upgrading to Windows 10 version 1903, Malwarebytes' security software suddenly deactivates Windows Defender. Since the first week in June 2019, the Malwarebytes forum has had the article MBAM disables Windows Defender after WinUpdate 1903 installed, which addresses this issue.
Malwarebytes had only suggested a workaround (in the Malwarebytes settings the option Change Malwarebytes to never register should be set in the Action Center). However, Malwarebytes had also released Beta 3.8 to fix the issue.
Malwarebytes fixes Windows Defender deactivation bug in Windows 10 1903 #malwarebytes #windows10 #securityhttps://t.co/QUKEcIXQiL pic.twitter.com/YtYDva08H7
— ghacksnews (@ghacksnews) 1. Juli 2019
Now Martin Brinkmann reports on ghacks.net (see tweet above) that this fix is apparently present as Malwarebytes 3.8.3 and should solve the problem of the deactivated Windows Defender under Windows 10 V1903.
Are Microsoft and Malwarebytes are stubborn?
While the issue with Malwarebytes 3.8.3 is fixed, German blog reader Karl comes up with massive criticism of Malwarebytes.
@etguenni das nennt man verbohrt #Malwarebytes schon vor dem Release reported auch an Microsoft und jetzt hat man es analysiert. Ich habe Stunden mit dem Forum Support verbracht.https://t.co/5Ox7VmNdIs
— al Qamar (Karl Wester-Ebbinghaus) (@tweet_alqamar) 29. Juni 2019
The tweet above says:
@etguenni this is called stubborn #Malwarebytes even before the release reported to Microsoft and now it has been analyzed. I spent hours with the forum support.https://t.co/5Ox7VmNdIs
The above issues were apparently reported by Karl to Malwarebytes / Microsoft early before the release of Windows 10 V1903. The Malwarebytes forum entry here is dated from April 25, 2019 and deals with the issues of Malwarebytes 3.7.1 in connection with Windows 10 1903 (Release Preview) 18362.52. I would say: You users are still the guinea pigs who have to pay for this.
