Are Eset Update Servers Down?

[itman 1,659]

Received no Eset update at cold boot of PC this morning. When I then subsequently manually checked, received this:

Never had this happen before.

[SCR 195]

Just checked and I'm not seeing a problem.. I'm on regular updates.

Installed components:

Detection Engine: 18132 (20180929)
Rapid Response module: 12919 (20180929)
Update module: 1014 (20180123)
Antivirus and antispyware scanner module: 1542.1 (20180821)
Advanced heuristics module: 1189 (20180806)
Archive support module: 1277 (20180727)
Cleaner module: 1166 (20180911)
Anti-Stealth support module: 1141 (20180917)
Firewall module: 1380 (20180813)
ESET SysInspector module: 1273 (20180523)
Translation support module: 1706 (20180822)
HIPS support module: 1328 (20180917)
Internet protection module: 1334 (20180522)
Web content filter module: 1058 (20170406)
Advanced antispam module: 7774 (20180919)
Database module: 1103 (20180629)
Configuration module (33): 1706.2 (20180925)
LiveGrid communication module: 1047 (20180717)
Specialized cleaner module: 1012 (20160405)
Banking & payment protection module: 1138 (20180921)
Rootkit detection and cleaning module: 1019 (20170825)
Network protection module: 1676 (20180710)
Router vulnerability scanner module: 1052 (20180816)
Script scanner module: 1043 (20180820)
Connected Home Network module: 1021 (20180907)
Cryptographic protocol support module: 1028 (20180626)

[itman 1,659]

Just ran a manual update again and this time it completed successfully. Hopefully the problem resolved and future auto updates will work w/o issue.

[Marcos 5,074]

If you are able to reproduce the issue in the future, we'll need you to enable:
- advanced update engine logging
- advanced network protection logging
in the advanced setup -> Tools -> Diagnostics and run update. Next disable logging and gather logs with ELC.

[Skier 7]

I have just had another 'File corrupted' notification which occur quite frequently.  I clicked on 'Check for Updates' and after a couple of minutes got the messages shown in the image.

Any ideas?

[itman 1,659]

3 hours ago, Skier said:

I have just had another 'File corrupted' notification which occur quite frequently.  I clicked on 'Check for Updates' and after a couple of minutes got the messages shown in the image.

Any ideas?

Your issue is different.

You might want to refer to this thread that went on for months:  https://forum.eset.com/topic/15480-error-when-applying-differential-update/ . The OP finally conceded that it appears the issue was related to his ISP and/or his ISP issued router.

Bottom line - if Eset shows an invalid signature or certificate error on an update download, it is because the it was corrupted in transit.

Edited September 29, 2018 by itman

[autobotranger 1]

Hey guys. Seems like something similar is happening on my end, though I'm using Eset Nod32 Antivirus.

I ran a manual update in Eset and noticed that it took quite a few minutes for it to finish. Usually it only takes a few seconds. Being curious, after the update had finished, I clicked update again to see if it would act the same way this time. It kept hanging for a while and eventually came with an error in red text "Product was not updated. Transfer was interrupted" (translated from Danish). Screenshots attached:

As you can see the first update went through, even though it took several minutes.

 

Choosing to manually look for updates again resulted in this error after several minutes of hanging.

 

 

[Marcos 5,074]

Errors like "file is corrupted", "invalid signature", "connection interrupted", etc. are typically caused by proxy servers on the way.  In such case, follow my instructions posted above. The best course of action would be contacting your local customer care to ensure that the case is tracked properly.

[Purpleroses 21]

I don't know if anyone else is having this issue but virus radar say it is at 18134 and I'm sitting at 18133.  In order for me to get 18133 I had to restart my computer this afternoon.  Now it says it is up to date with 18133 and not updating to 18134.  Do I have anything to worry about?.  This just started happening today

[itman 1,659]

I received 18133 via auto update at 2 PM EST today. That was the last auto update and Eset just checked at 7 PM EST. So if 18134 is available, it is not being served up yet via auto updating.

Just checked manually and Eset served up 18134. So it appears there might be something going on in the update server backbone that might be affecting auto updating.

[Nightowl 202]

I am updated to 18135 over here , not having any problem.