Hello,
Today having attempted to run a quick scan and full system scan multiple times I found nothing happening. I have previously experienced this behaviour (although for other reasons I ended up formatting then anyway and so never got to the bottom of it). Since nothing was happening, although Norton still displayed as 'secure' I attempted to reboot, which then resulted in an error message pop up, Norton totally vanished and the 'force shut down' option popped up blocking the error message. Unfortunately the PC shut down to fast for me to read the message so I have no idea what it said.
Norton appears to be functioning normally at the moment, but my main concern is what might have caused this behaviour and also if it is possible Norton (particularly the firewall) was not functioning prior to my attempt to run the scan.
To try and determine whether Norton was working prior to my attempt at a scan, I had a look through the history.
Norton's security history shows 'No User Logged in' for 13:02, which normally is the reboot/shutdown time, though given Norton vanished prior to the shutdown I have no idea what that would mean.
My last definite action before all this was a scan at 11:59. Between 11:59 and 13:01 there a whole range of entries, including:
1) programs entering/exit full screen mode
2) programs accessing the internet
3) rule default block epmap (last one is at 12:39
4) Using antiphising definitions version 20111026.006 (at 13:01 only).
Now to my rather unknowing mind that seems to suggest Norton (and it's firewall) was working right up until 13:02, and so I shouldn't need to worry about anything nasty sneaking in during that time? I'm primarily concerned with figuring out if it's possible something could have gotten in (IF the firewall was not working) so I can just get the pain of formatting over with now rather than leave it and find there is something later.
So in summary:
1) What could have caused the odd non-scanning behaviour/error on shutdown/norton to vanish
2) Should I be concerned/was Norton/Firewall working up until the error popped up based on the history logs.
Thanks.