eightiesrocker

I just had the same thing happen to me today. I manually updated my virus definitions and it solved the problem. Prior to this I rebooted my machine twice. For some reason the virus definitions never auto downloaded like normal. On the second boot, I noticed that eset wasn't checking for any new definitions automatically, That's when I initiated a manual check, then the error went away. I'll post if it does it again in the future.