Problems with Update/Upgrade from older Version..

Fresh? Read the thread and then you have the answer..!

Fresh download is only a temporary solution, if Eset don't correct this update problem! Or is there a new NOD32 Version available-->NO! (only beta)

bye

iNsuRRecTiON

 

I can assure you no emails that actually come to Eset remain unanswered. There are also phone contacts so in case you haven't received a response you can call Eset to find out if they actually got your email.

BTW, the beta seems to be much more stable than the release version 2.12.3

 

Hi iNsuRRecTioN,

I read the entire thread and cannot understand your point. Over 3 months have passed and you still didn't use the very simple solution provided to you twice If I had a problem on this scale (one component not updating), I'd wait a week if there's an evident solution, if there isn't I'd say it was a trick of my box and get that d**n fresh copy
Especially that there's a new, very stable version out (it fixed the single bug I encountered in NOD32), and it might as well fix your issue!

Regards,
SA

 

why one client should use this beta?!

Betas are only for testing and not for normal systems..

bye

iNsuRRecTiON

 

OMG....
I am too scared to post I have 2.12.3 with no problems.....not going to the "beta" route as yet (too many other things to do..spring is here)
Am I missing something here? or is the advice given and provided not a viable alternative?
I am lost (as usual)
Cheers

 

No you're not

Yes indeed

No you're not

 

Yeah, you're absolutely right. However some companies would have released this as 3.0 final, not as 2.5 beta. It's extremely stable and contains what you need. And anytime you wish you can revert to 2.12.3. So no risk factor, and benefits are certain: why not to use it?

 

...lol...