The workaround doesn’t work if I unchecked “Scan traffic from well-known browser processes only”
once in 20-30? here it is on every boot up and every time it comes back from sleep etc…on multiple pc’s. it may only last a few minutes but its ANNOYING and should not be like that
posted work around does not work still i have to have the box checked or no good.
thanks zfactor.
It seems that the changes we have done in WebShield has no connection with your problem. Must be something else.
Edit: as I can see your problem is not new with this version at all. With avast uninstalled it goes away? What is your avast edition? (AIS/Pro/Free) ?
Hi, today I was able, after some connecting and disconnecting of networks to reproduce the issue here on my laptop with Windows7 64bit + Wifi. However it has currently no avast version installed. So I guess it does not help much, yet the exclamation mark is there.
According to the reports, this is a recurrent behaviour, not a one time thing. I guess there is a reason why users are relating this problem to Avast, so there is a need to keep looking and reporting.
WITHOUT avast problem is gone 100% it started the the first beta after the 1203 version (i think) and even with the final version still happens. when i uninstall avast problem gone…win7 x64 as well as win7 x86 tested on both
I have about 10 reboots on the IP: 213.199.181.90 exclusion, and all came back good. No exclamation mark here, but to be fair, I didn’t have any after I checked the “only well known browsers” setting in the Web Shield, so I’m not sure which one fixed it, but so far, so good.
same here 
the yellow exclamation mark on wireless tray icon or wired tray icon is reproducible when “Scan traffic from well-known browser processes only” is unmarked.
This is also reproducible in windows vista no earth globe on the tray icon.
Not sure I understand. When you put the IP address to the exclusion list, did you uncheck the “only well-known browsers” or not?
The IP address exclusion was supposed to help even if it the box stays unchecked (which is the recommended configuration).
Thanks
Vlk
Sorry for the confusion. I currently have both recommended fixes enabled. The IP fix, and the “Well known browser” fix too. Since I posted earlier, I have rebooted about 8 more times with both fixes enabled, and I have not seen one yellow! on my taskbar. So far, so good Vlk.
Well the first fix (checking that box in WebShield’s settings) is confirmed to “fix” the issue. However, it’s not really recommended as it slightly degrades the level of protection.
We were hoping that the second fix would solve the issue as well, but it seems that not really…
Vlk
may i ask which ip address should i add?
i have not always the same ip
Read the thread…!! :
I don’t know whether it helps or not to find a solution:
In the last time during “Win7 Backup” of my system partition, I do that about once a week, my WLAN icon in the system tray half way through allways got a yellow exclamation sign or went totally off line. Both situations covered about 50 % happenings each.
Since I never had the idea it could be connected to avast! operation I was just living with that.
The situation could be cleared only by either rebooting the machine or by deactivation and activation of the WLAN driver in the device manager.
Reading this thread I applied “just for fun” the second proposed fix: “ignored IP 213.199.181.90”
Since that time during multiple backups the WLAN system stayed allways untouched.
Magic…? :o :o :o or what…?
please hope to have a fix soon i have a number of clients i recc avast to and now i am getting calls about this from people who are frustrated…
But what about the set Vlk suggested as workaround (web shield → expert settings → well known browsers only) ?
All other users in this topic seem to “solve” the problem, either by manually recognizing the connection, or using at least 1 of the 2 workarounds.
i understand that and yes it does “fix” it. BUT many of my every day customers are not going to know how nor are they going to research it here. they expect it to work out of the box…properly. i deal with a TON of older people and mom’s etc who (and i am NOT singling them out here) who are not computer savy. so they call me wondering why things are not working normally…
I’m sorry to hear that. I guess it will take some time for Avast Team to find a real “automatic” solution.
But I do want to express my opinion on this particular setting that Avast added in the latest program update.
The “wise” default setting, IMHO, would had been to keep the setting so to make Avast work just as before. That means, at least for program updates, to scan traffic in well known browser only. So users changing this setting would know to test it and change it according to their needs. By forcing the new setting to make Avast act in a different way than before, they caused this type of potential problems.
When the potential problems only arise in a very little percentage of users, it is “handable”. This time, it seems not to go so well. Leaving the default setting to make Avast act as before would have make the transition gradual, while finding solutions for any potential problems.
I own a license for paid Sandboxie, and I force IE9 to open in Sandboxie, so I decided to uninstall avast!'s web shield. After I did the program change, I reset all avast! settings to factory default, then did a repair (just in case), then set all of the settings to my liking. Since I have uninstalled the web shield, I have not had a single yellow !
Hi guys, just wanted to add that since 2011/09/08 the IP address in question (here known as the fix #2) which is used by MS to test the availability of the Internet is no longer scanned by avast, no matter of your settings or your mom’s.
My understanding is that the detection of internet availability is unreliable and unpredictable. I am getting the yellow warning on a notebook without avast, zfactor was reporting these problems with previous versions where WebShield ALWAYS worked as if the checkbox “Scan only known browsers” was always checked - yet now it seems that turning it that way again is a magic fix.
For sure there are many factors which may fool this detection of internet availability, and it seems that having avast installed may be one of those, in same cases. We will try to find out more. The great thing is we are here talking just about the icon, and not about any connectivity problems or troubles with the Internet, just the icon is wrong; which is - from the programmer’s perspective - very relaxing to know.