okay, just wanted to give a shot a again to the firewall, added components to AIS, including those I don’t normally use (behavior shield etc…), rebooted, and found that all these components remained unavailable (shields unreachable), i.e. present in the UI but unusable. The UI then froze while I was switching tabs. Sending dump files (for SVC and UI) to ftp and password to vlk.
Okay this said, I attempted a repair with the installer, rebooted, and it worked ;D >>> all is fine now
edit: just to add that at the opposite of what I stated previously, in other threads, my connectivity issues while resuming the system from sleep mode were not related to AIS firewall, but to a setting in my router (DOS attack protection, useless for a desktop). I just turned that thing off ;D
just adding that even after two reboots, Windows Action Center in Seven still doesn’t detect Avast firewall. It’s up and running so that’s no big deal…except I won’t be warned if it’s suddenly turned off. I don’t want to leave Windows firewall on and I’d rather turn off action center monitoring to avoid the constant pop up that Windows firewall is off.
nope, that’s been a frequent issue (in AIS) since Avast5 came out, and as said the repair option solved everything, which is new. There use to be no other choice but a full reinstall when adding components (especially the firewall), the issue is still there but the repair function works, so…
guys, how can I get Action Center detect AIS firewall again ??? I’ve uninstalled/reinstalled the firewall again, doesn’t change anything. I know I’ll be warned by Avast if the firewall was off but still, I’d rather Windows be aware and tell me too just in case Avast would fail to do so.
thanks Tech, this could have been the solution (your first link). I never had to stop WMI service before, but I did as you suggested, deleted the “repository” folder, rebooted, it got properly recreated but the result is worse then before ;D Now the AV and antispy aren’t recognized either (see screenshot). I’ll try a second reboot, and if that doesn’t work I’ll try the second solution (from your second link). I think the issue is from Avast but okay…I’ll post back here again in a few minutes.
yeah, the WMIdiag popped up as more or less expected an “unsupported OS version”…doesn’t matter. Yeah a new install would probably solve that. I wanted to avoid that but it doesn’t seem that I have any other choice if I want Avast to be detected again.
okay Avast has been re-installed, and Action center detects it again (AV, AS, FW). So yeah, the issue as I thought came from Avast. Must only happen when you modify a setup.
