XP wont Shut Down

Just moved to XP on a new machine. After installing NOD the machine will not shutdown. States IMON is running. I wait for it to close IMON but I get some memory error I believe. I even killed NOD and machine wouldt shut down for about 10 mins. It was in a loop where it kept on waiting for IMON to finish. I have done a search but can only find slow shutdown and not a 'fails to shutdown'

Thanks in advance

 

Are you running the latest? I also had a similar problem with unistalling NOD32 that it would hang the machine, but they fixed that.

 

Im running latest...and its not a shutdown time problem, it wont shutdown at all, goes into a contionuous loop of xp trying to close IMON.

 

Hi Huwge, can you please download a FRESH copy of the Nod32 BETA from www.nod32.com

Uninstall your current version.

Remove the Eset Folder from C Drive> Program Files.

Install the FRESH copy of Nod32 that you downloaded above.

Let us know how you go…

Cheers

 

Beta the only way to go ?

 

In this instance I would say yes, basically it is a final release.

Cheers

 

Yes for now unless you want purchase NOD32 V2?

It runs great as it is!!

Cheers

 

Hmm, is there some confusion?. I have NOD version 2 fully paid up.

 

No confusion here, try what I suggested, make sure you remove the Eset folder and see how you go with the BETA.

Cheers

 

Okay, I've downloaded beta and run it. I have a lot of locked files, not just the usual four...some being

NTuser.dat
NTuser.dat.log
Mousepointmanagerremotedatabase
system32/config

I will try and shutdown now and see if works but can any shed light on the locked files please?. At the end of the log it only shows 4 locked but I can count many more ?

 

As a general rule, [4] locked files are simply "swap" files and as such can not be infected, the general advice is to ignore these locked warnings.

Cheers

 

Well, shutdown ok there, but I see that a new beta out according to Ron

Any recommended settings?. I tried to stay with Blackspears stickie but seems more options now. Soory bout all the questions. Just upgraded to XP and still getting the machine set up to my liking

 

Just go through each module and each of the dropdown boxes that have file types and settings, and adjust each, it is fairly similar to what I have in the sticky thread, and I'll update that thread when the final release comes out.

Good to see your problem has gone away...

Cheers

 

Sorry did not want to confuse you What I wanted to say was go back and install V2.12.3 to see if that works!! But I see that you got the problem solved with the Beta which is great!!

Cheers,

 

Most of the files you have listed (NTuser.dat, NTuser.dat.log, system32\config\...) are related to the Windows registry. Since they are in active use by Windows, NOD32 is not able to scan them. This is normal for these files.

The "[4] File cannot be open" message at the bottom does not mean that 4 files cannot be open. [4] is used as an asterisk/footnote, like when are reading a book. *4

I'm not sure if that explanation made any sense.

 

Thanks Alglove, been running NOD a while and always thought 4 meant 4 heh, learn someting new every day

 

Seems I spoke too soon. Imon gets the window...not responding closing down and goes into a continual loop....does this mean the end of my love affair with NOD ?

 

It's time to send an email to support@nod32.com and place a link back to this thread.

Let us know how you go...

Cheers

 

Well.....it seems I may have sorted it. I did a search and found some people had the same problem as myself which was cured by removing Windowsblinds. This a new machine which had it preinstalled. I have removed it and shutdown twice with no problems.

On another note I see that beta is going to a proper release soon. Will I have to download again or will it just upgrade and will I have to pay again?

Thanks in advance

 

Good to see, and thanks for keeping us in the loop, it helps us all to learn...

Cheers