kernel32 error

Hi there, I have had nod32 for about 4 months with no issues. But suddenly at the last scan (and subsequent scans) an error message rears its ugly head 3 minutes into the scan. "nod32 has caused an error in kernel32, nod32 will now close".
I am running windows ME and have zone alarm. The only thing thats changed from when it ran perfectly are windows updates.
Has any one any ideas on how i can get rid of this annoying error message and what the hell is going on?
bc

 

Hi billycasper, welcome to Wilders.

Please download a FRESH copy of Nod32 from www.nod32.com

Uninstall your current version.

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”.

Let us know how you go…

Cheers

 

Thanks for the reply blackspear but can i ask what is probably a really stupid question. I have bought nod32 and if i try to download it again wont it try and charge me again?
andrew

 

Hi Andrew, no, they wont charge you again, simply use your Username and Password when requested upon downloading.

Cheers

 

Ok so ive downloaded nod32 again. unistalled and cleared the existing nod and reinstalled the new version.
It hasn't worked
I noted the scan logs and it errors at this point or just after
C:\_RESTORE\ARCHIVE\FS96.CAB »CAB »A0012326.CPY »GZ »A0012326.CPY - error - unknown compression method
When it did scan this message still appeared but nod32 carried on and no kernel32 errors appeared.
any ideas?

 

You were trying to fix the following error:

and you say that it now doesn’t happen any more:

So I’m a little confused, as it appears that your Nod32 closing issue has been resolved.

You can remove this from your scan by turning off “System Restore” rebooting your computer, and then turning “System Restore” back on.

Let us know how you go…

Cheers

 

Sorry about the confusion blackspear let me try and make it clearer.
I have been using nod32 without fault until recently. When i looked at the log files for the previous scans it appears that the scan found "an unknown compression method" at the point stated but carried on with the scan.
Then i started to get the kernel error and checked the log files to see that the scan erored at the "an unknown compression method" point.
For some reason it wont get past this point where previously it had.
I still have the kernel error

I will try the system restore thing and see if it works

 

I assume that emptying recycle bin will remove the archive file from your disk so subsequent scans should go fine.

 

Ok, it worked......I turned off system restore then did a scan, which worked. I then turned system restore back on and that worked as well.
Thank you for your help. 1 final question..?
Why?

 

Because.

 

Good to see, and thanks for reporting back.

You’re welcome.

Not sure, other than the file was stuck in System Restore, and the type of file was making Nod32 cranky, so turning off System Restore removed the file.

Cheers