Strange behaviour Nod32

Odos · May 09, 2009, 20:24:00

Hi all, just wondered if any of you Nod32 users have come across this before and have a solution. After installing an OS image file I start up the computer and the Nod icon is showing red and stating that the virus definition is out of date. Nothing unusual there as it's an older file in the image.

The strange behaviour starts if I click on update. The update window opens and the new definition file is fully downloaded after which the update application freezes without applying the update. It's not the entire Nod systems that freezes only the update part. Trying to use the update fuction again results in the update window opening and nothing happening. Anyway if I close the window and ignore it, it will complete at some time in the future. The quickest has been about three hours and the longest about three days spread over numerous restarts.

This happens in XP32bit, XP64bit and Vista32bit. Once it has updated this first time it works flawlessly until I again re-install an OS image. Anyone any ideas ?

Simon · May 09, 2009, 20:37:53

Not being a Nod user, this is just a guess, but I wonder if it's thinking you're trying to use the same licence on two different machines?

Odos · May 09, 2009, 20:47:46

Quote from: Simon on May 09, 2009, 20:37:53
Not being a Nod user, this is just a guess, but I wonder if it's thinking you're trying to use the same licence on two different machines?

Could Be

I suspected this at first but then decided against it as I would have expected Nod to use a similar type of validation to the one used by windows namely Hardware indexing, and all the obove systems are running on the same machine, plus after a while they all start working fine again.

Simon · May 09, 2009, 21:34:39

Maybe it just needs the one update check to re-validate? As I said, I'm only guessing, but it seems a reasonable explanation, in the absence of a better one.

Gary · May 09, 2009, 21:46:59

Quote from: Simon on May 09, 2009, 21:34:39
Maybe it just needs the one update check to re-validate? As I said, I'm only guessing, but it seems a reasonable explanation, in the absence of a better one.

The computer glitch fairy me thinks

Simon · May 09, 2009, 21:50:46

Who are you calling a fairy?!

Odos · May 09, 2009, 21:51:57

Quote from: Gary on May 09, 2009, 21:46:59
The computer glitch fairy me thinks

TBH this is my favourite explanation at the moment

The way I have my system set up is a little "strange" to say the least

Gary · May 09, 2009, 21:58:33

Quote from: Simon on May 09, 2009, 21:50:46
Who are you calling a fairy?!

Baz · May 10, 2009, 07:02:10

total guess but is the older file image an earlier version of NOD and the update definitions need the new version

Im on 3.0.667.0 at the moment

Gary · May 10, 2009, 07:30:23

Quote from: Baz on May 10, 2009, 07:02:10
total guess but is the older file image an earlier version of NOD and the update definitions need the new version

Im on 3.0.667.0 at the moment

Some people are still happily using Nod 2.5 Baz, I have had Nod glitches on updates before, nothing serious just now and then odd things, maybe for a second it thought it was installed on two machines

most odd but at least its working now. Sometimes computers act up and a reboot sorts it out, and we have no idea why, driver clash something in the boot order clashing hardware glitches or maybe, just maybe its mocking us

Noreen · May 10, 2009, 10:32:27

Tony, have you had a look here to see if anyone else has had this problem? http://www.wilderssecurity.com/forumdisplay.php?s=9a08aa89b0370020146a57eff497229a&f=88

Odos · May 10, 2009, 10:36:03

Quote from: Baz on May 10, 2009, 07:02:10
total guess but is the older file image an earlier version of NOD and the update definitions need the new version

Im on 3.0.667.0 at the moment

I'm using version 4.0.314.0. I never had any previous versions as I only purchased it in Feb this year.

Rik · May 10, 2009, 10:39:22

A very odd one, Tony. Well worth asking on Wilders, as Noreen suggests.

Odos · May 10, 2009, 10:40:00

Further to my above, anyone know how I can get hold of a previous version to see if that behaves any better ?

Will check out that link Noreen. Thanks

Rik · May 10, 2009, 10:42:11

I believe there's a link to the older versions on the d/l page at Eset, Tony.

Odos · May 10, 2009, 10:43:51

Quote from: Rik on May 10, 2009, 10:42:11
I believe there's a link to the older versions on the d/l page at Eset, Tony.

Cheers Rik will go check it out. A quck search for freezing from the link Noreen posted brings up quite a few threads so it's not as unusual as I thought

Odos · May 10, 2009, 11:16:13

Quote from: Rik on May 10, 2009, 10:42:11
I believe there's a link to the older versions on the d/l page at Eset, Tony.

You were correct, I is downloading as I type

Rik · May 10, 2009, 11:17:21

I thought I'd seen one.

Odos · May 10, 2009, 15:27:38

OK I've downgraded from version 4 to 3 on all my OS's and imaged them. I'll update the outcome if anyone is interested at a later date when I restore any of the images

Thanks to all

Rik · May 10, 2009, 15:35:00

We look forward to hearing how it goes, Tony.

Odos · May 13, 2009, 14:47:06

Just a quick update if anyone is interested. I've restored both the XP64 and XP32 images ( with version 3.2 of Nod ) today and both worked perfectly so it would seem that it's a flaw in version 4.

Rik · May 13, 2009, 14:50:03

Thanks for that, Tony. I've only got v4 on my NC10 netbook, which I don't image, so I should be safe.

Noreen · May 13, 2009, 17:20:10

Quote from: Odos on May 13, 2009, 14:47:06
Just a quick update if anyone is interested. I've restored both the XP64 and XP32 images ( with version 3.2 of Nod ) today and both worked perfectly so it would seem that it's a flaw in version 4.

Glad to hear it. I'm still with NOD32 v3.0.684 and I've no intention of changing yet.

Odos · May 13, 2009, 17:59:44

Another update if anyones thinking of getting Windows 7. I downloaded the RC 64bit yesterday. Installed today. Tried to put Nod v.3.2 on but it complained something cronic saying that it's not compatable

so in the end I had to install v.4

Rik · May 13, 2009, 18:01:54

More for the database, thanks Tony.