Abort update

This problem was present in v3.xx and now v4.xx. If you run a manual update and the update servers are busy, pushing the 'Abort' button doesn't seem to do anything.

Just another minor annoyance....

 

Same here, eventually it stops but can take 5-10mins.

 

I disbelieve that ESET update servers are busy. They´re more loaded olny a few times a year, so it seems to be a problem with your connection..

 

I noticed this problem with v4.0.424 yesterday and when checking the firewall logs it showed that IDS was blocking connections to the update address. Then when trying to abort the update, nothing would happen. So, perhaps have a look in your log files for any entries telling you that IDS is blocking packets then resolve the IP address mention and that should tell you if IDS is working against ESET.

 

No problem with my connection and as you say and I agree, it is a rare occurence. Regardless of the cause, pushing the Abort button should in fact abort the update.

Overall, I'm happy with the latest build and appreciate the many 'under the hood' improvements. Just a minor niggle that hopefully ESET will resolve in a future build.

 

Its a problem with ESET software or/and their servers, please do not blame the end users it becomes stale very quickly.

 

I can confirm there are absolutely no problems with ESET's update servers.

 

Should be problem between enduser ---- ESET Server ---> means internet path. Not means user internet conection but some routers or switch witch are used for comunicating with ESET update server (and this is not ESET fault). Try tracert or pathping to update server when you have problem with update.

For me when I have problem with updating I'll wait few seconds.

Sory this is only words. If you say no problem than prove it (logs or other way). Please do not take this personally, I appreciate what you doing for us.

 

ESET never have any problems (according to them) its all the end users fault.

I do know how to get around updates stalling, I was simply reassuring the OP.

 

Have any of you guys noticed any IDS log entries that could relate to the update stalling bug?

 

I didn't say that. Actually there are 3-4 very large base updates for v2 users per year. In such case, updates may be delayed a bit as the servers are under heavy strain. The period during which updates may not succeed at the first attempt has recently been minimized significantly by adding a new highly efficient server farm with high speed connectivity.