malwarebytes manual update rules for version 3

This is actually the preferred reflex, since PUPs aren't necessarily harmful, and extracting them can disable the program that they came with.

Malwarebytes defaulted to placing these files in quarantine rather than deleting them. 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). This was the only truly major issue we saw in version 3.0, so addressing it brings Malwarebytes back up to 'recommended' status. However, we can report that we didn't see any BSODs in Windows 10 during our testing of 3.2.

As a result, there wasn't a lot to distinguish the paid version from the free one. 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. 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. 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.

Malwarebytes manual update rules for version 3