Anonymously help the community by providing usage and threat statistics: Unchecking this option will prevent Malwarebytes Support Tool from sending anonymous telemetry data on usage of the program. It is not recommended to use any Repair System options unless instructed by a Malwarebytes Support agent. Repair System: Includes various system-related repairs in case a Windows service is not functioning correctly that Malwarebytes for Windows is dependent on. All user configurations and other data are removed. The Premium license key is backed up and reinstated. 
Clean: Performs an automated uninstallation of all Malwarebytes products installed to the computer and prompts to install the latest version of Malwarebytes for Windows afterwards. The information is saved to a file on the Desktop named mbst-grab-results.zip and can be added as an email attachment or uploaded to a forum post to assist with troubleshooting the issue at hand. As part of this process, Farbar Recovery Scan Tool (FRST) is run to perform a complete diagnosis. Gather Logs: Collects troubleshooting information from the computer. The Advanced menu page contains four categories: Place a checkmark next to Accept License Agreement and click Next You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. At this moment I still have not decided on upgrading to the legacy v3.5.1 as this version seems to consume more system resources (when I tried that some years back).Īnyway can someone please investigate and tell me what's going on? That would be much appreciated.ĭouble-click mb-support-X.X.X.XXXX.exe to run the program 
What I fear is that database support for older version may have been discontinued without further notice. It's not like the program fails to access the update server resulting in the "Cannot connect to server" message and such. This time however, pressing "Updates" multiple times would still result in the "No updates available" message (see attached). I know there have been previous situations where the databases have not been updated for a few days, but after which things have gotten back to normal.
It's May 23 as we speak and the Database version is still stuck at v2022.05.19.04. Have been successfully performed manual definitions updates daily, until after May 19.
Hello, I'm still hanging onto the old MBAM 2.
0 kommentar(er)
