When I updated from 2014 to 2016 and again here yeasterday, when I updated to 2018, the system told me that Avast was disabled and it was first after a restart and manual enabling that the Avast was back.
It happened both on my desktop with Win 8.1 and on this laptop with Win 8.1, so does anyone have an explanation
( and by the system I mean, first I saw a little red icon meaning that there was something to look at beside of the clock, when I opened the controlpanel, Windows firewall was back on and so was Windows defender, Avast was not detected)
I am on AVast premier
if this is a known bug in the windows security center why is it just now showing up?
right after THIS update and none of the previous versions?
sounds like someone goofed some coding up with this update to me
…
the only thing that has changed is avast, not the windows security center :o/
its easy to blame something else when you don’t really know what the real problem is
It is very random … I myself have never experienced. But if you look around the board you will find many instances of this . It appears to have been around since Vista and Avast 5
yeah, odly enough after checking security services etc and rebooting the computer a couple times it now is reporting it correctly.
Very strange indeed
but this never did happen before till this update… which made me suspicious
I can ensure you it is not avast that caused it.
I’ve seen it happen with all kinds of av’s and firewalls, even MS own software.
As essexboy said, the bug is real old.
It even already was in XP (before Vista).
Anyway, good to hear it is solved.