I had an issue with this yesterday, and perhaps you’re referring to my thread there. It takes a few clicks a lot of times to get the update to actually take, but mine went one step further and asked me to restart twice, until finally I was able to get the latest component package.
If you read that thread, it’s mainly speculation from the one user that Avast could be responsible, and he admits as much. When I asked about potential Avast and MBAM conflicts a while back, that same person said that the scanners won’t cause an issue and then re-iterated in the thread from yesterday that it was specifically the scanners, and that updates can still be messed with. Again, this was his speculation and he doesn’t solely blame Avast. He also mentions Fast Startup and recommends that being disabled, and it’s something I think i’ll do, but considering I don’t just shut down my computer often and have restarted several times over the last few days (including 10 or so hours before that first update attempt yesterday), i’m not sure how much of an issue that was.
Another thread that I posted regarding the updates generally and the number of clicks needed, he suggested that the first click is for updates to definitions, then subsequent clicks would be updates for updates to the program and component version. As you’ll see in my most recent thread, it wasn’t my experience yesterday. It could have been a weird one-off glitch, or something that’s wrong broadly.
So to answer your question: I experience the same thing, I don’t know if it’s due to Avast. I also use just the Free version that’s just the manual, on demand scanner.
Links to MB Forum threads in case people don’t want to click the hyperlinks above
which version you running Chris.
4.6.1 here. just pulled out of the ended premium trial which they upgrade you to now and again. not sure there was a auto update but as i dont have it running in background so im not sure.
running a scan now.
scrap that, just done a manual check after the scan for update and it started instaling. now on 4.6.6 and loaded without any isues from avast premium.
edit
4.6.6.294
version 1.0.77890
component 1.0.2201
Dinobot2
it didnt ask me to restart comp just firefox.
stupid hat on now.
only mbam ive ever used was years ago on and old pc to wipe hard drive.
sorry, dopy twat me is. it asked me to restart the program not firefox DOH!
just checked program files and mbam is in the malwarebytes folder and accessed today so i guess i do have it installed.
Now when I try to do a manual update, the message announces “you are up to date”.
it asked me to restart the program
Generally, this restart is performed each time the program version is updated, but not for the module update.
My program version is (has been for several days now) 4.6.6.294
Yesterday it was component pack 1.0.2189 that wouldn’t update to 1.0.2201, it told me it was installed but it wasn’t, and it kept looping every time I tried to update it, even after every type of startup…OK today
Wondering if you’re still having the same issue as last time? I tried updating MBAM and while it downloaded and installed an update successfully, i’m still on an out-of-date program and component package version. Subsequent clicks to Check for updates (on either the General or About tab) just pops up that Malwarebytes is already up to date.
I already did a scan on some files from the context menu and it didn’t do anything to update me to the latest version. I think it may have only updated the definitions but wasn’t doing anything for the program and component package. Even tried a computer restart and still the same issue.
I posted the issue on the Malwarebytes forums and was given the offline installer for the latest version which worked and i’m as up to date as you are after manually updating the definitions again. But I’m not sure if that fixed any underlying issue or that was just a one time glitch. I guess I won’t find out until the next big update.
Bumping this again to see if you or anyone else is having a Malwarebytes update issue. They updated to Component package version 1.0.2249, but i’m still stuck on 1.0.2242 after clicking Check for updates over and over. It still tells me i’m up to date after updating the update package version.
FYI. I have MWB v4.6.8.311. I did “Check for updates” today and got component package 1.0.2249.
Only use MWB for occasional manual scans, not live protection which would likely fight with Avast.
Ok i’ll try that next time if the update doesn’t work. I used their support tool to do a clean install at someone’s recommendation, so hopefully that actually does the trick. If it doesn’t, i’ll try your method, but it really shouldn’t be necessary to jump through all of the hoops or go in this sequence just to properly update it.
Also, when you run a scan, are you running a full scan of your computer or just scanning a small folder or something? You can’t do quick scans on the free version of Malwarebytes.
It is probably entirely unrelated to this current problem but long a go I suddenly had trouble updating MWB; it would say I had the latest definitions available when, as I eventually realised, they were not.
After a suggestion on another forum I found the problem was, as they had guessed, some change in the ISP’s default DNS server security settings and it was blocking the MWB’s update. No explanation was offered when I asked on the ISP’s forum about this being a possibility.
However when I took the ‘risk’ and swapped from the default ISP DNS server to another one, ‘magically’ the MWB updates started working again.
It is very simple to do if you go into your computer’s network settings you can change the default DNS server and set up a secondary one very easily. You may even find you get a little bit more speed too.
Alright so I tried updating the ‘regular’ way which just updated the Update package version, but not the new Component package version (1.0.2259). I tried your method of doing a scan (just scanned a random small folder on my computer), then manually checked for updates again, and it updated my component package version from 1.0.2249 to 1.0.2259.
So, just wanted to say thanks for the suggestion! It’s still silly that this method is required, but c’est la vie I guess.