MBAM 1.46

I definitely experienced the "double install" on at least one of my PC's...

on the other, it was either a double install, or a delayed install, or something weird...

but they eventually worked okay.

my understanding is that, aside from the delayed or double install, there shouldn't be any further problems.   I've run a few scans since then without incident.  So if it seems to working well now, i'd leave things alone.  

I also experienced the "double install" a little while ago. When I boot my PC, I always let my Avast 5 and SpySweeper 6.1 to update and then I double click MBAM to install the latest update before clicking my IE 8. Well MBAM did download data version 4055, but did not install. It then proceeded to download Prog V.1.46. After the download, I accepted the install but did not open again. I double click the MBAM icon and a window opened saying that MBAM 1.46 was downloaded and to accept it so it could be installed which I did again. This time MBAM installed completely but without the latest update data version which I have to download again. I did a quick scan and it seems to be working right. I only use MBAM to scan my sys periodically and I am wondering if it would be a good idea to uninstall and install it again clean. Mind you my install was in English.

Thank you and regards.  

So if it seems to working well now, i'd leave things alone.

Ditto here.

At first I thought MBAM would have quickly fixed this bug, til I realised the bug was actually in my current version (1.45) updater/installer, not in this latest.

Other users are reporting  the odd incompatabilities/BSODs due to other 3rd party products, but nothing with any program generally recommended around here. And even these were temporary, and solved with a reboot or two.

A good reminder that a clean install of a new version upgrade is always the best way to go, (but I'm lazy with certain products with a good track record, such as MBAM).

my understanding is that, aside from the delayed or double install, there shouldn't be any further problems.   I've run a few scans since then without incident.  So if it seems to working well now, i'd leave things alone.

Copied that. Did full scan and updated to data version 4056. No problems whatsoever.

Thank you David.

At first I thought MBAM would have quickly fixed this bug, til I realised the bug was actually in my current version (1.45) updater/installer, not in this latest.

I upgraded from 1.45 to 1.46 using the internal installer/update - it went without a hitch.  About an hour ago. Just lucky this time I guess.

Jeff