
Marcin and Tim (Majorgeeks owner) have each others personal phone numbers. You know when Marcin was in college building Malwarebytes the small crew at Majorgeeks (including me in a small way) was right there helping however we could the whole time. I told him you had reached out and I was going to give you his direct email but I don't think that is necessary now. Going forward we will add a visual indicator in the UI when a build is an Alpha or Beta so that in case it is wrongly picked by a third party people will be able to easily notice when it's not a final version.Īwesome. If it's not on the official site then it's not been released yet. (Or from Software Updaters, those usually/often use 3rd party sites). This is why most software manufacturers will recommend that you only to download/update from the official site and not from 3rd party sites. (And then came complaining on the official forum, we pointed them straight back to Majorgeeks to complain there). Of course anyone who had already downloaded that pre-release from Majorgeeks got the bugged version. Majorgeeks themselves have been caught out in the past when they scraped and posted a pre-release version of that particular software that contained a significant bug, the bug was found late and the update pulled just before the scheduled release. So what you see on Majorgeeks, and others, may be the final RTM version, but it may not be. Some eagle-eyed folks keep spamming httpx://download.#.com/#setup_v#.exe to try and get a headstart on publication during this short window - which we have tried to keep as small as possible to minimise the risk of third parties publishing links to release candidates that are later pulled. Placing blame on people who downloaded a file from Malwarebytes is tacky though.ĭue to caching, etc the launch processes go from the bottom up - file appears on the server, then the various linked website pages are updated and then the release announcement is made only after everything is ready. Remember the time sUBs accidentally released a version of Combofix that infected machines with the Sality virus? That's just one example I witnessed over the years and years I have been helping on forums with malware removal.

I'm not sure why that is so hard to admit. They have been around longer than Malwarebytes and they have promoted Malwarebytes at the top of their home page for years. Someone on your end made a mistake and now there is apparently an unstable copy of AdwCleaner in circulation. Majorgeeks isn't just some scraper website looking for clicks. I think it is kind of tacky to talk about one of the vendors in your partner program like you are. I would have a lot more faith in this whole conversation if you just admitted it was released in error. Majorgeeks didn't make up the 8.3 version because you yourself confirmed it is real. Majorgeeks just happened to download the 8.3 version thinking it was a final release before Malwarebytes pulled it. Please explain to me how there was an update to the AdwCleaner Lifecycle page the same day that the 8.3 version was listed at Majorgeeks but mysteriously there is no updated version of AdwCleaner on the website? Somehow that update of 8.3 was released (alpha, beta, final, whatever) but then removed.
