Performance Issue with Windows 10 2004

[bdubrow]

Hi all--

We are aware of an issue with Windows 10 2004 and Malwarebytes that can lead to performance problems.

This seems to be related to conflicts with our Ransomware Protection.

Please see this Knowledge Base article for additional information.

We are actively investigating, and have recently been able to reproduce the issue in-house. We hope to narrow down the root cause shortly. 

For now, here's our recommended mitigation suggestions:

• Delay upgrading to Windows 10 version 2004 until a fix is available.

• Reboot your system.

• Perform a clean reinstall of Malwarebytes with our Support Tool by following the instructions in this FAQ.

• If none of the above resolve the problem on your machine, then you can temporarily disable Ransomware Protection by toggling the switch in the Real-Time Protection card to Off.

To verify which version of Windows 10 you have installed:

• Press the Windows Key + R on your keyboard at the same time.
• Type winver and click OK.
• View the displayed version number. Computers affected by this issue will have "Version 2004" displayed.

We'll post updates to the situation on this thread, as available.

Edited July 6, 2020 by LiquidTension
Added winver steps

[bdubrow]

Hello--

We have just released a new beta version that intends to address the performance issues that can occur with Ransomware Protection enabled on Windows 10 2004.

Please see this post in our beta forum for more information.

You can opt in to receive beta updates by launching Malwarebytes 4, going to Settings > General > Beta updates and then toggle the switch so the setting is enabled.

After you've opted in to the beta updates, manually check for updates from that same screen: Settings > General > Application Updates and then click the Check for Updates button. 

If you have any questions or feedback on this fix, please post in the beta forum.

We're very hopeful that this update resolves the issue.

Thank you all for your patience while we worked to resolve this issue!

[bdubrow]

Further update on this...

After very positive feedback from our beta, we have officially released this update with the fix to general availability. 

Please see this post for details.