Virtual machines are not all that common for the average user,
I'm certainly not,
I'm not into testing security suites,
Over the years I found three utilities to keep me safe in what ever situation I'm in,
Or at least a sense of protection,
When one updates to a new version and it goes as bad as mabm 2.0 there's reason to sit back,
Nagging to upgrade is never really productive not in this short of time span,
Cheers.
Since Malwarebytes is not my only line of defense (and has not "found anything" in years), I feel safe running the beta
A Guy
Logging into a hidden admin account is not a safe thing to do for a novice to fix a third party program
Glad you like testing stuff I personally like Tried and True/ flawless installs and upgrades,
When that doesn't happen then there's cause for alarm and hesitation = Holdouts
I may ask mabm why the turn to Nagware is warranted in such a short life of 2.0 ?
Good idea, I had never logged into the built-in Admin account before.I logged into the built in (hidden) admin account
Built-in Administrator Account - Enable or Disable
And ran the update. Which worked. Disabled that account again, logged back into my account, and the problem was gone. Don't ask me why, some permission was reset I'd imagine. All I know is it worked!
A Guy
https://forums.malwarebytes.org/inde...owtopic=149022
AdvancedSetup said:
Changelog:
Malwarebytes Anti-Malware 2.0.2.1012 (Released May 20, 2014)
Improvements:
Changed some of the terminology used in scan results and scan logs to make them clearer
Enabling or disabling self-protection should now be more responsive under most circumstances
Each language name is now listed in its native tongue rather than being translated to make switching languages easier
Blank window is no longer observed flashing on screen during startup and shut down of system when Malwarebytes Anti-Malware is running in the tray on Windows Vista and newer operating systems
Issues Fixed:
Several crashes and BSOD issues fixed with rootkit scanning
Scan speed improved with rootkit scanning enabled under some circumstances
Rootkit scans should no longer hang indefinitely under certain conditions
Compatibility issues with certain VPN client software fixed
Protection no longer fails to start after upgrade under some circumstances when self-protection is active prior to upgrading
Entire General Settings tab now responds to clicks correctly
Several issues with Access Policy restrictions not restricting access as they should
Editing the Access Policy password no longer results in restricted areas of the software being inaccessible when the correct password is entered
Access Policy feature now functions when Bitdefender Total Security is installed
Manual scan of individual files and folders using context menu scan feature in Explorer no longer results in the scan failing to run under certain circumstances
Green checkmark status is no longer indicated when Malwarebytes Anti-Malware is unable to reach update servers when attempting to update
Text is no longer cutoff in the UI on Windows XP or when the 'Classic' theme is used on Windows 7
Scan time is now reflected accurately at the end of a scan
Quarantined objects remain listed correctly in Limited User Accounts when restoration of an object fails due to lack of permissions
Some words in UI which were not translated into non-English languages now are when those languages are selected
Driver left behind during uninstallation of Malwarebytes Anti-Malware is now removed as it should be when the product is uninstalled
Cecile Nguyen
Social Media Strategist
Odd Bill I have a Public Beta version with the same build number I got on May14 2014.
I sent Ron (Advanced Setup) a PM about it.
It is the same build.
The beta went gold.
If you are already running 2.0.2.1012, there is nothing to update.
(Confirmed by MBAM staff via PM at their forum.)
I can confirm that Malwarebytes Anti-Malware 2.0.2.1012 (Released May 20, 2014) is the same build as the beta version 2.0.2.1012 as well...
Quote
