Updating from 1.45 to 1.46 forces MBAM to keep reinstalling itself upon reopening

[Solemn]

This is by far the strangest bug I've come across with MBAM that has actually forced me to uninstall it completely. Basically as the title says: I was doing a manual update from 1.45 to 1.46 when I noticed a bit of buggy behaviour in terms of how the program updated. First of all it started to download/update the signature file first, but before even completing that to 100% (it got there on the progress) it closed that progress bar and started downloading the bigger program update instead. It then proceeded towards installing it like MBAM normally updates where it closes itself and the installer runs. From here on the same problem I've been having on and off forever occurred again (but this time with a twist). Basically MBAM is supposed to reopen itself after updating with a successful update message, but it always cuts short after running the installer and just vanishes (I assume it crashes? Nothing shows up in the Task Manager). I just get a random error message now saying that the error code was 0,0 and something about a failed register. I've noticed that this appears to be occurring on Vista and Windows 7 only (I've done this on x64 versions though and not 32bit). Either way I'm not sure if 'registering' will fix this as the whole new button confused me with no real description or information in the program when it suddenly threw it up after 1.44.

Anyway, the really strange part happened after this: usually I just reopen MBAM manually and it appears to be updated fine. In this case it did not even open. Instead, attempting to open it popped up the "MBAM has downloaded an update and is ready to install: OK/Cancel" window kind of thing. I of course clicked Cancel the first time and sure enough MBAM opened shortly afterward with it apparently in 1.46 updated form. Interestingly, as I mentioned earlier the whole signature update that occurred before the program update cut it off did not register and I had to redownload it yet again even though it appeared to be downloaded the last time (this never happened with pre 1.45 versions). I thought this was a one-time deal, but after closing MBAM and then running it again it did the exact same thing with the update window dialogue. This time I clicked OK for the install, and it simply just reinstalled itself (I think?) and then reopened. This did not fix the glitch as opening yet again brought back the install window + reboots didn't have any effect either. Furthermore, by selecting the OK option to reinstall when reopening I noticed that each time I did it, the signature file would require that same update again as if it kept reverting to the preset version before the whole update began!

So I've uninstalled MBAM for now and quite frankly I'm a little cautious on reinstalling it considering I have no idea how the update to the next version will fair off (1.46 notes did not appear to fix any element of this). Continuously reinstalling the program just for each program update seems a little ridiculous so at the moment I'm wondering if anyone has had similar issues or is willing to look into this. I've been a fan with MBAM in general, but when it came to relatively buggy program updates like this for quite a long time, I've been having my doubts now--I'd hate to drop the program altogether, but it seems this issue has been lurching around for far too long (until it got nice and ugly with this variation).

Other than that, my basic rig setup is in my forum signature. I haven't really had any other issues; Windows is fully updated, drivers are fine, programs in general run smoothly, and Avast has never really had a problem with MBAM (the version I've been using of MBAM is the free one anyway). If you need any more information, I'll see what I can do. Thanks in advance (this was a rather long read I imagine).

[exile360]

Greetings

This was an issue with 1.45's update routine. To fix it if you wish to all you need do is download version 1.46 directly from here and install it now that you've already removed version 1.45.

[Solemn]

Well I guess I should've just stayed quiet before writing that speech and reinstalled properly despite my worries. I'll give that a shot, wasn't aware that this issue was addressed in 1.46! If any ghosts of this problem come back I guess I'll update this thread. I really appreciate the speedy reply, hopefully there won't be any more burps so to speak.

[exile360]

No worries, your concerns are understandable and there were many posts on the board from other users such as yourself who were confounded by the same problem. Needless to say, going from 1.46 to 1.47 when it is released should not be so painful .

If you require anything further or have any more issues please feel free to post.

Thanks