Seems to be browser and site dependent. Firefox 48 shows issues in Yahoo mail Delete/Move/etc .js buttons are affected but Opera is not.
Some other sites not affected in Firefox.
Running Windows firewall and then re-visiting sites restores .js buttons. .js buttons work irregardless despite how they look whether windows firewall is running either way.
Also had issue with yesterdays microsoft security updates not downloading; error code: 0x800706d9 until windows firewall was started via services.msc
Pointing out here that above behavior is due to firewalls but what is notable is that Windows 10 firewall is not running at the time these artifacts were seen.
Advice elsewhere in the forum suggested Windows Firewall should be turned off (set in services to start Manual instead of Automatic) due to possible conflicts with Avast AIS firewall. How this issue was resolved was by
It was after turning Windows Firewall back on whilst still running Avast AIS firewall that the icon/.js button issues resolved. I’ve now set Windows Firewall to Automatic in services.msc. A Google search provided the answer as to what the error code thrown by Microsoft Update meant. It is related to their firewall not running.
Turning Windows Firewall back on resolved everything.
My question is: Is this a requirement in avast firewall that Windows Firewall to be running all the time alongside avast firewall or running AIS firewall as standalone is actually buggy in ways we will not see otherwise?
–I didn’t see issues until I stopped Windows Firewall.–
Well here’s the thing, when i open start menu, enter “firewall” and launch the GUI the first 2 lines state “being managed by supplier software” or something and “Windows Firewall is active”. Yet, it’s still happening.
One difference between bob3160 and I is that I am running avast firewall alongside windows firewall; bob3160 is running only windows firewall. Avast Free does not have a firewall.
Odd thing here is that one would expect firewall conflicts to occur when running both avast and windows together but that is not what is shown here. Rather, the opposite scenario seems to be in play here. Run both and everything seems to work as it should.
Stopping Wndows Firewall service alone should be sufficient to allow avast to step in and create rules for Windows Updates and .js icon buttons but that is not happening, as shown above.