Please advise if/why to change versions 3 to 4

I haven't kept up with all the changes.
I'm using v3.0.672.0, update 4549 as of today.
What are the advantages of scrapping this version and going to v4, if any?
(on one, very small, comp 2.7 is still chugging along happily)
I've dealt with the local host proxy in firewalls, so that's not really an issue. I just want few words why risk updating, please amd thanks in advance.

I suppose the licences are valid whatever version I use, forever (i.e. till expiration date), right?

Running on XP sp3 and on Windows2000

 

Hello,

A press release announcing ESET NOD32 Antivirus V4 can be found here on ESET's web site discusses the major changes between V4 and previous releases.

Regards,

Aryeh Goretsky

 

I changed because I don't like Fibonacci or Prime Numbered versions.

 

I still have V3 on two PC because V4 was causing hangs/freezing, and I don't expect, or want to troubleshoot a piece of software I paid for.

 

Thank you. That was helpful and the writeup convinced me to go for it.
It wasn't easy to find the correct version, not old, and not Eset security suite.
I couldn't figure out whether the Download button goes with the entries above or below the button. Almost gave up and switched to the Avira product.
But I did get v4 of AV, licence was accepted, it installed and it's very nice.

Few questions. I see in the firewall log strange attempted connections occuring during the update:
1. Why would Windows Explorer want to connect to 208.111.162.28:80 during this update? also x.x.x.31, x.x.x.42.
2. Why would svchost want to connect to localhost port 30606 (NOD proxy) during this update?
3. Why would system safety monitor want to connect to localhost 30606 (NOD proxy port) during this update? I understand msiexec.exe, but SSM?!

 

Hello,

I believe 208.111.162.28 is a cache server used by Microsoft for either Windows Update or for verifying digital signatures.

Version 3 clients use local proxying to intercept network traffic. In version 4, the Windows Filtering Platform is used instead, if the operating system supports it.

Regards,

Aryeh Goretsky

 

OMG, I installed on XP-SP3
That Windows filtering platform is for Vista.
Should I revert to v3?
Should I shut off some things like Web filtering? I do see port 30606 is in use, so now I'm confused, and will appreciate some explanation.

 

NOD32 4.0 comes with 2 web filtering drivers.If you install on XP then the other NON-WFP driver will be loaded.Your fine with what you have.

 

Well, I had to revert to v3.
V4 or the most recent Windows updates caused me problems. Particularily with web watch related things. I had to shut off Opera from the list of browsers - Opera does its own watch. It hasn't been a problem in v3 at all, ever, but definitely is in v4. Less trouble once I did that, but still ...
I got several BSOD, each wrote over 900gig or meg of a dump file, each blaming TCPIP.sys - and did you just install a new driver (yup, NOD v4) or hardware (nope). I haven't had BSOD since ages ago.

My subscription expires in less than two months. I can renew and use v3 or even 2.7 or not renew and use Antivir or renew and use v4+ which might get fixed or might not for XP. I suspect Windows7 drivers are doing me in. Yikes.

 

Hello,

By "web watch related things" do you mean NTP (time clock synchronization) or watching streaming videos?

It is possible there is a conflict with another device drive on your system, which lead to the crash within the TCPIP.SYS driver. ESET NOD32 Antivirus V3 and V4 both install device drivers as filters to inspect data streams (web traffic, file I/O, et cetera) for threats.

You can download and use any version of ESET NOD32 Antivirus (v2.7, v3.0, v4.0) provided on ESET's web site as long as your license is valid.

Regards,

Aryeh Goretsky

 

No, I mean "Web access protection" the thing in Advanced tree view where browsers and ports are listed. I don't do streaming video. I do synch time but that has never been an issue.

I suspect conflict as well, and don't have the skills nor time to debug - the severe problems were v4 with Opera.

V3 has worked fine all along, so I'll just keep using it. Thanks for your reply.