Confused - Disabled.SecurityCenter issue

[keithy397]

Hi,

I have had MBAM about 6 months now (love it!) and have dealt with many nasties it found ok but I ran MBAM earlier and have 2 issues with the Disabled.SecurityCenter entries. I have read some other posts here regarding the issue but they don't really answer the question for me.

Recently I installed the Avast anti virus beta, having had no problems with the stable version and I am unable to get it to update the definitions or program, at all. Now these 2 issues crop up and I'm wondering if they're a related problem? I made no changes to my auto updates and afaik haven't changed any security settings. (Where would I change them if I wanted to?)

I hope you understand my dilemma,

Cheers,

Keith

[GT500]

I assume you mean that Malwarebytes' Anti-Malware won't update? If so, does it work when you turn off avast!'s web shield?

As far as Disabled.SecurityCenter, that detection is meant to fix settings where the Windows Security Center is no longer monitoring your anti-virus software, firewall, etc. Since some anti-viruses will turn those settings off, this detection can often be added to your ignore list.

[keithy397]

As far as Disabled.SecurityCenter, that detection is meant to fix settings where the Windows Security Center is no longer monitoring your anti-virus software, firewall, etc. Since some anti-viruses will turn those settings off, this detection can often be added to your ignore list.

So, I can assume they were turned off by Avast and ignore them then? I've used many AV's over the years and never seen references to the Security Center before.

I assume you mean that Malwarebytes' Anti-Malware won't update? If so, does it work when you turn off avast!'s web shield?

No, I meant Avast! It just seems oddly coincidental that I lost the ability to update Avast and these items turned up in MBAM.

[GT500]

So, I can assume they were turned off by Avast and ignore them then? I've used many AV's over the years and never seen references to the Security Center before.

Unless there are other signs of infection, then that is probably a safe assumption.

No, I meant Avast! It just seems oddly coincidental that I lost the ability to update Avast and these items turned up in MBAM.

It isn't possible for detections of Security Center settings to break the update ability of an anti-virus software. avast! should be able to update unless a firewall, DNS issue, etc. are blocking it.

Please copy and paste the log from the scan into a reply.

[keithy397]

OK, thank for that GT500. Much obliged.

Here's the log:-

Malwarebytes' Anti-Malware 1.41

Database version: 3038

Windows 5.0.2195 Service Pack 4

27/10/2009 21:01:02

mbam-log-2009-10-27 (21-00-43).txt

Scan type: Quick Scan

Objects scanned: 93557

Time elapsed: 14 minute(s), 36 second(s)

Memory Processes Infected: 0

Memory Modules Infected: 0

Registry Keys Infected: 0

Registry Values Infected: 0

Registry Data Items Infected: 2

Folders Infected: 0

Files Infected: 0

Memory Processes Infected:

(No malicious items detected)

Memory Modules Infected:

(No malicious items detected)

Registry Keys Infected:

(No malicious items detected)

Registry Values Infected:

(No malicious items detected)

Registry Data Items Infected:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Security Center\FirewallDisableNotify (Disabled.SecurityCenter) -> Bad: (1) Good: (0) -> No action taken.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\FirewallDisableNotify (Disabled.SecurityCenter) -> Bad: (1) Good: (0) -> No action taken.

Folders Infected:

(No malicious items detected)

Files Infected:

(No malicious items detected)

[GT500]

Those settings that are being detected are the ones that tell the Security Center to notify you if the firewall is disabled. Since those are both set to 0 (zero) then Windows will not tell you when your firewall is disabled. If the avast! beta came with a firewall, then it is not an issue, and can be added to the ignore list.

There is nothing in that log that explains why you can't update, so unless something else is happening, then you should be able to update normally.

[keithy397]

That's great then GT500, thanks.

I still have the issue with Avast not updating, but now this issue is resolved I'll head over to Avast tomorrow and carry on where I left off!

Thanks again.