Malwarebytes 3.0 - Known Issues in Malwarebytes for Windows Support Forum Posted December 8, 2016 · Edited April 25, 2017 by bdubrow Updated for Malwarebytes 3.0.6 Known Issues for Malwarebytes version 3.0.6 Last updated February 3, 2017 If you are running an earlier Malwarebytes version, and your upgrade to Malwarebytes 3.0.6 fails for any reason, simply uninstall the earlier version and then reinstall new version. If mbae64.sys errors during installation, and sometimes, even a clean install won't remove it, you have in such case to use a FRST script to remove the Self-protection service and driver. Or they can be deleted both in Safe Mode. Under certain circumstances Web or Exploit protection will not start for some systems. Please try this workaround. There is a compatibility issue with Malwarebytes 3.0.6 and F-Secure Deepfreeze (either enable compatibility mode, or add Malwarebytes folders to F-Secure exclusion list) Read this KB Article for more details. There is an issue with imaging programs (such as Macrium Reflect) where large artifact files are left System Volume Information file if a backup is created with anti-ransomware protection enabled. There is a conflict with BitDefender 2017 safe pay plugin. Enhancements continue to be made to overall Memory and CPU usage and will be released subsequently. For computers left idle in certain circumstances, scans can appear to be stuck on Heuristics Analysis when it has actually finished (Open and close the GUI for workaround). If WMI services are off or disabled, the user will see a “failure to connect to service” error after installing. In Spanish and some other few languages the user will not be able to edit or add a scheduled scan. New scans don't reset "Threats Quarantined" counter on Scan Summary page. When upgrading from 2.2.1 Managed Applications (Anti-Exploit) settings are not carried over but instead all Advanced Settings will be reset to the current defaults. Any User Access Policy created in MBAM 2.x is not migrated when upgrading from MBAM 2.x to Malwarebytes 3.0; a new policy will have to be created.