What happened to update 1.1726?

After a day where i had 6 error connections one update failed (server conection failure) Nod updated to 1.1727 from 1.1725! here did 1.1726 go

 

It would be included in 1.1727 when uploaded to your computer.

 

But if you look on the eset site there is no 1.1726

 

This has happened before. Here's another thread on missing updates but it offers few answers. https://www.wilderssecurity.com/showthread.php?t=123538&highlight=missing update

 

I also, find the update feature of Nod32 to be lacking in consistency and function. It's been a very frustrating and annoying experience for me, to say the least. I just cannot trust it anymore to keep me updated properly and protected with current signatures. I have decided to return to Dr.WEB Anti-Virus for my protection, it gives me peace of mind...

 

of course you're welcome to your opinion, but as long as updates continue to arrive, I don't feel concerned about a "lack of function"... ymmv of course.

 

Update 1.1726 was actually issued, just the info about it didn't appear on the website. It will be added manually to the SQL database.

 

Well it escaped my pc which runs 24/7 there were so many errors yesterday with servers listed in my Nod i find it alarming i can miss an update, all functions within nod are as they should be but server side issues seem to be more problematic these days, i rarely have a clean sheet of updates and always see errors with connections of as yesteday failures as well, and to skip a whole update is i find quite disturbing when my pc is connected to the net (via ADSL firewall router). I know it may seem like just one update therefore not much to moan about but it should not happen at all should it?

 

Yep, lots of server not found messages in my logs as well. Hope ESET can solve it quickly...

 

Same here, the frequency of this problem needs attention, I know people say eset are aware, working on etc but it just continues having sporadic fits like yesterday, now say that update I missed had a signature for a new and nasty infection we would hope AH would get the malware but maybe not, and during the time between me missing it and the next update I may have been vunerable. As you say I hope they sort this out, its gotten alot worse over the last year

 

When can we expect this to be done?

 

I was told by US support that the update signatures were rolled into the 1.1730 update on the web site.

 

On the topic of updates failing. I had major issues with auto picking a rotten server, failing, and not trying any other server. I then tested a few of the other servers manually and they were all very responsive. Almost seemed like everyone was hammering that one server.

It's either a bug or very very poor design that it's unable to log a failure on one server then try another one.

Either way though, I've gone from 80% failed updates to 100% success after manually selecting a different server. As long as that one's stable so I don't have to manually rotate the selected server I'm happy.

 

You can always test all servers at www.nod32sse.com -> Server status

You'll be able to see the current status of a server and the month status .
There you'll see that servers u8.eset.com and 82.165.250.33 are not always online
~~~