Error occured while loading nod32m1.vxd

[halcyon]

Sorry to bring this up again, but I haven't heard from Eset people nor have I found an answer here.

I'm getting the following error when I start NOD32 On-Demand (Manual) Scanner:

Error Occurred while scanning operating memory. System memory cannot be scanned (the kernel service is not running or an error iccyred while loading nod32m1.vxd)

To sum up things at my end:

- Winxp sp2 32bit (all patches), stable (S-PI, prime95, memtest, s&m), 2GB RAM, A64
- NOD32 2.5 official (licensed, v. 2.50.16, beta versions gave the same error)
- no "nod32m1.vxd" file to be found on any of my drives
- bug report sent to Eset (no reply)
- re-install does not cure this (at least not for me)

If you do a quick search you'll notice that I'm not the only one having this problem.

Any solutions / answer from Eset?

Thanks!

[Firecat]

Maybe this thread is related....

http://www.wilderssecurity.com/showthread.php?t=80147

[TonyKlein]

Originally Posted by halcyon

- no "nod32m1.vxd" file to be found on any of my drives

If you're running Windows XP, you won't have it: Only Win 95/98/ME use VXDs (Virtual device drivers).

My guess is that the error message is the same for all operating systems.

And if this is indeed Win XP, try uninstalling, rebooting, and a fresh reinstall. That did it for most of us.

[halcyon]

Unfortunately re-install did not cure this for me.

[Blackspear]

With this issue can you please send an email to support@nod32.com and place a link to this thread. If you do not hear from Eset within 3 days (allows for weekends), please advise us here...

We would appreciate if you could keep us in the loop with your progress, as we all learn this way…

Cheers

[halcyon]

Email sent. Lets hope they can fix this. I'm a little worried about the "can't scan operating memory" part

Im also getting this problem. Also after I'd installed NOD, the icon for the On demand scanner was none existant, and the target of the executable was C:\Program Files\ESET\NOD32\nod32.log\nod32.exe

Removing the \nod32.log corrects the problem, but I still get the error scanning operating memory error..

Windows XP SP2
P4 3.2GHz
1.5Gb RAM
SATA HDD

[Marcos]

Would you please post the information about installed components here? (NOD32 COntrol Center - NOD32 System Tools - Information)

[halcyon]

I contacted Eset and got a reply. They basically wanted me to check if the kernel (nod32krn.exe) and gui (nod32kui) were running properly (they were).

However, I did _one more_ uninstall / reboot / re-install / reboot cycle.

Oddly enough, the problem is now cured.

This is quite odd imho, as my previous such re-install cycle did not cure the "memory cannot be scanned" problem.

So, for those of you still experiencing this problem, I recommned you do the whole clean uninstall/re-install (with reboots in-between of course) once again to see if it cures the problem for you.