Syurba

Thank you for making this topic @Bertel. Similar to yourself I stopped using Malwarebytes last month (and plan to keep it that way) after spending countless hours trying to resolve issues caused by malwarebytes, as I commented in this other thread: The thing that has frustrated me the most about all of this is the terrible communication around these issues. From the threads that I have read, every time an issue like this comes up there's a workaround posted and if you're lucky they let you know "devs are working on fixing it". That doesn't really give me any confidence, especially when "devs are working on fixing it" and it has been months with absolutely no update. So I'm glad that @AdvancedSetup has at least given some sort of update about this particular issue in this thread. That post alone has more substance than the pinned "Performance Issue with Windows 10 2004" thread. Why hasn't that been updated with a similar update? The pinned thread from 2 weeks ago that says "We'll post updates to the situation on this thread, as available." has no updates... No update report in 2 weeks does not give me confidence in Malwarebytes. By the way, my problem wasn't caused by the 2004 update, and I don't know if my issue ended up getting fixed. I check the release page here: and I see: * June 17: Fixed: Certain MWAC BSODs under certain circumstances * July 1: Fixed: additional MWAC BSODs under certain circumstances Like ?????? I have no idea if this is related to my issue. Sure I had a BSOD caused by MWAC, but the same thing also caused audio stutter, PC freezing. Were they all fixed by this? And actually right as I type this I find: That says: "Fixed: Several Web protection BSODs and incompatibilities" Which seems like the more likely fix, but "stuttering" is not mentioned anywhere there, just "incompatibilities". You actually have to check @AdvancedSetup's post in another thread to link the two together: Would it really hurt to add some more detail to the release notes? Especially considering that issue has been around since at least February, which is when the thread above was created. I understand that it was only a beta release page, but given the lack of details on the non-beta release page, I honestly doubt any details would have been provided. And that's what frustates me the most. You have an issue from February, affecting many users, with a lack of updates (or updates scattered around in multiple posts because nobody will pin a thread for it), and when you do fix it 5 months later, you get a one line explanation, which is so vague you can't even tell it was related to the issue in the first place. In my case I spend tens of hours trying to debug the issue, suffered through reinstalling software from fresh windows reinstalls, swapping out hardware, and not to mention finding the time to do all that during WFH and what am I greeted with? "Devs are working on fixing it" while the issue has been going on for months with no meaningful update report, and then when it does get fixed I get absolutely no explanation about what happened. Why did I have to waste tens of hours trying to resolve this with absolutely no explanation as to what happened? How can I have confidence in Malwarebytes that it won't happen again when this is how you treat a customer who spends so much time trying to solve an issue caused by your product? How can I trust them anymore? I just can't.

Has there been any communication about this issue at all outside of the forums (e.g. email, or notification within the malwarebytes application)? Or any plans for rollback? I got a new computer around the time the update causing the issue was released, so of course I thought it must've been a problem with my hardware and didn't suspect malwarebytes at all. Tens of precious hours wasted trying to swap out different GPUs, RAM sticks, SSDs (which involved upgrading to windows 10 on my old SSD so I could reduce the risk of having windows activation issues due to swapping motherboards), changing settings in windows, clean reinstalling windows, bios reset, switching between wifi/ethernet, updating drivers. Literally tried everything I could think of. I was about to RMA my motherboard and was only stopped when I went back to using my old computer to prepare for my new motherboard to get RMA'd and noticed my old computer suddenly had the same issue. When I went back to using to my old computer, if I had not been prompted and agreed to update malwarebytes to the same version that was causing the issue, I probably would have never realised the issue was with malwarebytes and my motherboard would be RMA'd right now. From my experience, the severity of the problem varied a lot and sometimes it took days before the issue started to occur. It seemed to be the most extreme when either using qbittorrent, or for whatever reason running speedtest-cli on my linux virtual machine (this did not occur when running speedtest-cli on the windows host). Sometimes it got so bad that I would wake up in the morning and couldn't even log in because my computer was basically completely frozen (I keep my computer on 24/7). I've also had an instance where it caused a BSOD, as well as prevented my ethernet from working until my computer was restarted as the network interface kept continually trying to reset (The network interface "Realtek PCIe GbE Family Controller" has begun resetting. There will be a momentary disruption in network connectivity while the hardware resets. Reason: The network driver detected that its hardware has stopped responding to commands. This network interface has reset 1026 time(s) since it was last initialized.). Not to mention it seemed to sometimes be causing strange video/audio sync issues where the video was delayed a couple of seconds but the audio was immediate (saw this happening in videos in the browser, games, and even Zoom video calls). I've captured a video (that I was going to send with my motherboard RMA request 🙂) of the issue where you can hear the stuttering while qbittorrent is torrenting, and then speedtest running on my virtual machine where you can most definitely hear it 🙃. You can also see the video/audio sync issues in the video, which seem to strangely disappear after the speedtest is done. Needless to say I'm pretty frustrated and disappointed by malwarebytes after all of this and have stopped using it as I just can't trust it anymore. It's been one week since I stopped using it and I've had absolutely no problems with stuttering. This issue definitely needs more exposure, either some sort of pinned topic or an email being sent out. This stuttering is the type of behaviour I'd expect from malware, not anti-malware software. Who knows how many other people have been having the same issue and have not been able to link it to malwarebytes. For me this last month has been absolute hell trying to resolve this issue and could have been pinpointed much earlier if there was more communication from malwarebytes about the issue or some sort of rollback. I really hope an explanation of the root cause of this is eventually released, similar to the one for the memory leak in 2018, which also caused me headaches: I have attached a dump of the BSOD: 042620-7812-01.dmp where I can see some files relating to virtualbox and malwarebytes being referenced. Would really love to get some answers to this issue.