someone in the French section reported some blocking from Avast on Google pages, using VPS 110427-1. His issue got solved after updating to 110427-2. I personally didn’t have any problem with the old VPS but I just updated anyway ;D
http://forum.avast.com/index.php?topic=77127.0
ps: hard to believe this has happened again :
I’m trying to figure out why I’ve only seen it posted in the forums and not on the blog or the main webpage AGAIN. Well, last time it was posted on the blog at least. This time, only in a few topics on the forum. Luckily we’ve been quick to notify the users that it’s just a FP.
yeah what I still don’t get is why I didn’t get any issue with the “bad” VPS…
Me either. The last FP issue happened at one of my locations that I was working at, with an AMS Mirror and ADNM console. One computer got the bad VPS version, but the computer that I was working on didn’t.
I guess we’re lucky and the computers that we’re working on don’t download the bad update in time, and instead it downloads the good one. Not quite sure.
It also depends on how long the bad VPS update is available, and the update interval you have set in Avast!
Greetz, Red.
the thing is that I’m pretty sure I’ve used 110427-1 (so the supposed to be bad one) a couple of hours as I updated manually to get it.
I also had the “bad” VPS, but didn’t use any Google image thingies.
Did you…??
no I don’t think so…so it just affected that (image search) and nothing else on Google?
Informing about such issues is what the ‘avast! News Service’ would be ideal for (instead of the current useless advertisements).
Not only, but mostly.
asyn
No bad idea, imo.!!
+1 that would be the very least they could do in such cases
Good idea
Greetz, Red.