Latest Version of Malwarebytes

johngalt said:

This happens more often at MB than you'd think. A βeta package gets released to a few βeta testers in the wild, but never actually gets released worldwide as a βeta.

I used to think (and this has happened as well, explicitly being affirmed by MB Staff) that it was always a situation where the βeta was released and then pulled from distribution because of some reason. Usually, MB staff would make a note of it when someone would (invariably) ask why someone else would have a screenshot of a version no one else had.

That may very well be the case here, but it's also possible MB has started some sort of A/B testing method with βeta releases.

Either way - it's always (theoretically) possible that a βeta release here or there can end up installed on only a few (relatively speaking) machine out in the wild.

I'm just an enthusiast and old school tester for MB, and I've seen it numerous times. Porthos and other MB staff have probably seen it much more than I have. ANd we've even seen it here in 10F also, where someone would report a version that no one else (or only 1 or 2 people) has.

So. rest assured that almost everyone here in this particular thread has seen this thing happen before and doesn't accuse someone of posting falsified information or lying in any way, manner or fashion. We all know this happens from time to time with MB.

Thanks for the explanation John.

1PW said:

Respectfully, if anyone is understandably concerned with their v4.4.1.119 beta, please consider an appropriate backup followed by an over-the-top reinstall with a known, genuine, current, release version (v4.4.0.117 - CU 1.0.1318) to ease your mind.

I am quite certain that Malwarebytes will always appreciate the feedback from their alpha & beta testers. Despite outstanding in-house testing by devs & QA folk, the bitter price to be paid is always the possible risk of rare bricked/crippled/unstable/impaired system. Still, Malwarebytes' staffers/forum volunteers will always assist the unfortunates

Perhaps this is a timely opportunity to remind those permitting beta versions that serious regressions (though rare) can occur. Personally, I would abstain from ANYONE'S beta if that computer is used in an enterprise/revenue environment, is the only computer in a family household, and especially so if an effective, working, backup plan is a foreign concept, etc.

</RANT>

If I may add one item here..........

If you wish to reinstall MBAM for any reason, the official Support Tool is the best way to go.

https://support.malwarebytes.com/hc/...s-Support-Tool

New updated MBAM ....just got it

1PW said:

Respectfully, if anyone is understandably concerned with their v4.4.1.119 beta, please consider an appropriate backup followed by an over-the-top reinstall with a known, genuine, current, release version (v4.4.0.117 - CU 1.0.1318) to ease your mind.

I am quite certain that Malwarebytes will always appreciate the feedback from their alpha & beta testers. Despite outstanding in-house testing by devs & QA folk, the bitter price to be paid is always the possible risk of rare bricked/crippled/unstable/impaired system. Still, Malwarebytes' staffers/forum volunteers will always assist the unfortunates

Perhaps this is a timely opportunity to remind those permitting beta versions that serious regressions (though rare) can occur. Personally, I would abstain from ANYONE'S beta if that computer is used in an enterprise/revenue environment, is the only computer in a family household, and especially so if an effective, working, backup plan is a foreign concept, etc.

</RANT>

f14tomcat said:

If I may add one item here..........

If you wish to reinstall MBAM for any reason, the official Support Tool is the best way to go.

https://support.malwarebytes.com/hc/...s-Support-Tool

1PW said:

I actually do agree with you but even with build 896's welcomed growth and nearly 3 months of successful use coupled with its obvious maturity, some are reluctant to run the MBST-Clean or MBST-Repair and already chafed at their imagined loss of privacy let alone their reaction to the M$ UAC popup which instantly raises their apprehensions followed by occasional abandonment of their forum thread without reply or they become less cooperative.

But yes. MBST is preferred for MB4.

As a serial βeta tester, I cannot agree with all of this enough. If you're not βeta testing with the intention of being able to fix something if it breaks (and report it regardless of if you can fix it or not) then you should not be using βeta builds, period. No matter how good a development team is, a βeta release is classified as βeta in the first place because there is a good possibility that it is not ready for consumption by the general public.

Unfortunately, some people only ever equate βeta with "new and improved" over stable, which, while it can be, more often than not it is not.

C'est la vie....

johngalt said:

As a serial βeta tester, I cannot agree with all of this enough. If you're not βeta testing with the intention of being able to fix something if it breaks (and report it regardless of if you can fix it or not) then you should not be using βeta builds, period. No matter how good a development team is, a βeta release is classified as βeta in the first place because there is a good possibility that it is not ready for consumption by the general public.

Unfortunately, some people only ever equate βeta with "new and improved" over stable, which, while it can be, more often than not it is not.

C'est la vie....

Correct. You should expect the occasional issue with beta's and be prepared to report it. That said MB seems to have few issues on beta builds. I've had more issues with duff definitions than anything else.

Yah. Their dev team is lightyears ahead of other (so-called) dev teams (I'm looking squarely at you, M$!) but things have broken before, even with MB. I've been right smack-dab in the middle of a couple of them.

Guess nobody posted this yet. 1.0.1344 is Public now.

https://forums.malwarebytes.com/topic/274681-malwarebytes-44/?do=findComment&comment=1464575






Malwarebytes community,

We want to let you know we recently released a new version your product, 4.4.0.117 component package 1.0.1344

As usual, if you don't want to wait for the 'Update Available' notification, go right ahead and retrieve the update manually by clicking "Check for updates" in Settings > General.

What’s New in 1.0.1344:

Enhanced Support for Edge Browsers
Teams Banner for Trials
Enhanced Hardening against False Positives
Enhanced detection and remediation

Some Issues now addressed:

Fixed: Update available notification does not display when auto updates is turned off
Fixed: Switching between settings tabs shows incorrect behaviour
Fixed: Malwarebytes web protection slowing down PC (CU: 1.0.1292)
Fixed: Cannot change password for user access if password is too long
Fixed: MWAC is not handling IP address exclusions specified as an IP Integer value
Fixed: Check for updates is not disabled in jump list menu while scan is in progress
Fixed: Delay RTP when Malwarebytes starts seconds does not honor restore defaults
Several UI Issues
Fixed: The Upgrade button on the RTP card navigates the user to a wrong place
Fixed: Password length restriction not visibly enforced
Fixed: Accessibility - Settings Tabs do not have focus rectangles when using keyboard navigation
Fixed: Restore Default settings doesn't work on Delay RTP when MB starts dropdown
Fixed: German. Start date and Start Time settings drop-downs are too small. Text is not visible at all
Fixed: Quarantined items in Detection History should be in chronological descending order
Fixed: Error modal typo: “Please check your internet connetion…”
Fixed: Incorrect Swedish translations
Fixed: The configure custom scan window (text and drop down menu border) does not render correctly on Russian OS
Fixed: Sign in: Forgot password requirements "e.g." instead of "ex"
Fixed: Drop down menu wheel not always visible
Fixed: Advanced Scanners page (Scan Start > Advanced Scanners) Button: Configure Scan should be Configure scan
Fixed: Settings\Notifications: Needs copy updates

Thank you so much.

-Erix

f14tomcat said:

Guess nobody posted this yet. 1.0.1344 is Public now.