This content has been marked as final. Show 2 replies
Some updates cause this to appear for some unknown reason. There has also been a similar ongoing bug with Security Center 8 and to a lesser extent with Security Center 9. Apparently 3 things were causing it. 2 have been fixed and the 3rd is proving difficult to pin down. We are told that the next version of Security Center should not have this problem.
We are also told that, in actual fact, protection is still active despite the warning.
Until then keep clicking the fix button whenever it happens.