Posted 18 July 2011 - 02:53 AM
Well a few days ago, I downloaded the recent Windows Updates, and everything seemed to be normal.
The next day however, I returned to the computer after a few hours away, and the Internet was not working. I switched the modem on and off and this did not help, but it was working perfectly fine an hour before. I decided to check Nod32 to see if it found something, or there was sort of error, and as soon as I opened it from the system tray, an error popped up saying Nod32 GUI encountered an error and needs to be shut down. Sorry for the inconvenience.
I thought this is strange, and tried reopening it from the start menu, but it said cannot connect to Kernel.
I restarted the computer, and Nod32 loaded as normal. I checked the internet, and this time it was up and running perfectly. Then in the system tray, a Windows red balloon indicated that no virus protection could be found, even though Nod32 was up and running and when opened, anti virus and anti spyware was ticked. Scanning could be accessed as well. I looked at the Windows Security Centre, and the 'virus protection' was 'off' even though it obviously wasn't.
I then decided to reboot the computer into safe mode, and scanned with Hitman Pro which found nothing. I then looked at Eset's site for information and it said it could be a dysfunction in the antivirus' interface, or a Backdoor Bot. I thought the Bot was unlikely as nothing suspicious had been going on, and I had done a lot of scans with eset, malwarebytes and HitmanPro the day before. I used Eset's tool for the Bot just in case, but it does not say whether it found something or not, the command prompt box just appears and then disappears. I then ran a full scan with Malwarebytes and nothing was found.
I rebooted the computer a few hours later, and the little balloon did not appear again, nor did any errors and the internet was fine. I am just wondering, what could have caused this? Could it have been Windows Updates, and it somehow didn't recognize Eset Nod32 for some reason, or was it a malfunction in Nod32's system?
Thanks- sorry for the long essay like information