Malwarebytes lifetime for Windows is a next-generation antivirus replacement. The first of its kind for home users, Malwarebytes for Windows employs four independent technology modules—anti-malware, anti-ransomware, anti-exploit, and malicious website protection—to block and remove both known and unknown threats. For that people, Malwarebytes is the perfect software to install on their computers. It won’t slow down your PC and you can work with your PC like you used to be, after the installation. Malwarebytes latest version has an amazing capability of removing infections on the PC. The database of Malwarebytes anti-malware software is updating daily.
Malwarebytes 3.0 was a major update when it arrived in December 2016 -- and like many major updates, some aspects were a little rough, particularly stability within Windows 10. With version 3.2, the company claims it has corrected some major issues, so let's take a look at how this revision stacks up.
It's stable in Windows 10: With version 3.0, some users (us included) experienced seemingly random blue-screen errors in Windows 10 unless we disabled most or all of Malwarebytes' active scanning functions. As a result, there wasn't a lot to distinguish the paid version from the free one. However, we can report that we didn't see any BSODs in Windows 10 during our testing of 3.2. This was the only truly major issue we saw in version 3.0, so addressing it brings Malwarebytes back up to 'recommended' status.
The scanning engine remains high-quality: During our tests, the app's malware scanner picked up some files and a Registry entry left over from an apparently incomplete uninstallation of a third-party driver management utility that, according to Malwarebytes, may have bundled a potentially unwanted program (PUP). Malwarebytes defaulted to placing these files in quarantine rather than deleting them. This is actually the preferred reflex, since PUPs aren't necessarily harmful, and extracting them can disable the program that they came with. Generally speaking, Malwarebytes' scanning tech is rated favorably by independent testers, such as West Coast Labs and Google's VirusTotal service, and it's cultivated a reputation for not bogging down your PC.
Detailed, plain-English explanations: While other security vendors often slather on fancy-sounding terminology, Malwarebytes is good at telling you exactly what a given feature is doing. Take the 'Usage and Threat Statistics' toggle, for example. This covers the anonymous usage data that it collects. In the description on its website, Malwarebytes itemizes basic things like, how many people are running the free version, trial version, and subscription versions? Where is Malwarebytes being used globally? What malware is being detected the most, and how often?
Its full privacy policy even includes detailed and simplified explanations side-by-side. This kind of transparency about your data -- and the deliberately limited extent of it -- is good to have, and it's not as common in the security industry as it should be.
Limited testing by independent labs: The company asserts that the average 'zero day' malware (the kind that's too new for there to be reliable detection/removal) has only a 55 percent detection rate, which can make a given antimalware app look worse than it is when subjected to a barrage of zero-day infections during testing. Therefore, Malwarebytes does not submit its apps to the full gauntlets provided by AV-Test and AV-Comparatives, whose testing takes special notice of zero-day security. However, if Malwarebytes wants to be recognized among its competition, we'd argue that it needs to submit its apps to the same rigorous standards as the competition, even if those standards can create perception issues.
Now that Malwarebytes appears to have fixed its stability issues in version 3.2, the user experience is rounded out nicely. However, we'd like to see Malwarebytes go through the gauntlets set up by AV-Comparatives and AV-Test to get a better picture of how it stacks up against the competition.
While installing Malwarebytes for Windows, you may encounter a runtime error message similar to the example below.
Runtime Error (at xx:xxx):
Could not call proc.
If you are attempting to install on XP or Vista, see Malwarebytes support for Windows XP and Vista for more information.
Malwarebytes for Windows needs to be able to save files to the %TEMP% folder during installation. If the Malwarebytes for Windows setup file encounters Runtime Error: Could not call proc. during installation, this suggests the %TEMP% folder is either located on a network or Random Access Memory Drive, also known as a RAMDrive or RAMDisk.
If Malwarebytes for Windows displays Runtime Error: Could not call proc.during installation, follow the steps below to install Malwarebytes for Windows.
A fix for this issue will be released in a future upgrade of Malwarebytes for Windows. If Malwarebytes for Windows notifies you an upgrade is available, we recommend installing the upgrade to receive the latest features, improvements, and fixes. To see which upgrades have been released, refer to the Malwarebytes for Windows Release History.