NOD32 not updating

[Nomegusta]

Originally Posted by ctrl

^^ Yup when i try to update on my sp3 machine the database goes back to some v2967 or something. But updates nicely on my sp2 machine. I am using the trial version 3.0.669.0. Xp sp3 sucks.

What gives right!?

[ctrl]

^^ I am now quite happy after i shifted back to sp2, though i have sp3 installed on my desktop, its just for the sake of using up to date software and nothing else

[SmackyTheFrog]

Originally Posted by Nomegusta

What gives right!?

You're just hitting on different update servers, some of which are working properly and some which are not. It has nothing to do with the service pack level.

[ctrl]

Originally Posted by SmackyTheFrog

You're just hitting on different update servers, some of which are working properly and some which are not. It has nothing to do with the service pack level.

The problem is that the updates database goes back to 29xx in sp3 but not in sp2.

[Nomegusta]

Originally Posted by ctrl

The problem is that the updates database goes back to 29xx in sp3 but not in sp2.

So all in all, people who are with sp3 can't be properly protected with Nod32? That's phocked up.

[funkydude]

Originally Posted by Nomegusta

So all in all, people who are with sp3 can't be properly protected with Nod32? That's phocked up.

Read this.

Originally Posted by SmackyTheFrog

You're just hitting on different update servers, some of which are working properly and some which are not. It has nothing to do with the service pack level.

[Nomegusta]

Originally Posted by funkydude

Read this.

How come this server doesn't work? How do I get a server that will get me a proper update?

[SmackyTheFrog]

Originally Posted by Nomegusta

How come this server doesn't work? How do I get a server that will get me a proper update?

Hit update a few times. update.eset.com resolves to a whole bunch of addresses and it is luck of the draw if you get one that is screwing up or not.

[Nomegusta]

Originally Posted by SmackyTheFrog

Hit update a few times. update.eset.com resolves to a whole bunch of addresses and it is luck of the draw if you get one that is screwing up or not.

I've been trying updating, something like, 10 times a day for the past 5...

[Brummelchen]

Is there actual a server issue present?
i cant get any update for v4 (v2 works)
signatures stuck at em002_32 at 40% (per cent)
and it seems to happen on all servers...

[thomas_sz]

Here the same behaviour.
Last success on 6/30/2009, database 4202.
Actually out is 4205...

[Brummelchen]

4206 was loaded this minute - and works, no fail.
I was updating from 4202 up to 4204 and got stuck.
4205 came properly and latest 4206 too.
I dont have any clue what happend except guessing 4205
was synced on eset servers while i tried to load 4204.

[thomas_sz]

Still here on 4202.
Folder Updfiles\temp contains
- em000_32.dat (48,601 bytes)
- em002_32.dat (19,443,168 bytes)
Clearing update cache has no effect.

[Brummelchen]

Try deleting the whole content of \Updfiles

Its like the button after F5 -> Updates [Empty Cache]

[thomas_sz]

Thank you, Brummelchen,

but deleting the whole content of \Updfiles didn't help.

Only de-installing and re-installing after rebooting persuaded EAV to load new virus databases.

Why EAV doesn't record details of download errors? Solving this errors could be easier.

[Thankful]

Unable to update to virus signature 4220.

[BFG]

Hello,

It's a large update and a load balancing issue. It's by design and not an error.

BFG

[Thankful]

Originally Posted by BFG

Hello,

It's a large update and a load balancing issue. It's by design and not an error.

BFG

When can this paying customer expect to have protection against the latest threats? I've already been online an hour and a half today.

[BTIsaac]

Originally Posted by Thankful

When can this paying customer expect to have protection against the latest threats? I've already been online an hour and a half today.

I assume it will happen, when other paying customers, who have been on line before you and thus waited a lot more than you did, get it. Rule of thumb: first come, first served.

[Thankful]

Originally Posted by BTIsaac

I assume it will happen, when other paying customers, who have been on line before you and thus waited a lot more than you did, get it. Rule of thumb: first come, first served.

This is unsatisfactory.
If this is the case, Eset should buy more servers.

[aerialrave]

My situation was, I have to un install nod32 due to a problem in my game.
but when I install it again, it says that I'm up to date by the virus signature database was 3832 what happen here? When I un-install it, I delete the Eset registry in regedit.

[Marcos]

Originally Posted by BFG

It's a large update and a load balancing issue. It's by design and not an error.

Let me put this statement right. The thing is that due to big changes in the engine the updates have been temporarily paused and will be resumed in a couple of minutes.

[aerialrave]

^So, that was only temporary?

[Thankful]

Originally Posted by Marcos

Let me put this statement right. The thing is that due to big changes in the engine the updates have been temporarily paused and will be resumed in a couple of minutes.

Thank you for clarifying this. Your response is very much appreciated.

[aerialrave]

@Marcos
When it will be back sir?