MalwareBytes Causes Windows 10 2004 Problems

[AxlSmithNotThatVideoGuy]

I had/have this too. It was totally pain. I had to e.g. revert back to Windows 1909 because I didn't know that it is Malwarebytes that after some time, halt almost everything  - some applications that I started first run quite alright for sometime (after a few hours the system was unusable) but cannot start any new application). Then yesterday I tried to 2004 update again because WU offer it as first time I used MediaCreationTool. Luckily I found this thread after some one pointed that this kind problems are always security programs based.

Malwarebytes should definitely offer update or some notification to user, if Malwarebytes detects Windows 10 with 2004 and old Malwarebytes Component package version and so on. If is not possible, Malwarebytes should send email to all paid user just in case.

Updating to 4.1.1.71/Update package version 1.0.25785/Component package version 1.0.961 help much, there was still some odd thing. Yesterday I tried to start command line I use (ConEmu) and it did not start. I thought that could not be true, again 😞 But then I exiting Malwarebytes and all ConEmu processes started, totally 3 ConEmu-window at once. So now on I know that, if something not start, I shutdown Malwarebytes. That ConEmu-problem is still only problem so far, and today it works with Malwarebytes on without any proplem.

Setting have already like recommended in post #6

This is for information only, I do not request any help.

[exile360]

Of the millions of Malwarebytes users, only a relatively small number of users are affected by this (I have Windows 10 with the 2004 update and never had any problems with Malwarebytes Premium, and the same is true for many of the helpers here on the forums, and of course Malwarebytes QA has tested with the 2004 update).  If impacted by the issue I would definitely recommend keeping an eye on the forums here for news on any releases and to keep your Malwarebytes up to date to ensure that you get the fix as soon as it becomes available.

[AxlSmithNotThatVideoGuy]

Well I have not have any problems with MBAM and Windows 10 updates before that. So? It means nothing. And of course developer should release information if it knows problems with, even with couple of users. It was hard way to find out that it was Malwarebytes that slows down almost anything. How many have problems but cannot find out that it is MBAM's fault, so we do not know anything here. So there might me more than we know here.

[exile360]

If a significant number of users are impacted by an issue they do generally create an FAQ entry or KB article of some kind, however I have never known of any developers that alerted all users any time there was any sort of known issue with their product, especially if only a small percentage of users are affected as users would end up constantly inundated with alerts about every bug and issue ever discovered in the product which wouldn't be helpful either since the frequency of alerting users each time there is an issue would result in users ignoring the alerts (and likely many users getting annoyed with it as well).

With all of that said, as a general troubleshooting step whenever a system is suffering from any kind of performance issue, testing to see if the resident security software is the cause should be one of the first things to test, at least based on my experience, not specifically with Malwarebytes, but with every security software I've ever used (including the built in Windows Defender/Microsoft Security Essentials).

Now that you have posted in a thread about this issue you should receive an email whenever there is a response to this thread, including once the issue is fixed and a member of the staff posts to inform the community that the issue has been fixed and that a new version is available which includes the fix.

[AdvancedSetup]

Please note that we have released a new beta today that we hope should address the issue with Windows 10 build 2004

If you're running Windows 10 build 2004 and were having an issue please try the new beta and let us know if this beta version corrects the issue or not.

Thank you