Malwarebytes 3.0.6 Component Update 1.0.75 fixes issues - gHacks Tech News

Malwarebytes 3.0.6 Component Update 1.0.75 fixes issues

Malwarebytes released a component update for Malwarebytes 3.0.6 that updates the Component Package to version 1.0.75 fixing several long-standing issues along the way.

The new update, updates the previously release preview of the component package of the software. All users, regardless of whether they have installed the preview update or not, should receive the component package update to version 1.0.75 through the software's automatic updating functionality.

The latest version is already offered as a download on the official website. So, if you have downloaded Malwarebytes just now, you have the latest version of the product installed already.

Malwarebytes 3.0.6 Component Update 1.0.75

malwarebytes 3.0.6 component 1.0.75 update

You can check the version of Malwarebytes in the following way:

  1. Open Malwarebytes on your system so that the interface of the program is visible on the screen.
  2. Select Settings > About in the interface.
  3. There you find the Malwarebytes version, and more importantly for this update, the component package version. It should read 1.0.75.

If it does not, select Dashboard to go back to the starting page. Locate Updates under scan status, and click on the link next to it there to run a manual check for update. If it is not picked up, I'd suggest you download the program anew from the Malwarebytes website to update it this way.

You are probably wondering what has been fixed in the version:

  • Fixed issue with imaging programs (such as Macrium Reflect) where large artifact files were left in the System Volume Information folder if a backup is created with anti-ransomware protection enabled
  • Fixed problem where Web Protection and Anti-Ransomware may fail to start properly
  • Fixed problem where Web Protection detections were failing on Windows 10
  • Fixed problem where DNS was not resolving properly with Web Protection enabled
  • Fixed problem where Web Protection did not show the proper block page when Bitdefender 2017 was also installed
  • Fixed an issue where certain drivers were not stopped and unloaded in Free mode
  • Fixed memory leak
  • Improved overall malware detection and remediation

The update addresses startup issues of several of the security program's components. In particular, it fixes issues with Web Protection not being enabled properly, and Web Protection related issues, such as DNS not resolving properly when the module ran in the background.

It is too early to tell whether component update 1.0.75 will fix all issues surrounding Web Protection and other components.

Malwarebytes notes that the update fixes several reported security vulnerabilities in the program as well.

Closing Words

If you run Malwarebytes 3.0 or later on your Windows system, you may want to make sure that the latest update is installed. It fixes several security issues, and long-standing issues that at least some users of the program had to live with since the release of Malwarebytes 3.0 Final.

Now You: Do you run Malwarebytes 3.x? What is your take on the new version?

