Scootcha

The exact same symptoms for me. I actually find .75 to be more annoying because it is now more random. At least before I could expect it to happen and know that hitting the 'Turn On' box or the 'X' would just be a part of my system restart routine. Now it is a spinning Wheel of Chance.

"Enhancement" = A bug fix fed through a marketing speak translator.

I thought I might be able to also say that the beta was working fine since it worked well for over 24 hours. Nope. The "Real-Time Protection layers turned off" just came back on at least one of my machines. It looks like I am destined for more wasted time waiting for yet another fix attempt. This is getting very tiresome.

So the basic premise of your conspiracy theory is that MB3 itself is susceptible to a malware attack? Let me digest the underlying implications of that defense.

This works both ways: Do you have visibility into what percentage of those customers are having problems but just not reporting them?

Updated MB 3.0 tagline: 4x stronger, 4x faster, 4x the hassle

I consider not having those "capabilities" to be a distinct plus at this point.

This mirrors my experience. If I dismiss the assorted known bugs my i3 and Xeon systems work well. My Core2Duo laptop basically becomes unusable with MB3. Last week I got an email from a friend who was trying to clean up her Mom's AIO PC and ran into what sounds like this problem. Yes, she had downloaded MB3 and I suggested she find a version of 2 to run. Even though it will be impossible to quantify MalwareBytes is going to lose customers if they continue down this track.

Not that it is more important than basic functionality ( I just reverted to MB2 on the laptop that can't handle 3) but I find that unnecessary "Awesome!" editorializing kind of childish. Just give me pertinent status information without the fluff.

I should have added that unlike ZVAXX I'm only seeing the high CPU temps for a relatively short time-span which is probably due to the Dell throttling on this particular laptop. Slow performance or burning up is not a great choice to have to make.

I signed up just to balance out those dismissing your concerns about .1469. While the full scan running ~99% on my Celeron, i3 and Xeon desktops just make for a faster completion my testing with an older Win7 Dell with a Core2Duo laptop has been brutal. I've tried running a full scan a few times after fresh reboots and letting the system stabilize and the system becomes useless where trying to bring up any additional app, task manager or even trying to cleanly shutdown the system becomes unresponsive. I realize this Dell laptop has some CPU throttling issues that are unique but that does not mean we are not seeing some very annoying behavior with 3. Just cause they are not experiencing it on their platforms does not mean there is no problem, especially when compared to what we were seeing with version 2.