Jump to content

exile360

Staff
  • Content Count

    31,130
  • Joined

  • Last visited

  • Days Won

    48

Posts posted by exile360

  1. One of our Support leads asked that I have you try installing this patch from Microsoft to see if it corrects the issue:

    http://download.windowsupdate.com/c/msdownload/update/software/secu/2019/09/windows6.1-kb4474419-v3-x64_b5614c6cea5cb4e198717789633dca16308ef79c.msu

    Please try installing that, then restart your system and see if the issue has been resolved and let us know how it goes.

    Thanks

  2. Thanks for letting us know.  If it isn't fixed after reboot, please try a clean install, then upgrade to the beta again to see if that fixes the issue.  Instructions follow:

    1. Download and run the Malwarebytes Support Tool
    2. Accept the EULA and click Advanced tab on the left (not Start Repair)
    3. Click the Clean button, and allow it to restart your system and then reinstall Malwarebytes, either by allowing the tool to do so when it offers to on restart, or by downloading and installing the latest version from here

    Once Malwarebytes is reinstalled, open it and go to settings again and enable beta updates and update as detailed below:

    • Open Malwarebytes and navigate to settings by clicking the small gear icon in the upper right
    • Under the General tab scroll down near the bottom and enable the option listed under Beta updates and confirm that you want to allow beta updates when prompted
    • Scroll back to the top of the General tab and click the Check for updates button under the Application updates section

    Please let us know if that fixed the issue or not.

    Thanks

  3. As for the issue with Web Protection, it seems the system is having problems with security certificates:

    Application errors:
    ==================
    Error: (06/15/2021 02:46:47 AM) (Source: Microsoft-Windows-CAPI2) (EventID: 4107) (User: )
    Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    .
    
    Error: (06/15/2021 02:46:47 AM) (Source: Microsoft-Windows-CAPI2) (EventID: 4107) (User: )
    Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    .
    
    Error: (06/15/2021 02:46:47 AM) (Source: Microsoft-Windows-CAPI2) (EventID: 4107) (User: )
    Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    .
    
    Error: (06/15/2021 02:46:47 AM) (Source: Microsoft-Windows-CAPI2) (EventID: 4107) (User: )
    Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    .
    
    Error: (06/15/2021 02:46:47 AM) (Source: Microsoft-Windows-CAPI2) (EventID: 4107) (User: )
    Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    .
    
    Error: (06/15/2021 02:46:47 AM) (Source: Microsoft-Windows-CAPI2) (EventID: 4107) (User: )
    Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    .
    
    Error: (06/15/2021 02:46:46 AM) (Source: Microsoft-Windows-CAPI2) (EventID: 4107) (User: )
    Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    .
    
    Error: (06/15/2021 02:46:46 AM) (Source: Microsoft-Windows-CAPI2) (EventID: 4107) (User: )
    Description: Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
    .
    
    
    System errors:
    =============
    Error: (06/15/2021 02:42:03 AM) (Source: Service Control Manager) (EventID: 7000) (User: )
    Description: The MBAMWebProtection service failed to start due to the following error: 
    Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
    
    Error: (06/15/2021 02:32:01 AM) (Source: Service Control Manager) (EventID: 7000) (User: )
    Description: The MBAMWebProtection service failed to start due to the following error: 
    Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
    
    Error: (06/15/2021 02:30:26 AM) (Source: Service Control Manager) (EventID: 7000) (User: )
    Description: The MBAMWebProtection service failed to start due to the following error: 
    Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
    
    Error: (06/15/2021 02:26:39 AM) (Source: Service Control Manager) (EventID: 7032) (User: )
    Description: The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Malwarebytes Service service, but this action failed with the following error: 
    An instance of the service is already running.
    
    Error: (06/15/2021 02:26:34 AM) (Source: Service Control Manager) (EventID: 7031) (User: )
    Description: The Malwarebytes Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.
    
    Error: (06/15/2021 02:23:56 AM) (Source: Service Control Manager) (EventID: 7000) (User: )
    Description: The MBAMProtection service failed to start due to the following error: 
    Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
    
    Error: (06/15/2021 02:23:45 AM) (Source: Service Control Manager) (EventID: 7000) (User: )
    Description: The MBAMWebProtection service failed to start due to the following error: 
    Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
    
    Error: (06/14/2021 11:18:43 PM) (Source: Tcpip) (EventID: 4199) (User: )
    Description: The system detected an address conflict for IP address 2600:1012:b00b:3392:f04e:81da:6609:b1f9 with the system
    having network hardware address 2C-30-33-3C-4D-B0. Network operations on this system may
    be disrupted as a result.

    Please see if the information in the following Microsoft support article helps: https://docs.microsoft.com/en-US/troubleshoot/windows-server/windows-security/event-id-4107-or-event-id-11-is-logged#resolution

    If it does not, then it would be best to rule out infection as a possible cause.  To do so, please follow the instructions in this topic, skipping any steps you are unable to complete, then create a new topic in our malware removal area by clicking here and a malware removal specialist will guide you in checking and cleaning your system of any threats and hopefully resolve the issue with Web Protection and security certificates on your system.

  4. That detection looks like a false positive.  Please report it by creating a new topic here: https://forums.malwarebytes.com/forum/42-file-detections/

    To export the scan log, click on the History tab under Detection History (the right-most tab in the image you posted above), then locate the entry from the scan and double-click it to open it.

    Next, click on Export on the bottom left of the report and select the option to copy to clipboard or save it as a TXT file and post the contents in a new topic in the area I linked to above to report it as a likely false positive so that Research may correct the detection.

    Thanks

  5. Greetings,

    It looks like one of Malwarebytes' folders is waiting to be replaced on reboot, likely from a previous reinstall attempt or update.  Please restart the system first, then see if all of Malwarebytes' protection starts properly or not.

    If the issue remains, please see if a clean install corrects it:

    1. Run the Malwarebytes Support Tool
    2. Accept the EULA and click Advanced tab on the left (not Start Repair)
    3. Click the Clean button, and allow it to restart your system and then reinstall Malwarebytes, either by allowing the tool to do so when it offers to on restart, or by downloading and installing the latest version from here

    Next, if the issue persists, please open Malwarebytes and look at the Real-Time Protection card on the right and let us know which of the protection modules is/are disabled so that we can narrow down what the cause/fix might be.

    Thanks

  6. Greetings,

    I'm sorry you're having trouble activating the software, but we'll do our best to help.

    Please verify that the following processes/files are allowed in ESET's firewall and real-time protection components to make sure it isn't blocking Malwarebytes:

    C:\ProgramData\Malwarebytes\MBAMService.exe
    C:\ProgramData\Malwarebytes\mbam.exe

    Once that is done, try activating Malwarebytes using your license key again to see if it now works and let us know how it goes.

    Thanks

  7. A new beta of Malwarebytes has been released which should address this issue.  Please refer to the info in this post for details.

    If you wish to install the beta, first close any web browsers where you have the Malwarebytes Browser Guard add-on installed, otherwise you will likely need to reboot after installing the beta, then do the following:

    • Open Malwarebytes and navigate to settings by clicking the small gear icon in the upper right
    • Under the General tab scroll down near the bottom and enable the option listed under Beta updates and confirm that you want to allow beta updates when prompted
    • Scroll back to the top of the General tab and click the Check for updates button under the Application updates section

    If you try the beta, please let us know if it resolved the issue you were experiencing or not.

    Thanks

  8. A new beta of Malwarebytes has been released which should address this issue.  Please refer to the info in this post for details.

    If you wish to install the beta, first close any web browsers where you have the Malwarebytes Browser Guard add-on installed, otherwise you will likely need to reboot after installing the beta, then do the following:

    • Open Malwarebytes and navigate to settings by clicking the small gear icon in the upper right
    • Under the General tab scroll down near the bottom and enable the option listed under Beta updates and confirm that you want to allow beta updates when prompted
    • Scroll back to the top of the General tab and click the Check for updates button under the Application updates section

    If you try the beta, please let us know if it resolved the issue you were experiencing or not.

    Thanks

    • Like 1
  9. A new beta of Malwarebytes has been released which should address this issue.  Please refer to the info in this post for details.

    If you wish to install the beta, first close any web browsers where you have the Malwarebytes Browser Guard add-on installed, otherwise you will likely need to reboot after installing the beta, then do the following:

    • Open Malwarebytes and navigate to settings by clicking the small gear icon in the upper right
    • Under the General tab scroll down near the bottom and enable the option listed under Beta updates and confirm that you want to allow beta updates when prompted
    • Scroll back to the top of the General tab and click the Check for updates button under the Application updates section

    If you try the beta, please let us know if it resolved the issue you were experiencing or not.

    Thanks

  10. It sounds like a common tech support scam site/pop-up which can use your browser to detect info about your system which is likely how it determined your system make and model.

    That said, if you do see any symptoms of infection and suspect that the device might be infected, please post in our mobile malware removal help area located here: https://forums.malwarebytes.com/forum/182-mobile-malware-removal-help-support/

  11. Greetings,

    It's likely that the developer of the add-on is being paid by, is affiliated with, or is using the blocked site for some purpose such as harvesting browsing data, displaying ads, or modifying search results.  It's a fairly common issue with many add-ons, especially lesser known ones from less reputable/unknown developers.

    As for why nothing was detected, my guess would be that the add-on itself is likely not malicious and doesn't fit the criteria to be detected as a PUP (Potentially Unwanted Program) so Malwarebytes would not detect it in a scan.

  12. I have seen users running Webroot alongside Malwarebytes successfully, however I've also seen several cases where users did experience compatibility issues between the two, though they were usually resolved by excluding Malwarebytes from Webroot.

    If you can't exclude Malwarebytes, please see if quitting Malwarebytes first helps (right-click the Malwarebytes tray icon and select Quit Malwarebytes, and if it still won't let you, please try uninstalling/reinstalling Webroot and restarting to see if that allows you to do so as it may be an issue with Webroot's installation.

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.