Jump to content

I don't like the way MalwareBytes handles re-installation after updates


Recommended Posts

When i update from v1.39 to v1.4, the re-installation is a total failure and as a result, the program itself has totally become dysfunctional. I had to download another separate installler to do the update up to v1.4, which is pretty inconvenient. I wouldn't complain about this issue if it was only once, but then this situation happened for about three times already. I do hope that i don't have to keep on downloading the latest installers just to upgrade my version. ;)

A suggestion: why don't the development team create a file to include in the update with the sole purpose of uninstalling the older version of Malwarebytes on the machine automatically before installing the new one? That way users don't have to bother uninstalling the MBAM themselves or have their MBAM corrupted after doing a version upgrade through the update module...

Link to post
Share on other sites

I've always installed new versions over old ones without issues. Possible causes for your issue could be either your anti-virus or firewall blocking the process or if you're on Vista, having User Account Control turned off could also cause issues with the installer.

Just for reference, I've done the update install several times over several versions on XP Home SP3, XP Pro SP3 as well as SP2 and Vista x64 SP1 and SP2 without problems.

Link to post
Share on other sites

  • Staff

Must be something on your system causing this. I don't recall hearing anyone having this issue so consistently. The first thing we do with beta versions is to test installation process. We've not had issues such as this since I've been working on beta apps.

Link to post
Share on other sites

I've always installed new versions over old ones without issues. Possible causes for your issue could be either your anti-virus or firewall blocking the process or if you're on Vista, having User Account Control turned off could also cause issues with the installer.

Just for reference, I've done the update install several times over several versions on XP Home SP3, XP Pro SP3 as well as SP2 and Vista x64 SP1 and SP2 without problems.

I forgot to mention: the issue occur on an RC version of Windows 7. I allowed the antivirus & firewall to not interfere with MBAM's installation. Possibly due to the UAC, as i have it turned off. Is it possible, i mean? It sounds unlikely that disabling UAC could have caused the problem, as this issue did not happened in Vista with UAC turned off.

Link to post
Share on other sites

  • Staff

I'd be willing to guess that it's more or less impossible for anything to be downloaded which the software does not ask or require be downloaded to the system. Regardless of your settings.

Your system can't decide to pull off the server, it can only get what's offered.

Link to post
Share on other sites

I forgot to mention: the issue occur on an RC version of Windows 7. I allowed the antivirus & firewall to not interfere with MBAM's installation. Possibly due to the UAC, as i have it turned off. Is it possible, i mean? It sounds unlikely that disabling UAC could have caused the problem, as this issue did not happened in Vista with UAC turned off.

It's because UAC is off. With it turned off programs cannot request (and therefore do not receive) the required privelage elevation (ie Run as administrator), so with the automatic updating, you never get the chance to select Run as administrator so the program tries to install and fails to install properly because it isn't give the proper privelages.

By the way, turning UAC off is ALWAYS a bad idea. It's there to protect your PC, it may nag you a bit more than you'd like or add an extra click or two, but the first time it prevents a piece of malware from installing on your system you'll learn to appreciate it. Most programs these days are designed to be UAC aware, meaning that if UAC is off, they will not function as they should and may fail to install properly (such as the problem you're having with Malwarebytes'). Incidentally, mbam.exe, the scanning component of Malwarebytes' also requires administrative privelages, so if you scanned your system with UAC off and it found something it would likely not be able to remove it due to lack of full admin level access to your system and its files.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
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.