Summary
Malwarebytes 3.0.6 Component Update 1.0.75 fixes issues
Article Name
Malwarebytes 3.0.6 Component Update 1.0.75 fixes issues
Description
Malwarebytes released a component update for Malwarebytes 3.0.6 that updates the Component Package to version 1.0.75 fixing several long-standing issues along the way.
Author
Publisher
Ghacks Technology News
Logo




  • We need your help

    Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

    We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats (video ads) or subscription fees.

    If you like our content, and would like to help, please consider making a contribution:

    Comments

    1. BobL said on March 2, 2017 at 5:27 pm
      Reply

      I had several of the aforementioned Malwarebytes issues and received the latest update automatically. So far, so good

    2. TelV said on March 3, 2017 at 1:46 pm
      Reply

      I had to update manually (thanks for the tip Martin), but the latest version didn’t resolve the problem I have with the self protection early start module which remains disabled.

      Version 3.0.6.1458 displayed that module as Off as well, but it could be re-enabled by clicking the button to enable it – which appeared not to do anything – exiting the application and restarting it. But version 3.0.6.1469 disabled it permanently. The latest component update hasn’t changed that.

      I noticed as well that the self protection module itself can’t be turned off either. That could cause a problem with Windows System Restore not restoring the system to an earlier date and time and which can usually be resolved by disabling the AV. But if the self protection module can’t be disabled, it would mean having to uninstall the application before running System Restore to prevent error 0x80070005 appearing when the system reboots to the desktop.

      1. Gary D said on March 4, 2017 at 12:33 pm
        Reply

        @ TelV

        I’ve had the problem with error 0x80070005 while using Win System Restore with AV programs running.
        I found that the solution was to restart the PC/Laptop in Safe Mode ( no internet connection ! ) then do a System Restore.
        In Safe Mode, AV programs are not loaded/enabled and can not interfere with System Restore.
        I’ve been doing this for about two years and it has never given any problems.

    3. Hy said on March 15, 2017 at 3:27 am
      Reply

      FWIW, Malwarebytes was one of the security programs alleged to be compromised according to reports of the latest big leak last week. Here is the list of security programs alleged to be compromised:

      • Comodo
      • Avast
      • F-Secure
      • Zemana Antilogger
      • Zone Alarm
      • Trend Micro
      • Symantec
      • Rising
      • Panda Security
      • Norton
      • Malwarebytes Anti-Malware
      • EMET (Enhanced Mitigation Experience Toolkit)
      • Microsoft Security Essentials
      • McAfee
      • Kaspersky
      • GDATA
      • ESET
      • ClamAV
      • Bitdefender
      • Avira
      • AVG

      Almost half of the other allegedly weaponized programs were portables. The following programs were said to have been successfully made to execute malicious code and steal information without the user knowing:

      • VLC Player Portable
      • IrfanView
      • Notepad++
      • Skype
      • Chrome Portable
      • Firefox Portable
      • Opera Portable
      • ClamWin Portable
      • Kaspersky TDSS Killer Portable
      • McAfee Stinger Portable
      • Sophos Virus Removal
      • Opera Mail
      • Thunderbird Portable
      • Foxit Reader
      • LibreOffice Portable
      • Prezi
      • Babel Pad
      • Iperius Backup
      • Sandisk Secure Access
      • U3 Software
      • 2048
      • LBreakout2
      • 7-Zip Portable
      • Portable Linux CMD Prompt

    4. TelV said on March 23, 2017 at 4:59 pm
      Reply

      I have a minor issue with Malwarebytes and was wondering if anyone else is experiencing it as well.

      Steps to reproduce:

      1. Either schedule a threat or hyperscan, or run one manually. When it finishes, don’t click the blue Close button on the summary window which appears to tell you that the scan has finished.
      2. Right click any .exe file and then click “Scan with Malwarebytes”.

      When I do that, I get a message that the scan can’t be run while another one is in progress (even though no other scan is actually running).

      Does anyone else see that?

      1. Martin Brinkmann said on March 23, 2017 at 5:16 pm
        Reply

        Can confirm this issue. If you click close, the scan works. Sounds like a usability issue, the summary screen seems to be seen as part of the scan job.

        1. TelV said on March 23, 2017 at 5:31 pm
          Reply

          Yes, I know. I’ve reported it to tech support, but they just seem to want me to uninstall it using their removal tool and then reinstall it again and send them the log files. I’ve already done that last week in response to a similar request, but now I’m being asked to do it again.

          So I thought I’d ascertain whether I was the only one experiencing the problem hence my post. .

          I also wanted to determine if the version I’m running which has been updated to today to 1.0.1577 includes the patch to address the so called DoubleAgent dll injection attack described here: https://thehackernews.com/2017/03/hacking-windows-dll-injection.html

          However, they don’t respond to the question.

        2. Hy said on March 23, 2017 at 8:22 pm
          Reply

          @TeIV: Interesting reading–thanks for posting the link. For those who didn’t click through:

          “Here’s the list of affected security products:

          Avast (CVE-2017-5567)
          AVG (CVE-2017-5566)
          Avira (CVE-2017-6417)
          Bitdefender (CVE-2017-6186)
          Trend Micro (CVE-2017-5565)
          Comodo
          ESET
          F-Secure
          Kaspersky
          Malwarebytes
          McAfee
          Panda
          Quick Heal
          Norton”

    5. Hy said on March 23, 2017 at 8:43 pm
      Reply

      So I’ve been reading almost nothing but bad stuff on here about the new MB 3, but after the nag to upgrade suddenly and repeatedly appeared, I decided to see for myself what the fuss was about. EOL for 2.2.1 is in June anyway, my license is up in August, so I thought I’d take the next five months to evaluate the new version and make a decision about whether to renew or not. Running MB 3.0.6.1469, component package 1.0.75, update package 1.0.1574, and the sky hasn’t fallen in yet, I’m happy to report. No issues at all so far, actually. And funnily enough, it’s using about the same and sometimes less RAM that version 2.2.1 was (about 335-400 megs compared to 380-390 or so). Running it next to Emsisoft AM and Online Armor FW with mutual exclusions set up in all three. I’ll keep an eye on MB 3.0.6 to see if any issues arise…

      1. Hy said on March 23, 2017 at 8:46 pm
        Reply

        P.S. Forgot to say: running it on Win 7 Pro 64-bit.

      2. TelV said on March 24, 2017 at 3:06 pm
        Reply

        So you’re saying the right click issue I mentioned which Martin also confirmed isn’t occuring on your system?

        1. Hy said on March 24, 2017 at 9:24 pm
          Reply

          Third day running and no problems at all, to my surprise, after all that I heard before giving it a try. I have to say honestly: if Malwarebytes continues to perform this well I may very well renew my annual premium subscription later this year.

          I haven’t tried to do what you mentioned about trying to scan a random exe before the previous scan has been closed, but I wouldn’t regard it as an issuse, minor or otherwise. I think Martin is correct when he says in his reply to you above that “the summary screen seems to be seen as part of the scan job.” In other words, even if actual scanning per se has stopped, until you click “Close” and close that scan job, you may not open another one.

      3. Gina said on May 3, 2017 at 10:42 pm
        Reply

        Have you tried to do a System Restore with the new upgraded version? I also run Windows 7 Pro, 64 bit, and after the Malwarebytes upgrade on my computer (around the first week in April) I had a problem not being able to do a System Restore. I contacted Malwarebytes by email. After 10 days of not hearing from them, I decided to just uninstall the software. I uninstalled Malwarebytes (in Safe Mode), did some registry cleans and reinstalled the OLD VERSION (2.2.1.1043) of Malwarebytes (from disc). So far, no problems with System Restore.

    6. chesscanoe said on March 23, 2017 at 9:50 pm
      Reply

      Even though I paid for MB a while ago, I don’t have it installed. Too many questions and problems for me. As someone said, “What, me worry?” It’s not worth the aggravation to use in my humble opinion.

    7. John McCulloch said on April 3, 2017 at 6:16 pm
      Reply

      Had to deactivate version 3.06 and uninstall on 64bit Windows 10, as was causing the Dreaded Blue Screen of Death – Bad Pool Header error. Reverted to v2.2.1.1043 as an interim measure.

    8. AJ North said on May 3, 2017 at 9:37 pm
      Reply

      Malwarebytes 3.1.0.1716 Beta has been released (2017.05.03), so there may be some real hope on the horizon; expect the final version in the near future. Here is the changelog:

      Performance/protective capability:
      Multiple enhancements result in reduction of memory usage
      Faster load time and responsiveness of third-party applications
      Improved performance of Web Protection
      Faster Malwarebytes 3 program startup time and responsiveness of user interface
      New detection and protection layer with machine learning based anomaly detection (to be deployed gradually even if it shows “enabled” under Settings)
      Improved Self-Protection by requiring escalated privileges to disable protections or deactivate a license
      Enhanced malware protection techniques and remediation capabilities
      Added an automatic monthly scheduled scan in Free mode

      Usability:
      Added ability to control the priority of manual scans on the system
      Added setting to turn off ‘Real-Time Protection turned off’ notifications when protection was specifically disabled by the user
      Added ability to exclude the last website blocked by Web Protection via the tray menu
      Fixed several defects related to configuring Custom Scans, including selecting child folders and fixing issues with touch screens
      Fixed problem where a right-click context scan appeared broken after scheduled scan due to misleading “Cannot start a scan while another one is in progress” message
      Fixed issue where you could not add or edit a scheduled scan in Spanish and some other languages
      Fixed issue where scan could appear stuck on Heuristics Analysis when it had actually completed successfully
      Fixed issue where Self-Protection setting would fail to toggle correctly after an upgrade

      Stability/issues fixed:
      Fixed several crashes in the Web Protection module
      Fixed issue where Ransomware Protection would be stuck in ‘Starting’ state after a reboot
      Fixed a conflict with Norton that caused web pages not to load and plug-ins to crash in Chrome
      Fixed issue with WMI protection technique in Exploit Protection that could cause Office applications to crash
      Fixed several crashes related to the service and tray
      Fixed many other miscellaneous defects and user interface improvements

    9. AJ North said on May 11, 2017 at 2:13 am
      Reply

      How do I upgrade to the latest version of Malwarebytes 3?

      The latest version of Malwarebytes 3 is [v3.1] released on [5/10/2017]. Users of Malwarebytes 3 [v3.0.6] and older should upgrade to receive the latest updates.

      To upgrade:

      Go to the Products page on our website at http://www.malwarebytes.com/products/ and click Download next to Malwarebytes 3.
      Locate the installer file in your Downloads folder (or other saved location).
      Double-click the installer file and run the program, and follow the installer instructions to complete the installation.

      https://support.malwarebytes.com/customer/portal/articles/2679359-how-do-i-upgrade-to-the-latest-version-of-malwarebytes-3-0-?b_id=15026

    Leave a Reply