Jump to content

Peakeen

Members
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Sorry but it's much worse than that! If it were just MB's update that crashed then, yes, "pain in the butt" would fit the bill. However many of us were left completely unable to login to Windows because of this abortive upgrade. I'm guessing that there are many non-techies out there still unable to log in and totally at a loss to understand what has happened and to how to proceed. That is better described as "unmitigated disaster". I'm posting this, not as a snide comment, but because I think MB need to consider how to move forward, and coming up with a work-around pending a new version is only part of it.
  2. It's F8 for safe mode not F12. However what I had to do was boot the original installation CD and enter R for the recovery console. When eventually you get into a DOS environment enter the command disable MBAMService You should then be able to boot, login and uninstall MBAM It's worth noting for the moderators that I have used MBAM for a couple of years, but only for on-demand scans every week or two. Therefore I believe MBAMservice should not have started at boot or login. In fact it was the appearance of the "M" system-tray icon just before everything came to a grinding halt that alerted me to what was wrong. Good luck - happy new year!
  3. Seriously folks, just uninstall MBAM then install MS Security Essentials. Trouble is, how do you uninstall MBAM when your computer hangs every time you log in (as mine did) and you don't know how to boot into safe mode or use the recovery console? How do you find esdog's instructions if your computer hangs every time you log in and you can't get onto this forum. In fact, how do you even know to suspect MBAM? The people posting here have an above average level of technical skill (especially AussieDave, although his instructions need modification to work in the northern hemisphere). I wonder how many of MB's clients just see a broken computer and are now contemplating defenestrating the damn thing. I suspect many more people are affected more seriously than MB seems to think.
  4. Your wrong to assume that a small number of posts means that only a small number of users are affected. How many of those 2 million users do you suppose have spent the day watching their computer hanging time after time for reasons which they just don't understand, and then given up and gone to the pub? Even if they suspect the problem might be associated with MBAM they can't get on-line to check, let alone post in this forum, because, well, their computer is hanging. I'd guess only a small percentage of users actually have the skills to fix something like this unaided. Just a thought.
  5. My experience was that I could log in (XP Pro SP3) but then, as others have said, everything froze. Using Linux Mint to browse for similar problems in the past few days confirmed my suspicions that MBAM was probably to blame. My solution was to boot into the recovery console from the installation CD, use LISTSVC to find what services were started, and then to use DISABLE to prevent MBAMService from automatically starting. I could then boot and login successfully. The first thing I did was to uninstall MBAM and I'm not planning to reinstall any time soon. I run Microsoft's anti-virus and Zonealarm firewall, but I only ever use MBAM for on-demand scans so MBAMService should not have started. I suspect there are lots of folk out there staring at a frozen screen, totally unable to use their machine thanks to this "upgrade".
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.