NOD32 v4

Weird. On the Wilder Security forums there doesn't appear to be an official thread announcing v4 is out, apart from a v4 beta thread. Yet in user-created threads they are confirming that v4 is out. :confused::p

Anyone seen any changelists?
 
Last edited:
Ah looks like quite a few are having problems then. Mine said 'at risk' and was red in the status tab / system tray and wouldn't update properly either.

so it's not just me then! I got a BSOD and the upon reboot nod32 v3 wouldn't start the antivirus and said I was not protected.

Probably a duff definition update again.
 
well v4 should sort it? clean install?

yup, done a clean install, but now v4 will not update the definitions, reckons that the ones from feb 6th are the most up to date. :confused:

I've put in a support ticket, but by the length of time it's taken then to respond (12 hours and counting) I would say they are having some problems.
 
v4 won't install. It gets to the "compiling data files" part of the installation and then says there's been an error with the installation. Sometimes it says that the PC hasn't been restarted since a program uninstall. Complete rubbish.

Managed to install v3 but its now on an old virus signature database (3553).
 
Last edited:
so it's not just me then! I got a BSOD and the upon reboot nod32 v3 wouldn't start the antivirus and said I was not protected.

Probably a duff definition update again.

I had the same thing earlier too, running the update manually from the Nod32 control panel fixed that
 
...a blue screen this morning... and it was the only program not functioning properly on a restart.

This happened to me earlier, and I only just noticed the icon was red now (I have it perma-hidden). In the status window it says:

"Virus scanner initialisation failed. Most of the NOD32 modules will not function properly".

That's quite dodgy since I have been flirting with files of questionable integrity :p Manual update did not fix the problem for me :(

I'm downloading v4 at the mo (albeit ridiculously slowly). Will let you know how it goes!

Cheers,

Suman
 
Apparently it's widespread and to do with the transition from v3 to v4, they've now disabled the definition update servers.

Bit peeved at how botched this has been to be honest, I had to waste 30 minutes I didn't have to spare today uninstalling, rebooting and reinstalling when I needn't have bothered. This isn't the first time ESET have dropped the ball, they recently mucked up another definition update that caused no end of problems.

More here.

And a KB here
 
Last edited:
althought compared to kaspersky, nod32 seems expensive, they know how to look after customers, a 'nod32' licence covers you from 2.7 to 4 :)

imo they should take a leaf out of kaspersky's book and offer the home version for say £4.99 a year
 
Installed fine on Vista Ultimate x64 here Marc... you have Admin rights I take it?

Update worked fine also, and all seems hunky dory. Will run a quick scan now to make sure I haven't picked up eAIDS during my unprotected escapades :p
 
Installed fine on Vista Ultimate x64 here Marc... you have Admin rights I take it?

Update worked fine also, and all seems hunky dory. Will run a quick scan now to make sure I haven't picked up eAIDS during my unprotected escapades :p
Yes. Just tried again and nothing doing. :(

Just reinstalled v3 and it has updated to 3901 successfully. So back where I was before I tried v4. I've raised a ticket with Eset support so I'll see what they have to say about my v4 installation problem.
 
Last edited:
Keep getting an annoying issue where I can't bring up the control centre :confused:

Both double clicking and right clicking on the NOD32 icon does nothing!! Icon is still green though, so hopefully it is active...
 
Keep getting an annoying issue where I can't bring up the control centre :confused:

Both double clicking and right clicking on the NOD32 icon does nothing!! Icon is still green though, so hopefully it is active...

Yup i've had that plenty times with v3 on both vista x32/x64 and XP32. Either click the icon in the proggy files start menu of NOD32 or task manager kill the app and then restart it via start menu/ proggy files/eset/nod32, should work in task bar after that. Weird bug :(
 
Last edited:
It's so annoying! I can get to the GUI from egui.exe in the program directory though. Did you ever manage to solve the problem Montegue? Should submit a ticket to ESET I suppose...
 
Back
Top Bottom