This is an amalgam of other people's fixes for common NOD32 problems. Please try these (in order) before asking for further help. Also see the NOTES section at the bottom. I will update this as required. With thanks to Blackspear, xTiNcTion and others for their suggestions etc. If you are having problems with NOD: Not being able to get rid of an infection Doing odd things Or want help in setting it up for maximum protection ...then follow the following procedure. 1. If you have NOD already installed then uninstall it, remove the registry keys (HKLM/Software/ESET), reboot and delete the entire ESET directory under 'Program Files' 2. Download NOD32 installer (from Eset website). 3. De-compress the installer. (In Windows XP, right click on NOD32 installer and choose "Extract files..." - put the content on a new folder. You could use any other unzip tool, like 7-zip or winzip). 4. In that folder, unzip nod32config_en.zip (2.2 kb) containing: config.xml and install.bat These files are created and hosted by Computalleres de Nicaragua - a NOD32 Reseller. 5. Double-click on install.bat to begin the installation process... wait for the installer to finish. System will restart automatically. 6. Enter your username and password for NOD and update it. 7. Download and install SuperAntispyware, Lavasoft's Adaware and (preferably) Microsoft's Windows Defender (legitimate copy of XP required. Also requires Validation.) 8. Update all antispyware programs fully. 9. Turn off system restore. 10. Download and run Winsock Repair. You will then need to restart your computer in safe mode. 11. Run SuperAntispyware, Adaware and Windows Defender in full scan mode and let them remove anything it finds. 12. In Windows Defender, click on the Tools icon, then Spynet Community and choose 'Join Community' option. You will then be warned in the future if any programs try to add themselves to the startup groups, change IE setting etc 13. Run NOD32 and let it remove anything it finds. (NOD Control Centre will not run in safe mode. User 'Start/Programs/ESET/NOD32) 14. Restart computer normally. 15. Turn on system restore. 16. Do a Windows Update and install all updates and security patches. Ensure you have a firewall turned on. 17. Hopefully, your PC will now be a much better, more stable beast! NOTES Error scanning MBR of disks? More than likely you have slots for CF cards etc on your pc. Colour coding during scan - Blue: Files locked by Windows (clean), Red: Infected file, not yet dealt with, Brown: Infected file deleted/cleaned If you have Threatsense enabled (already done if you've followed the above setup instructions) then any unknown samples will be automatically submitted to ESET for further investigation or you can do this manually be emailing it to samples at eset.com In a Windows server enviroment IMON should be disabled on the server only.