Battlefield 3 beta and Avast 6.0.1289 (latest defs) fails to run the game from the web browser\launch system (Battlelog beta). The game\browser just sits there while searching infinitely when I try to launch the game from server selection or matchmaking.
If I disable Web Shield then everything works as expected (games found\launch etc).
I tried adding to the exclutions list…
The key word is “beta”. Often avast will not work with a particular software until the software is officially released. Have you tried a previous release of Battlefield?
I know it’s “Beta” and no there is no other version to test. It’s something to do with the way the game is launched that causing Avast to silently block it. I have checked logs etc and there is nothing (it’s blank!)
I dont want to have to disable the webshield everytime I attempt to play. I would just like to get it added to my exclusion list.
I wasn’t talking about exceptions. I just didn’t get “too deep” into details of your particular system.
In Avast 6.0.1289 (the current stable version), some changes were made to improve http traffic scanning that is not necessarily passing through your web browser.
Avastsvc.exe is the one “responsible” for that checking. If you have a firewall that needs “rules” to let some process connect (inbound and/or outbound), then I was suggesting to add this avastsvc.exe to your rules. This should solve most problems of “some http traffic being blocked by Avast”.
What the first setting in web shield does is turn the behaviour of Avast as it was before version 6.0.1289.
If you don’t know how to configure that rule in your firewall, then simply use that first setting I posted. It is not “ideal”, but it lets you do your “job”, while not degrading the security messures that much.
You don’t need to do both things if one just works for you. The firewall rule is the preferred one, and the other is there for cases where there is no other possibility.
