Update does not complete and starts again

Thanks Marcos,
Could you help me find ESS/EAV. I can't see it on the Eset site.

thanks

 

Remember this is BETA Software, even though it may be very stable:

https://www.wilderssecurity.com/showthread.php?t=186164

Cheers

 

Thanks Blackspear,
I see this is V3.0 beta.
I assume that I download "ESET NOD32 Antivirus RC1" from the page you pointed me at then remove V2.7 and install V3.0
thanks again

 

Correct.

AGAIN, the Warning that this is BETA Software.

Cheers

 

OK - done

Version 3 beta 3.0.414.0 loaded and working. Updated in a flash to version 2565 20071002 which looks current.

Ran a full scan over the drives - no problems. So far so good.

Thank you to the Moderators and Forum Members for their help and support through my trials.

I wonder if we will ever have the luxury of knowing what was going on.

cheers

 

Johnoz,
Please can you be more explicit regarding your configuration ?
1) Do you use a personal firewall ?
If yes : could you deactivate temporarly and then try again to update ?
please could you check configuration

2) Can you check windows XP firewall and do the same ?

3) Can you check your ADSL gateway (firewall rules ?)

Regards

 

Hi Phillipe,
I have now changed to Ver 3 beta and this seems to be working. Started this morning and updated no problems.

For the record, I use

Win XP SP2
ZoneAlarm firewall - free version
Netcomm NB3 ADSL modem - a simple single port modem.

I tried disabling ZoneAlarm ( but not removing) - no change
I did not try any changes with XP firewall.
I have made no changes to the modem's setup since installation and will need to get out the book to check out it's firewall rules.

Thank you for the help.

 

Ok, it seems that there's more going on, since I experienced exactly the same problem today.
Download of updates goes fine at a steady 100-120 KB/s till it hits 50%. Then it goes down to 2-10 KB/s till it reaches 69%, a point at which it stops, switches server and does it all over again. This has happened some 20 times in a row.

Manual updating does exactly the same.
I followed every step here and I still get stuck at 69%.

Only similar situation I can figure out between my system and that of Johnoz is that my ISP won't allow traces to my machine. I use an Anydata CDMA Radiolink modem (Wireless Radio ISP) and I have noticed that trace sites such as Visualware or Dslreports can't trace back to my machine, not even to my ISP. In fact the trace ends unexpectedy some 3-4 hops away from my ISP. I assume some manner of firewalling is in place or that the wireless nature of my ISP may have something to do with it...

BTW, I'm running Vista ultimate and no other security software other than windows firewall and windows defender.

 

Please try the following:

Check that the below files exist:

C Drive> Windows> Temp

C Drive> Documents and Settings> (User Name) XXXXXX> Local Settings> Temp

Do the "Temp and TMP" folders exist in "Environmental Variables" when you right click on My Computer as per the screenshots found in this link? https://www.wilderssecurity.com/showthread.php?p=764434#post764434

When you then navigate to the folders mentioned in "Environmental Variables" are they actually there?

Sometimes the only method is to delete and reinstall the Temp folders.

You can also try running this file http://www.nod32.it/getfile.php?tool=settmp it will set both the user and system TEMP/TMP variables to c:\windows\temp. Just make sure the folder exists.

With Vista, you can also try turning off UAC in the Vista Control Panel.



If after the above the issue remains, can you also try the BETA:

Remember this is BETA Software, even though it may be very stable:

https://www.wilderssecurity.com/showthread.php?t=186164

If this resolves it for you as well, then it points to an issue with v2.7

Cheers

 

Yes, I ried all that to no avail, but I managed to narrow down the probabilities. It defenitely has something to do with my ISP. Since I'm on a laptop, I tried updating from friend's houses and public access Internet places.
The conclusion I came to was that this very same laptop, has no problems whatsoever updating from "standard" ADSL ISPs, but fails to do so at 69% whenever my ISP is used. I tried this at 4 different friend's houses who use the same CDMA ISP as me and NOD failed at 69% at each of their houses.
However, on standard "per cable" ADSL ISPs, it had no problem updating.
I can't say that the problem could be related to the need of NOD update to have "a continuous flow of data", as an ESET person here stated, since I get a very continuous and fast data stream rated with a 96% QOS by Visualware.
The only strange thing about my ISP is (as I stated) that you can't do traces to our machines, so my wild guess would be that NOD 2.70.39 has difficulty updating on machines that can't be traced.
This may be an issue, but I don't complain too much, since I can manage to update at work or McDonalds... hehe