System not fully protected

[geranium]

Malwarebytes states the the System is not fully protected see pic.

 

What is this about please?

 

geranium

 

[HighwayHunter]

Okay man I had this similar issue and what I did to fix it was I clicked where it says check for updates, and dude your malwarebytes may be out of date, check for updates and if it updates then click fix now and see if that works.

[daledoc1]

Hi, and welcome, @HighwayHunter:
 
Sorry to hear you are having issues.
Each computer is unique.
Problems that sound "the same" most often are not.
The same is true for solutions.
They most often need to be individualized.

It is less confusing for everyone if we try to stick to "one user per topic".
As it looks as if you already have your own separate topic, it would be less confusing if you would please wait for help there.
That way, the staff and experts will be able to more easily provide both you and @geranium with individual help to get you both up and running.
 
 
@geranium:

 

Basic troubleshooting starts here, please:

• Please uninstall your current version of MBAM and reinstall the latest build - MBAM Clean Removal Process 2x
• If that does not correct the issue, then please read the following and post back the requested logs - Diagnostic Logs
• NOTE: There is an FAQ section with valuable information located here - Common Questions, Issues, and their Solutions

 

Thanks for your patience and understanding,

[geranium]

Thank you daledoc1

 

I have in the meantime tried a manual update again, as  my automatic updates have apparently not been working, and am getting the message Unable to access update server.  Is there perhaps a problem at Malwarebytes?

 

And how could the Malicious Website Protection become disabled?

 

Thanks for help

 

geranium

[daledoc1]

Hi:
 
No, things seem to be updating fine and I'm not aware of a problem with MBAM servers; then again, I am not on staff.

Nor would that explain the disabling of the realtime protection modules.
 
Each computer is unique.
There are many possible explanations for what you are seeing.
Most of them are resolved by following the steps I already suggested.
If the clean reinstall doesn't resolve it (step #1), then the staff will need to see those diagnostic logs (step #2).

When you do reinstall, you may want to try adding exclusions in your AV - the files that need to be excluded can be found HERE.

 

So, I suggest that you please try those steps and then report back.

 

Thanks,

[geranium]

Thanks daledoc.

 

I am running XP SP3 and have only the Windows firewall. I am running the free Avast and cannot see how to exclude any files and would be grateful for any help with that.

 

Thanks

 

geranium

[daledoc1]

The MBAM files that need to be excluded are listed  HERE.
Unfortunately, I'm not personally familiar with Avast; there are some instructions for an older version of both programs here.
 
Having said that, it might be easier and faster to just post back with some basic system info to help the staff.
To do so, please read the following and post back the requested logs as attachments to your next reply - Diagnostic Logs

 

Thanks,

[geranium]

I have re-installed and updated and all seems fine.

 

I just need to know how to set up the exclusion in Avast which I couldn't find how to do and your link is not helping me..

 

Thanks for help

[daledoc1]

I'm sorry, but it would take an army of full-time MBAM staff to keep up with writing & updating specific instructions for each and every version and flavor of all AV products.

The instructions provided are the generic ones that list the files in the current MBAM version to exclude in the AV.

That's probably the best we can do for Avast resources here at the MBAM forum.
 
Your best bet to learn how to configure Avast might be to check with the "help file" in the program, the support page of the company website, the user forum (unfortunately, the Avast user forum has been offline because of hacking for a while now) or other resources?
 
Or perhaps someone will come along here who has personal experience with Avast.
 
Having said all that:
If everything is working OK, then it's not always strictly necessary to set those mutual exclusions (it can be helpful in certain cases, e.g. on older, slower machines).
If not, then please read the following and post back the requested logs - Diagnostic Logs

 

Thank you,