Ad Muncher and WSA 8.0.1.131

[The Seeker]

Ad Muncher seems to be incompatible with Webroot SecureAnywhere, or more precisely, the Web Threat Shield. When enabled, Ad Muncher doesn't filter anything; disable the Web Threat Shield, and AM kicks back in immediately.

[pegas]

Sorry to hear about your troubles but I don't have problems at all running Ad Muncher 4.93/32930 along with WSA .131. It would be maybe worth to try to set allow for admunch.exe in the protected applications.

[The Seeker]

-{ Quote: "It would be maybe worth to try to set allow for admunch.exe in the protected applications." }-

Is this something you've had to do?

[pegas]

-{ Quote: "Is this something you've had to do?" }-
No, in my case I don't even have admunch.exe listed in the protected applications. However I have had a few issues with other applications and the clue was to let them "Allow" or "Protect".

[pegas]

I can confirm that new version of AM 4.93/33053 is incompatible with WSA .131. Having the same symptoms as The Seeker has reported. Coupled with my problems with IE9 and systray icon I am fed up quite a bit ...

[The Seeker]

Ah yes, I forgot to mention that I was using an internal beta, which has now become an official beta (http://admuncher.com/beta.pl).

[Techfox1976]

. o O {?} So AM worked fine with WSA. Then the AM people changed it and broke it from working fine with WSA... And so of course this is WSA's fault. :)

(I personally just use AdBlock Plus in FF and never see any ads or have any problems with WSA, so I can't really say that I can feel the pain here.)

((That being said, I'd take a look and see if this AM beta or any of its files - especially the DLL that is likely being injected and/or loaded into the browser - shows up as [U] in the scan logs, and is therefore Untrusted, and therefore is likely to freak out about being watched or be blocked from accessing Protected applications (like the browser), and if it is [U], then report it to Support so they can [G] it. Of course I'd expect unknown things to be blocked and not work, and I'd expect a beta of something to be unknown until somebody knows it.))

[Mongol]

-{ Quote: ". o O {?} So AM worked fine with WSA. Then the AM people changed it and broke it from working fine with WSA... And so of course this is WSA's fault. :)

(I personally just use AdBlock Plus in FF and never see any ads or have any problems with WSA, so I can't really say that I can feel the pain here.)

((That being said, I'd take a look and see if this AM beta or any of its files - especially the DLL that is likely being injected and/or loaded into the browser - shows up as [U] in the scan logs, and is therefore Untrusted, and therefore is likely to freak out about being watched or be blocked from accessing Protected applications (like the browser), and if it is [U], then report it to Support so they can [G] it. Of course I'd expect unknown things to be blocked and not work, and I'd expect a beta of something to be unknown until somebody knows it.))" }-

Do we know this was ADMunchers fault? Both ADMuncher and Webroot released new builds at about the same time...:blink: :dry: ::)

[Triple Helix]

It's best when ADMuncher comes out of Beta is to send the lines in the WSA scan log to support: http://www.webrootanywhere.com/support

Thanks,

TH

[The Seeker]

-{ Quote: ". o O {?} So AM worked fine with WSA. Then the AM people changed it and broke it from working fine with WSA... And so of course this is WSA's fault. :)" }-

Not once did I say this was WSA's fault; I merely reported that they were incompatible. I did so in the hope that another user may have experienced the same, and perhaps found a way to overcome it.

[pegas]

-{ Quote: "Not once did I say this was WSA's fault; I merely reported that they were incompatible. I did so in the hope that another user may have experienced the same, and perhaps found a way to overcome it." }-
I second you :-)
I may add that AM betas are stable and publicly deployed builds and are in fact final builds. It is more less the same how Webroot handle their WSA betas. So I can't agree with TH that we should wait for final builds. In addition Webroot proclaim that WSA is as compatible as possible. Unfortunately WSA makes me more troubles recently than NIS2012. If any new updates/upgrades are installed NIS always asks for permission to run them but NIS never blocks anything without giving me a hint at least.

[Triple Helix]

Well contact WSA support and explain the situation about Ad Muncher to see if they can fix the issue as soon as possible! http://www.webrootanywhere.com/support

TH

[The Seeker]

-{ Quote: "Well contact WSA support and explain the situation about Ad Muncher to see if they can fix the issue as soon as possible! http://www.webrootanywhere.com/support

TH" }-

Done.

[The Seeker]

-{ Quote: "Sorry to hear about your troubles but I don't have problems at all running Ad Muncher 4.93/32930 along with WSA .131. It would be maybe worth to try to set allow for admunch.exe in the protected applications." }-

I can confirm that this does indeed solve the problem for WSA 8.0.1.131 and Ad Muncher v4.93 Beta Build 33053.

[Triple Helix]

That's great to hear and it will help other members that have WSA and Ad Muncher! :thumb:

TH

[The Seeker]

This problem has now been resolved by the good people at Webroot, by adding Ad Muncher to their whitelist.

-{ Quote: "Thank you for your report. After analyzing the automatically attached logs, we have white-listed the unknown processes, which SecureAnywhere had been monitoring on your system, in our security definitions database." }-

Cheers Webroot! ;D

[Triple Helix]

-{ Quote: "This problem has now been resolved by the good people at Webroot, by adding Ad Muncher to their whitelist.

Cheers Webroot! ;D" }-

Great to hear! And if Ad Muncher gets another new update and if you run into the same problem just contact WSA support to get them to whitelist the files again! ;)

TH

[The Seeker]

-{ Quote: "Great to hear! And if Ad Muncher gets another new update and if you run into the same problem just contact WSA support to get them to whitelist the files again! ;)

TH" }-


Will do ;)