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