Licensed version changed back to trial version

[klavier]

I have a 3-user license for NOD32 for 3 years starting August 5th 2006 but this morning one copy won't update and is giving the following message --

You have been using this trial version for 43 days after the 30-day evaluation period. Further updates will not be possible. Please uninstall the program, or purchase a full version of NOD32.

The context menu for scanning in Windows Explorer has also stopped working with a similar message.

NOD32 is running fine on one of the other PCs. The third PC is at another location so I'm unable to check it at the present.

Can anyone suggest what might be causing this and how to fix it?

[Blackspear]

Hi klavier, welcome to Wilders.

This has come about because you have the old Trial Version installed, please take the following steps:

Please download and save to your desktop a FRESH copy of Nod32 from HERE (http://www.nod32.com.au/nod32/download/commercial.html)

For help with entering your Username and Password please see HERE (http://www.wilderssecurity.com/showthread.php?p=833156#post833156)

Uninstall your current version of NOD32 through the Windows Control Panel> Add or Remove Programs.

REBOOT your Computer.

Remove the Eset Folder from C Drive> Program Files.

Install the FRESH copy of Nod32 that you downloaded above using “Typical Settings”.

There is a Nod32 Tutorial on how to install and setup Nod32 HERE (http://www.wilderssecurity.com/showthread.php?t=37509)

Cheers ;D

[klavier]

Thanks for the very quick reply.

The PC with the problem was the one on which I ran the trial version of NOD32. This was installed after June 2006 and was directly updated to the registered version by entering the Username and Password, which is supposed to work from what I've read elsewhere in the forum - in fact it's worked fine until now.

At least the other two PCs had fresh installs from a download of the registered version so I shouldn't have to do a reinstall on them.

Thankfully your extra settings are very well documented and fairly easy to apply.

[Marcos]

{QUOTE-> Thanks for the very quick reply.

The PC with the problem was the one on which I ran the trial version of NOD32. This was installed after June 2006 and was directly updated to the registered version by entering the Username and Password, which is supposed to work from what I've read elsewhere in the forum - in fact it's worked fine until now.
<-QUOTE}

If you didn't use a trial version 2.51.26 or newer which brough the new "Full version" button for upgrade to a full version, entering a username and password to the NOD32 update setup panel wouldn't have upgraded it to a full version.

[stimpee]

Ive had this problem with a couple of the machines here at work and they were not trial versions upgraded. The only version that was, was the trial i ran to check out the app before buying (which ive now uninstalled/reinstalled with the registered version download).

On a handful of the machines, it says the client is so many days over the trial period and counts down until the continue button is displayed. Then I go to the update section and click "Full Version" and it just disappears and changes back to the registered version without asking for a serial.

To reiterate, this was on a clean machine using the registered version (which required the serial and password to download).

The users however, never read the box and just click the "Close" which means that NOD32 doesnt load. It would be better if there was both a "Close" and a greyed out "Continue" then they would know to wait.

Anyway, any suggestions?

[Blackspear]

Hi stimpee, please follow the steps in post number 2 above.

Let us know how you go...

Cheers ;D

[stimpee]

Thanks, I will but until it happens again on someone elses computer I cant test it so it might be a while. However, its happened on 3 machines already in the past 2 weeks. I think we are using about 20 of our 50 licences already and I'm moving people over from Symantec bloatware so I'll have more machines to test on.

[Blackspear]

{QUOTE-> ...from Symantec... <-QUOTE}Make sure you use the Norton Removal tool (http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/2006031710323113?Open&src=&docid=2005033108162039&nsf=tsgeninfo.nsf&view=docid&dtype=&prod=&ver=&osv=&osv_lvl=&seg) before installing NOD32.

Cheers ;D

[Djito$]

Hi Blackspear,


I' m new in this Forum.
I have facing problems with my NOD32 Update and I search and find the instructions you sent. I follow them but the usarname AV-1234567 (whitout space) and pass ~Removed - Ron~ dosen't work. Is it possible to assist me?

Thanks in advance,

Djito$

[pykko]

{QUOTE-> Hi Blackspear,


I' m new in this Forum.
I have facing problems with my NOD32 Update and I search and find the instructions you sent. I follow them but the usarname AV-1234567 (whitout space) and pass ~Removed - Ron~ dosen't work. Is it possible to assist me?

Thanks in advance,

Djito$ <-QUOTE}
They seem not to work anymore. When did you buy the license?

[Blackspear]

{QUOTE-> Hi Blackspear,


I' m new in this Forum.
I have facing problems with my NOD32 Update and I search and find the instructions you sent. I follow them but the usarname AV-1234567 (whitout space) and pass ~Removed - Ron~ dosen't work. Is it possible to assist me?

Thanks in advance,

Djito$ <-QUOTE}Please send your actual license in a Private Message to me, and I will check it. The Username you are quoting (AV-1234567) is only an "example", it is NOT the Username that was provided to you by Eset.

Cheers ;D

[stimpee]

{QUOTE-> Make sure you use the Norton Removal tool (http://service1.symantec.com/SUPPORT/sharedtech.nsf/docid/2006031710323113?Open&src=&docid=2005033108162039&nsf=tsgeninfo.nsf&view=docid&dtype=&prod=&ver=&osv=&osv_lvl=&seg) before installing NOD32.

Cheers ;D <-QUOTE}Yeah, I already know about that. I don't even trust it so we generally just image the whole HD with a new OS with the NOD32 already registered on there.

One of the users here (unfortunately one thats not always in the office) has the problem of NOD32 I outlined above (Oct3rd) every time he starts his PC which is very annoying, and his machine was from a registered version (non-upgrade) and a fresh XP (without Norton every being there).

Its funny as his is the only PC this is happening to.

[Blackspear]

{QUOTE-> One of the users here (unfortunately one thats not always in the office) has the problem of NOD32 I outlined above (Oct3rd) every time he starts his PC which is very annoying, and his machine was from a registered version (non-upgrade) and a fresh XP (without Norton every being there).

Its funny as his is the only PC this is happening to. <-QUOTE}Does he use a Registry Cleaner?

Cheers ;D

[stimpee]

{QUOTE-> Does he use a Registry Cleaner?

Cheers ;D <-QUOTE}registry cleaner? no. why should he? its a freshly installed version of XP and NOD32 registered version.

[Blackspear]

{QUOTE-> registry cleaner? no. why should he? its a freshly installed version of XP and NOD32 registered version. <-QUOTE}No, however registry cleaners can cause this type of issue. Uninstalling and reinstalling should resolve this, did it?

Cheers ;D