Quote:
Originally Posted by psicodude
I don't use Symantec, but your version number for Defender almost matches mine. I have 4.11.15063.0. Last update was 1:03 pm today. I've seen these policies get messed up in the past when lots of updates are happening, like they would have today. You may actually have a newer AV version than their system understands and it throws this error. Just a guess though, sorry.
|
It's just strange because I've been seeing this issue based off of whatever update they made on their end over the weekend.
So I've consistently been seeing this issue for the last 4 days and they seem unable to help or isolate the problem and I'm going at my wits end here.
Literally they're only suggestion is working on another laptop, as if that is a viable alternative (as if I have multiple laptops lying around for work purposes like this).