TommyGunnSF

Again, thanks for the reply. But, I don't run Kaspersky...ever. It came as bloatware and I always exit it upon any reboot. I've just not gotten around to completely deleting it. Plus, it's not installed on my XP box. It's not Kaspersky. It sucks up my CPU only during scans...not while it's running in background. The net is that I just don't like the feature set of 2.x. For example, when it recovers a scan, it doesn't tell the user but just runs in the background slowing everything down. It should float a pop-up letting the user know it's recovering a scan and giving the user the option to continue or postpone or kill the scan. That's how nearly every other app works for such things. There are other gaps in the feature set, but I just don't care about 2.x any longer. I'm going back to 1.75 and will wait till an update. Cheers!

Although I appreciate the generous "call to arms" with my issue....I'm not hearing anything that addresses my issue. Which is, quite simply, that MBAM 2.x is a resource hog. I've jumped through all these hoops above (and those requested by the original TS offline) and, still, nobody has been able to give me a straight answer. What in my logs points to the need for either of the suggestions made...1) run ComboFix (ha, this still is the best), 2) delete all my torrents and uTorrent (which...seriously?! give me a break. 95% of my torrents are from private trackers). Let me put this most clearly...*everything*....I repeat...*everything* is running just fine on *both* of my computers. The one and ONLY app that is NOT running perfectly remains Malwarebytes 2.x. So, although again I truly appreciate the replies, I'm not buying the deflections away from my real issue, which remains MBAM 2.x. The way I see it, my best move is to down rev back to v1.75. If someone can convince me otherwise, I'm all ears. Otherwise, I'm going to wait till the next major release for all the kinks to be worked out. Cheers.

So I did the clean install on, both, my laptop (W7) and desktop (XP). Both are running slightly better, but I'm still not happy with performance. And, actually, the feature set remains subpar with 2.x, in comparison to the previous rev. I've included the requested logs, just to be sure...but I'm inclined to go back to the old rev of MBAM and wait for v 2.x Awaiting your response. Thank you. FRST.txt Addition.txt CheckResults.txt

Thanks for the reply, FF. Before spending the time to create an account on this forum, I spent a couple hours reviewing threads that closely matched my issue (including reading the pages you suggested, yada yada yada...I'm not a noob). The two things bubbled up from my research were...it seems that there are more than enough users having CPU issues (meaning, it's statistically significant and not just our collective imaginations...what is the company doing about this?!), and secondly, I didn't read one single instance where the clean install solution was anything more than a waste of time. This just comes off as a usual "uninstall/reinstall" punt that is so often the calling card of a CSR at their wits end. Don't mean to sound like a total dick here, but I'd just like someone to demonstrate that they have: 1) actually carefully read through the issues I've painstakingly detailed; 2) have carefully looked through the attached logs; 3) have provided me with a troubleshooting path that may demonstrate a more personalized effort than the typical "hands-in-the-air" punt. Tell me why doing this clean install/log creation will be any different and maybe I'll give it a shot (and, if I do give it a shot and it actually works, I will happily eat my words and tout you as a customer service god). Again, thank you for your reply regardless.

Longtime MBAM user here. Have always found the product to be a very elegant, resource-efficient, effective tool. I also have always appreciated the ability for the user to custom configure the way the app works. However, with the 2.x release, I am reconsidering my AV solution. if I can't get this hog to run properly, i'm going to trash it. CPU utilization is terrible and many of the most useful customizations have been omitted from this most recent release. On top of this, I sent in a service request outlining the CPU issues (and some other config questions), sent in the "attach" and "DDS" logs per request and the CSR felt that the best fix for my issues was to run ComboFix...wtf?! When I asked him to provide me with what in my logs pointed him to this (seemingly) incongruent fix, all I've gotten has been silence. Hence, I was forced to open an account here and try to resolve this with some of the more engage MBAM experts here. Original note to MBAM support (log files attached): Drew W, Jul 02 11:41 AM: Dear sirs - I have been a loyal Malwarebytes user for the past several years. Love the product! But, this most recent update to the app omitted some useful features from the past rev, which has added quite a bit of overhead (and annoyance) that need not be. 1) Notifications need to be broken out, like they used to be. Users need to have the option to control how website blocks are notified *and* how threats are notified. The latest rev. lumps them both together. Please break them out again. 2) Scans seem to consume even more CPU than in previous versions. Although I understand the need to focus on the scan, is it truly necessary to consume 90%+ of the CPU (and I have a quad-processor high-RAM device)?! Why not either lower the CPU demand and/or allow a user to control how much of the CPU the app can consume (like Photoshop). 3) Related to CPU consumption...trying to cancel a scan is a disaster. It does not cease the scan immediately, but requires up to 5 minutes to finally cease. Pause scan is immediate. The only way to do an efficient cancel scan is to pause first, wait for the scan to pause, then cancel it. Just hitting "cancel scan" causes the app (and CPU) to hang. 4) Related to the inordinate CPU consumption, scheduled scans are a problem in that if a user selects to Recover missed scans, the scan starts immediately at the next chance (i.e. first bootup of the morning) and just causes all sorts of problems with the high CPU consumption. Please offer the option of the app to *warn* the user of a pending scan with the option to either "continue scan" or "pause scan" (with a drill-down option of a time select for postponing...a la the restart reminder for Windows Update). As it is, I've had to disable the Recovery option. This means I will most surely miss some needed scans (as will other users). Please make changes to ensure that this most recent rev works in the manner that your customer base has become accustomed to. As it is, this most recent rev is a terrible CPU hog with a poorly thought out feature set. I, like others, may end up lighting up the message boards with recommendations NOT to upgrade (and in my case, to go backwards). Thank you for your consideration. Feel free to contact me with any questions. I would appreciate follow-up, please. Drew W attach(DW_W7).txt dds(DW_W7).txt