CaptainLeonidas

I did a quick check-up of this current version of MBAM on an older version of Windows 10 and I was perplexed to see how quickly this instance of a Antivirus solution kept allocating more and more RAM over time. Within a short timespan it managed to claim nearly 300 MB of RAM while an other AV solution happily kept running without little to no change to it's RAM footprint. Yes, I am well aware Beta's needs more tweaking to get the bugs out. But this was unreal to me. Another thing that is beyond me is the fact only those with a full license seem to get access to the Beta program. I for one would never burden my paying clients with access to Beta's as they most likely would not pay for nearly finished products anyway but to get a stable version maintained for for the duration of their subscription of their production systems. Beta access should be a perk for those willing to lent their computers to a "free" AV-solution knowing they pay for it by testing a raw product. At the end of the day I of course removed this MBAM beta as soon as I could. Clearly this beta is in my humble opinion nowhere near release candidate status.

Perhaps in light of the posts now popping up left and right, about Windows 10 build 2004 and severe performance issue and the like, you may want to add a check in the MBAsetup.exe checking Windows builds as is before it start the installation itself? I myself already am telling folks I know to be using MBAM to be extra careful with upgrades (Microsoft and MBAM alike). So I am doing my part making sure friends and college's of mine do not get trapped in this mess. Time to step up too Malwarebytes?

Seems I may have to wait longer before I try MBAM then. Bummer as I was hoping to re-install once again. I will look forward to whatever logs are gathered. Perhaps I might see some similarities with my setup and get a more founded insight if indeed it is time once again for MBAM to be part of my security protections on my devices.

I "believe" I will do better not to install any MBAM at this time. I am fully aware I am wasting my paid subscription for the 3 devices I bought it for. However since I have not been notified that my issue has been resolved (and I mean I am to get some tech-talk in depth details then) I am waiting. Note: I will again try to see if MBAM is trustworthy enough to protect my devices but only if and when a new version is announced or if I am directly contacted it has been resolved in the current version.

Only by turning off which of the four separate components are causing the issue it is usually web protection or ransomware protection. Also does not hurt to place mutual exclusions in both Avast and Malwarebytes. Is this officially confirmed? I recall a Avast post once stating "Real site" being the issue at the time. If indeed web protection is the issue with the current MBA on Windows 10 Pro May 2020 I could re-install the MBA software but like you wrote disable this feature for the time being. However with an assumption I rather not try at all.

Now that I think about the VM which was offered Windows 10 May 2020 I think I recall I recently bought a Windows license key for it through Windows Store. The other Windows 10 Pro running in VM's have older activations applied..

From https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004 Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. I fail to see this as a forced upgrade. Again any update or patch for that matter may not be available thru Windows Update for a number of reasons. But that discussion is not for this forum as it does not help the issue at hand. In your words: I am not defending Malwarebytes as there are issues with some configurations at the moment and has been going on for several months and have not been able to be reproduced by the developers. I just hope to see a production ready release soon or like I wrote before an answer: Can the current MBA installation be tweaked to allow current users you continue to run MBA (production release) on Windows 10 Pro May 2020 instead of a Beta release?

Unfortunatly you missed the info I provided. As you will be aware of I run Windows on both iron as I do on virtual hardware (VMware Workstation 15.5). You may agree with me if I run Windows 10 Pro (I have 5 VM's) on identical virtual machines and of those only 1 is offered the update you logic is flawed.

Regarding your text: That is considered force upgrading before Windows update offers it to you. I would also have uninstalled Avast/AVG as 3rd party AV programs have a very high potential of messing feature updates up. I do not see this as force upgrading but I guess will look at it our own way.

Added info: of the 3 Windows device I have running Windows 10 Pro/MBA/Avast/HitmanPro, the Microsoft Surface Pro 6 is still 1909 (OS Build 18363.836) will state within Windows Update thru Setting that Version 2004 is not yet ready for the device. The computers current running Windows 10 Pro Version 2004 never showed this notification.

The computer systems were made up-to-date thru Windows Update Assistant. Of course I made sure to look at the release notes (https://docs.microsoft.com/en-us/windows/release-information/) regarding issue's listed for Version 2004. The Windows Update Assistant was downloaded from https://www.microsoft.com/en-us/software-download/windows10.

I will review your advice for now. In my case MBA is a backup AV much like Hitman Pro/Alert and the native Windows Defender. Do know MBA Premium worked fine out of the box on 3 computers I govern but only after the computers had been updated with the Windows 10 Feature May 2020 update issue's arose. All of my device are up-to-date. If the beta does improve working in general then this automatically means the current version may have shortcoming. Beta's are great for testing the water / reviewing future features for those in the field whom like to test near public release(s) but are in my humble view unfit for production systems. Offering the use of a beta version is therefor a well intentioned workaround at best, not a solution. The shortcoming I ran into are perhaps not too visible now as Windows 10 May 202 is being release by Microsoft in batches. Your advice however could be to hold any Windows 10 upgrading for now till your current beta has matured to full production status. I do wonder if the current version can be tweaked to disable problematic parts of MBA Premium until the next official release becomes available.

Btw your tools needs some updating to be AVG acceptable. User folder names are not what a tool like your should include / read out as part of de log files in the zip. I myself had a look the logs and replaced folder names when possible (just hope I dit not miss anything).

mbst-grab-results.zip

I am looking at similair issues with MBA on my Windows 10 May 2020 computer. Random freezing of the PC or when starting up the MBA services takes forever to get started (Running withing services).

@caamt13Just start MWB again -> update via GUI -> restart service. If for whatever reason the process is still running in Taskmanager while restarting the service -> kill process and start service via Services

I have updated 2 computers so far. They both had the service "MBAMservice" disabled till the current update became available. Force updates via the MWB Gui and then restarted the service "MBAMservice" issue resolved.

Restart the service first after the update or reboot.

Well, seems I am not the only one with issues. That both good and bad. I do hope MB will sents a notification when the issue is resolves perhaps a update on the main page? Btw updating seems impossible for now. Getting message the update server is offline (well something along that line).