IE doesn't browse out to internet/intranet. NOD32 with update date of 1/1/1601

We have been getting random IE not being able to browse out to the internet/intranet for the last few months. You can ping the external site, but not able to browse to it in IE/Firefox..etc. We recently founded that when this occurs NOD32's last update date is x/x/1601 or another date going back to the year 1601.

When this occurs, we will not be able to disable eset nor uninstall it.

If we reboot these client machines, they are able to get back to internet browsing. This occurs randomly and I have not found any root cause.

Running ESET ver 4.2.35.0

Anybody run into this or have info as to the cause?

 

Hello,

Just to verify, you are stating that the calendar year on the computers is set to 1601 and not 2011?

The latest version of ESET NOD32 Antivirus is 4.2.71, which is a newer build by ~35 builds. Does installing that make any difference?

Regards,

Aryeh Goretsky

 

See image provided by OP in another thread.

 

Could somebody with the year 1601 listed in the last update attempt date export the HKEY_LOCAL_MACHINE\SOFTWARE\ESET\ESET Security key, upload it to a private ftp server (the export will contain the username/password) and pm me the link?

 

Sure, I'll PM you with reg key once I get a client that runs into this again. It's pretty random at the moment and I haven't turn off auto scan after successful update on all clients...so we should see it again soon.

 

Marcos,

It happen again today for a user, this time around it's the year 1621. I will PM you the sftp access to the registry key that you are requesting.

User is on def 5908.

 

Hello,

I think I saw this exact same glitch once (the year 16xx, not able to browse internet) on my sister's computer with ESET NOD32 Antivirus 4.2.64.12 on Windows XP SP3. As far as I know, it has not occured again. I've never had it on my computer though.

Regards,

Mark

 

Mark,

it's pretty random...

On machines where we turned off scheduled task to scan after each successful definition update...we have not been getting this so far. It's affecting machines where there is a schedule task to scan after each successful def update.

 

Hi Cesspool,

I already had this problem. I solved uninstalling EAV (through this KB), then installing it again.

Regards,
Rafael Guedes

 

Hi Rafael,

It's not a matter of uninstall/reinstalling(because problem will persist). Rebooting will resolve the problem temporary until it occurs again the next time. Just trying to determine if it's a bug or the root cause.

Cesspool

 

Still persist randomly in our corporate environment with recent upgrade to NOD32 4.2.71.2

 

I'm seeing this behavior in my environment too. It seems to have gotten more noticeable recently. We're on 4.2.64. I just read this thread - I'll keep an eye out for strange definition dates.

 

We just upgraded as well and have had a bad problem with this as well. Reboots seem to be the easier temp fix. I need to check if the dates are changing, that's very odd