Discussion in 'polls' started by HolyWind, Mar 18, 2008.
Which Version of NOD32 are you currently running on your system if applicable.
I wish I could choose more than one answer but...
v3 and v2 on different systems.
Slowly upgrading all to v3.
There is no point in using versions older than v2.7 .They can no longer protect the computer from today's threats
I`m sticking with 2.7...for a little while longer anyway.
Always the newest version. It's not about a vintage thing.
ess v3.0 on workstations & 2.7 on server 2k3
Just upgraded to Version 3. Seems okay at the moment apart from the missing tray icon occasionally
Running v3 on Vista SP1 and it's working great.
Version 2.7 most definitely !
Not sure what you mean that nod32 cannot protect from current threats?. Can you clarify please.
Also, I recently ran into a problem that tech support couldn't help me with. Was running 2.7. Have a 40gig drive, only half full. Scan took @ 25 minutes.
Bought 3.0. What a hog. Scan ran 8 hours & was only 68% done. Killed it. Kept trying...cleaned disk with ccleaner tried again.....same results. Unloaded it & got a refund. Went to Kaspersky. Not too happy with it either but scans only run @ 2 hours now......still too long for my taste.
Would love to return to nod32 if they will only admit a problem & fix it. Any comments out there?.
Thanks to all.
He means that versions older than 2.70.39 (2.5 and older) are too outdated to be useful.
Think the problem may be on your end but don't know what it is. When I ran a full system scan yesterday using v3, it completed in ~25 minutes (~570,000 files, ~110GB).
Willing to accept something specific to my machine but can't get by the fact that 2.7 ran in 25 min in the same machine & all I did was install 3.0 (3 times) & the scan times went to hours!! Made no other changes to the machine.
Is that true; 2.7 is 'no longer useful'?
Not 2.7 , just 2.5 . NOD32 2.70.3x is OK
Tried NodV3 then decided it didn't play well with a program.
Now using Nod2.7.
Separate names with a comma.