Unable to access update server Malwarebytes Free 2.1.8.1057

[philecreed]

Windows 7, SP1.

For the past 2 days, when I try to update Malwarebytes, the Database Version blue bar activates but I get message "unable to access update server". Then message changes to v.2015.12.19.04, suggesting that I now have all the current updates. But do I really have the updates?

 

I  saw a similar post where the reply to the user was asked to check system time, reboot, and, if that did not resolve the problem, download and run 2 diagnostic programs and attach the 3 generated files to his reply. I did all this and am attaching the three files hereto. 

 

I hope someone can help resolve this update issue.

 

Addition.txtCheckResults.txtFRST.txt

[daledoc1]

Hi:

 

A quick check of your logs shows a TON of items in MBAM quarantine and it looks as if MBAM was last installed back in August.

 

There are some other problems, as well, such as broken Windows Search Service and possible hard disk errors, and some other anomalies:

 

=================== Event log errors: =========================

Application errors:
==================
Error: (12/19/2015 11:13:47 AM) (Source: Windows Search Service) (EventID: 7010) (User: )
Description: The index cannot be initialized.

Details:
    The content index catalog is corrupt.  (HRESULT : 0xc0041801) (0xc0041801)

Error: (12/19/2015 11:13:47 AM) (Source: Windows Search Service) (EventID: 3058) (User: )
Description: The application cannot be initialized.

Context: Windows Application

Details:
    The content index catalog is corrupt.  (HRESULT : 0xc0041801) (0xc0041801)

Error: (12/19/2015 11:13:47 AM) (Source: Windows Search Service) (EventID: 3028) (User: )
Description: The gatherer object cannot be initialized.

Context: Windows Application, SystemIndex Catalog

Details:
    The content index catalog is corrupt.  (HRESULT : 0xc0041801) (0xc0041801)

Error: (12/19/2015 11:13:47 AM) (Source: Windows Search Service) (EventID: 3029) (User: )
Description: The plug-in in <Search.TripoliIndexer> cannot be initialized.

Context: Windows Application, SystemIndex Catalog

Details:
    Element not found.  (HRESULT : 0x80070490) (0x80070490)

Error: (12/19/2015 11:13:34 AM) (Source: Windows Search Service) (EventID: 3029) (User: )
Description: The plug-in in <Search.JetPropStore> cannot be initialized.

Context: Windows Application, SystemIndex Catalog

Details:
    The content index catalog is corrupt.  (HRESULT : 0xc0041801) (0xc0041801)

Error: (12/19/2015 11:13:34 AM) (Source: Windows Search Service) (EventID: 9002) (User: )
Description: The Windows Search Service cannot load the property store information.

Context: Windows Application, SystemIndex Catalog

Details:
    The content index database is corrupt.  (HRESULT : 0xc0041800) (0xc0041800)

Error: (12/19/2015 11:13:34 AM) (Source: Windows Search Service) (EventID: 7042) (User: )
Description: The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.

Details:
    The content index catalog is corrupt.  (HRESULT : 0xc0041801) (0xc0041801)

Error: (12/19/2015 11:13:33 AM) (Source: Windows Search Service) (EventID: 7040) (User: )
Description: The search service has detected corrupted data files in the index {id=4700}. The service will attempt to automatically correct this problem by rebuilding the index.

Details:
    The content index catalog is corrupt.  (HRESULT : 0xc0041801) (0xc0041801)

Error: (12/19/2015 11:13:33 AM) (Source: Windows Search Service) (EventID: 9000) (User: )
Description: The Windows Search Service cannot open the Jet property store.

Details:
    0x%08x (0xc0041800 - The content index database is corrupt.  (HRESULT : 0xc0041800))

Error: (12/19/2015 11:13:32 AM) (Source: ESENT) (EventID: 455) (User: )
Description: Windows (3496) Windows: Error -1811 occurred while opening logfile C:\ProgramData\Microsoft\Search\Data\Applications\Windows\MSS043EA.log.


System errors:
=============
Error: (12/19/2015 11:13:48 AM) (Source: Service Control Manager) (EventID: 7031) (User: )
Description: The Windows Search service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service.

Error: (12/19/2015 11:13:48 AM) (Source: Service Control Manager) (EventID: 7024) (User: )
Description: The Windows Search service terminated with service-specific error %%-1073473535.

Error: (12/19/2015 11:13:16 AM) (Source: Service Control Manager) (EventID: 7000) (User: )
Description: The Joulemeter Service service failed to start due to the following error:
%%1053

Error: (12/19/2015 11:13:16 AM) (Source: Service Control Manager) (EventID: 7009) (User: )
Description: A timeout was reached (30000 milliseconds) while waiting for the Joulemeter Service service to connect.

Error: (12/19/2015 09:44:31 AM) (Source: Disk) (EventID: 11) (User: )
Description: The driver detected a controller error on \Device\Harddisk1\DR1.

Error: (12/19/2015 09:44:30 AM) (Source: Disk) (EventID: 11) (User: )
Description: The driver detected a controller error on \Device\Harddisk1\DR1.

Error: (12/19/2015 09:44:30 AM) (Source: Disk) (EventID: 11) (User: )
Description: The driver detected a controller error on \Device\Harddisk1\DR1.

Error: (12/18/2015 06:54:15 PM) (Source: Disk) (EventID: 11) (User: )
Description: The driver detected a controller error on \Device\Harddisk1\DR1.

Error: (12/18/2015 02:00:13 PM) (Source: Schannel) (EventID: 4120) (User: NT AUTHORITY)
Description: The following fatal alert was generated: 10. The internal error state is 10.

Error: (12/18/2015 02:00:13 PM) (Source: Schannel) (EventID: 4120) (User: NT AUTHORITY)
Description: The following fatal alert was generated: 10. The internal error state is 10.

 

So, for starters, you may wish to try a clean reinstall/upgrade of MBAM, as per the steps here: MBAM Clean Removal Process 2x.

That might get MBAM back up and running.

Be sure to reboot when prompted by the removal tool, and it's not a bad idea to reboot again after the reinstall, for good measure.

>>>I would definitely do this, though, because you are NOT running the current program version, which is 2.2.0.1024.

 

However, cleanly reinstalling/upgrading MBAM will not fix the other issues with the system.

So, even if MBAM does seem to be working OK after the clean reinstall, you might want to head over to another area of the forum for a deeper look at the system.

The tools needed cannot be used here in this section of the forum.

So, although it's not clear that you are or may have been infected, the other forum is the best place to get some free, expert help checking to be sure.

The helper there can assist with running a check disk, repairing the Windows Search Service, and other problems.

To start the process, I suggest following the steps here: Available Assistance for Possibly Infected Computers and then posting a FRESH, NEW set of FRST logs in the other forum area.

(When you run FRST again, please place a checkmark in the "Addition.txt" option before running it, so that it will produce both logs.)

 

Thanks,

[philecreed]

Many thanks, daledoc1. The reinstall of Malwarebytes solved the problem. I'll see what the scan shows and then check the hard drive and the other problems.

Phil

[daledoc1]

Super!

 

I'm glad you were able to resolve your issue.

 

Thanks for taking the time to let us know.

 

Cheers,