malwarebytes blocking avast?

[mytimbuk2]

This action was printed in my Logs with Malwarebytes Pro, it appears to be blocking an outgoing IP related to the Avast program name? Any idea what this means?

IP-BLOCK   173.199.172.XXX (Type: outgoing, Port: 62254, Process: avastsvc.exe)

Thanks

[DavidR]

It isn't alerting on avast, this is their so called malicious site blocking at work and it doesn't like that IP address.

The avastSvc.exe is the main controller for avast, this includes the web shield localhost proxy. When you are using your browser all http traffic/connections are redirected through the web shield proxy so that the content can be scanned. So something is trying to connect to that IP.

The problem is MBAM isn't reporting what is initiating the connection but the avast process controlling the redirection through the proxy.

Personally I feel this mbam feature is more hassle than it is worth, it isn't just malicious sites that are pinged, but also other categories; not to mention that you have both the web shield and network shield looking after this type of thing. I have disabled this on both of my mbam Pro installations, that decision is however up to you.

I don't know why you have obfuscated that last part of the IP as we can't check it out.

[mytimbuk2]

Not sure where my replies went, I answered twice. First time I got the irritating CAPTCHA Phrase wrong and lost the entire reply, second time it said that it posted, but apparently didn't.  I guess I'll just say thanks for your reply. Both Avast & Malwarebytes have apparently stopped some evils from implementing, so I guess I'll live with it or suffer the consequences. 
Thanks

[DavidR]

You're welcome.

Always a good idea to do a copy (Ctrl+C) of your post before posting, just in case, saves having to type again if you have a problem. The Captcha can be a pain, but also for the spammers, you only have one more post (3) were you will need to use the Captcha function.

[Para-Noid]

I asked that very question on the MBAM forum. The answer I received is to the effect that MBAM is not really blocking avastsvs.exe
I have learned to ignore it as nothing is wrong. It's that MBAM detects something that isn't there. You and your computer are fine. 

[bedebill]

Hi all I am running avast do I need to download Malwarebytes AntiMalware too ?

[CraigB]

Hi all I am running avast do I need to download Malwarebytes AntiMalware too ?

Its a great program and would be an added benefit to your security setup, update it and run a weekly quick scan with the free version or there is the paid Pro version.

[rob24]

It isn't alerting on avast, this is their so called malicious site blocking at work and it doesn't like that IP address.

The avastSvc.exe is the main controller for avast, this includes the web shield localhost proxy. When you are using your browser all http traffic/connections are redirected through the web shield proxy so that the content can be scanned. So something is trying to connect to that IP.

The problem is MBAM isn't reporting what is initiating the connection but the avast process controlling the redirection through the proxy.

Personally I feel this mbam feature is more hassle than it is worth, it isn't just malicious sites that are pinged, but also other categories; not to mention that you have both the web shield and network shield looking after this type of thing. I have disabled this on both of my mbam Pro installations, that decision is however up to you.

I don't know why you have obfuscated that last part of the IP as we can't check it out.

How do you disable the part you are talking about in mbam (I have the free version). I ask as I still have not updated Avast free to 7.0.1474 from 7.0.1466 still fearing a crash or a useless pc at the end of it. I thought maybe to disable this part of mbam might lessen the chance of problems if I update, though I daresay you will say there are now none 

[iroc9555]

How do you disable the part you are talking about in mbam (I have the free version).

MBAM Free version does not have real time protection. Nothing to disable then.

[rob24]

OK thanks!

[iroc9555]

OK thanks!

You are welcome.

BTW you should try 1474. I have XP spk3 as you do and I have not encountered any trouble.

[rob24]

OK thanks!

You are welcome.

BTW you should try 1474. I have XP spk3 as you do and I have not encountered any trouble.

Have successfully updated to 1474. No probs except on reboot shutdown and on closedown again, I got some sort of dialogue box on screen about not able to write to memory, then a load of numbers. But other than that showing for a 2-3 seconds it was fine and closed or restarted OK.

[iroc9555]

Have successfully updated to 1474. No probs except on reboot shutdown and on closedown again, I got some sort of dialogue box on screen about not able to write to memory, then a load of numbers. But other than that showing for a 2-3 seconds it was fine and closed or restarted OK.

Try to get a screenshot of the alert and attach it here. Maybe someone can figure it out.

[rob24]

Had to snap it with a phone camera. It appears just before the pc switches off. I don't need to do anything, it doesn't stay there more than about 3 seconds.
Hope you can see it OK.

[iroc9555]

That is a Skype service. Try to update program or better yet uninstall and reinstall again.