This is my first post to the Malwarebytes forums... I'm experiencing the same slowdown and system hang issues on an XP machine as reported in this thread. Mbamservices.exe goes to 97-99% CPU utilization in the Task Manager upon booting up. For a couple weeks now I've seen much longer startup times. Yesterday, it made the system totally unstable and unusable. I made several different attempts to stop MBAM without success... resorted to hard shutdowns and was finally forced to uninstall Malwarebytes from this machine. I've already tried a full reinstallation using mbam-clean.exe without any success. I also tried complete removal of Microsoft Security Essentials along with MBAM, removal of any orphaned registry entries, defragging the registry, resetting the page file, wiping the free space and defragging the hard drive BEFORE reinstallation of both products and still no luck. I've been running Malwarebytes in parallel with MSE (and ESET NOD32 prior to switching to MSE) for several years without any previous issues. All proper exclusions are set in both programs. I have had no recent similar issues whatsoever with other PC's running various flavors of Vista and Windows 7. In my opinion, it's almost definitely a problem isolated to Windows XP. This particular machine is older, but is very well maintained and not a weakling given its age. It’s a Dell Precision M70 mobile workstation with a 2.0 GHz Pentium M processor, 2 GB RAM, 256 MB nVidia Quadro FX graphics card, etc. I'm not running ANY unnecessary junk at startup. It has Windows XP Professional SP3 with all updates. Also in my attempt to resolve this issue, I ran SFC, checked the logs, ran F-Secure and Sophos online scanners (no infections found), etc. This “High CPU utilization” issue also appears to have caused various other random errors in the system event log at startup which have all disappeared since removal of Malwarebytes. Based on the other posts and my situation, I'm convinced that some recent change to Malwarebytes has "broken" the product for the Windows XP operating system. Are you guys pulling out your support for XP a full year before Microsoft does? In all seriousness, I'm hopeful you guys are giving this issue the attention it deserves, will discover the cause of the problem and issue a fix for it very soon. Thanks!
