Stave

Registry Key: 1 Malware.Sandbox.23, HKLM\SOFTWARE\WOW6432NODE\MICROSOFT\WINDOWS\CURRENTVERSION\UNINSTALL\{86164718-6457-42DE-8DB6-EA05F7045F2C}_is1, No Action By User, 23, 0, , , , , , File: 1 Malware.Sandbox.23, C:\PROGRAMDATA\VALHALLA DSP, LLC\VALHALLAFREQECHO\INSTALLERFILES\UNINS000.EXE, No Action By User, 23, 0, 1.0.51055, 23, dds, 01640845, 238B751E79A5F2F5FAE768E4D49B9207, F5938A7650357EC342012A4CDAA526DAB8914B245CB1EC52768BC4255B590770 File source: https://valhalladsp.com/demos-downloads/ Valhalla Freq Echo Legacy: Version 1.0.5 (32/64-bit) https://valhallaproduction.s3-us-west-2.amazonaws.com/freqecho/ValhallaFreqEchoWin_V1_0_5.zip log.txt unins000-ValhallaFreqEcho-false-postive.zip

Thanks for your reply. I hope this is fixed quickly. The first thing I thought was that it was some form of actual malware or phishing exploit masquerading as a Malwarebytes message. I have my browser fairly well locked down, so I haven't seen anything like this in quite a while. I guess it's tough to block a (previously) trusted a application like this on our systems.

Malwarebytes Premium user here and not happy to see this popup tonight. Please disable it and add and opt-out setting to block any future marketing tests. Until this is patched, does anyone have a hosts file entry, IP block, permission setting or another way to block these without breaking the legitimate Malwarebytes functionality that I paid for?

Eagerly awaiting the update fix. If the fix will be lengthy, perhaps rollback to the previous stable version in the meantime.

Also having this problem today with Malwarebytes 3 Premium on Windows 7 64-bit. My browser crashed and Windows popped up a notice about lack of memory. Then Malwarebytes was showing Real Time Protection (web) tuned off. I killed the process and Malwarebytes restarted and I watched the MBAMService.exe memory usage in Task Manager steadily climb through the roof. Then I searched and found this discussion and have now disabled the Malwarebytes service until I see notice of an update fix release here.

As a test, I re-enabled MSE Real-time protection after the Tuesday (11/29) update from Microsoft. After a couple days without issue, I had the same system slowdown hang again today (12/1). I have had all the exclusions in place since last week, but the exclusions alone do not seem to be a 100% effective solution. I have now disabled MSE Real-time protection again and will keep it off until there is some official diagnosis and solution from Malwarebytes and Microsoft. Until this recent problem I had both MSE Real-time protection running alongside Malwarebytes Premium for at least a few years without the need for any exclusions and without conflicts. Earlier in this discussion, I read that Microsoft doesn't intend to support two simultaneous real-time scanners, but I can't help wonder what has changed to break the previous compatibility.

I also wanted to mention that since disabling Real-Time Protection in MSE I have been able to run an MSE Quick Scan and MBAM Threat Scan successfully without any hits.

Yes, I had added all MBAM and MBAE .exe files to both "Files and Folders" and "Processes" exclusions in MSE and rebooted when another hang occurred. However, in MBAM I only added the MSC directory and MsMpEng.exe to Malware Exlusions in MBAM. I had not added the MSE Processes to Web Exclusions in MBAM. I will do so now. At first, the exclusions seemed to work for most of the day until later when I had another hang. A notable difference was that the latest (post-exclusions) hang occurred some minutes after booting. I thought everything was okay and started browsing, then minutes later I had the exact same slowdown as before the exclusions. The difference was that before I added exclusions, the hang would occur immediately after booting which didn't even allow me to open any application. I am still waiting to see some official updates that specifically address this conflict between MSE and the Malwarebytes products, before I re-enable Real-Time Protection in MSE. After you story about a killed SSD, I'm not eager to do more testing on my own system until there is an official fix rather than this temporary exclusions workaround. I see MSE definitions updated to 1.233.356.0 today. @BryanWright: Yes, as I mentioned in my earlier post I had another hang after putting in all the exclusions yesterday.

I thought I had some success with the exclusions earlier today, but I had another extended hang just now (with MSE 1.233.245.0 and MSE/MBAM/MBAE exclusions in place). After many minutes waiting to shutdown, the "Preparing to Update configuration" message was shown on the screen, despite not making any changes nor seeing any Windows update notices (and nothing is shown in Update History). For now, I have kept the exclusions in place, but disabled MSE Real-Time Protection. I did update MSE again to find new definitions version 1.233.278.0 available, but I will keep Real-Time Protection off until there is a more concrete diagnosis and fix available. I will check for updates here from Malwarebytes and Microsoft tomorrow.

I think I've seen a similar issue here intermittently for the past few days on Windows 7 x64 Ultimate SP1 (with current November updates), Anti-Malware Home Premium 2.2.1.1043, Anti-Exploit Free 1.09.1.1261 and Microsoft Security Essentials (1.233.202.0 definitions). On boot, any application I tried to launch would hang for a long time (minutes) before responding. I was able to eventually shutdown, but the process also took extra minutes for each menu selection (to shutdown). I saw MsMpEng.exe and mbam.exe using the majority of CPU% on startup. The Event manager showed MsMpSvc timeouts as well as other Service timeouts. Finding this thread here, I have added the mutual exclusions to both MSE and MBAM and the persistent hangs at startup seem to have stopped. Both programs still claim the most CPU for a while after startup, but they calm down after their initial scans and other programs launch normally without the previous extreme delays I was seeing.