Archive

Archive for the ‘NOD32 FAQ’ Category

How do I uninstall ESET Smart Security/ESET NOD32 Antivirus? (4.0)

February 17th, 2010 admin No comments

Due to corrupted installations or newer program releases, reinstalling your ESET security product is sometimes necessary.

Uninstall

Click Start โ†’ All Programs โ†’ ESET โ†’ Uninstall. After you uninstall, you will need to restart your computer.

Warning: Do not attempt to uninstall your ESET security product using the Windows Add or Remove Programs utility from the Control Panel.

After restarting, confirm that you can see hidden files and folders by clicking Start โ†’ Control Panel โ†’ Folder Options โ†’ View and select the Show hidden files and folders option.

Click Start โ†’ My Computer and then navigate to and delete the following folders:

C:\Program Files\ESET
C:\Documents and Settings\All Users\Application Data\ESET
C:\Documents and Settings\%USER%\Application Data\ESET

Windows Vista and Windows 7 Users must delete the following folders:

C:\Program Files\ESET
C:\Program Data\ESET

NOTE: The uninstaller may remove the above folders automatically. If you are unable to find the folders after selecting Show hidden files and folders, the removal is complete.

Categories: NOD32 FAQ Tags:

Why does the file scan not indicate the presence of malware on a NSS volume?

February 16th, 2010 admin No comments

When scanning files with ESET File Security for Linux the scan detects no malware on a mounted NSS volume, even if present. Upon finishing, the scanner displays a list of scanned objects. Are some of the scanned objects infected, however, all items on the list will appear as clean.

The reason for this is that Novell Storage Services (NSS) distort common unix security principles the scanner relies on, limiting its privileges. This can result in threats not being detected on NSS mounted volumes.

To fix this problem:

Open the configuration file (with root permissions) in a text editor.
user@machine:~$ sudo nano /etc/esets/esets.cfg
[sudo] password for user:

Find the [global] section

Find the line:

esets_user = “esets”

and replace it by:

esets_user = “root”

Save the configuration file and exit.

Restart the esets_daemon.

NOTE: It is important to restart the ESETS daemon after saving the changes for the new settings to apply.

Categories: NOD32 FAQ Tags:

Mozilla Firefox update error: Update XML file malformed (200)

December 30th, 2009 admin 77 comments

The Update XML file malformed (200) error message may occur after an attempt to update Mozilla Firefox. The error message may vary slightly depending on which version of Mozilla Firefox is installed. You must exclude the *.mozilla.org certificate so SSL protocol checking functionality will not interfere with the update process.

ย ย 

  1. Open the main program window by clicking the ESET icon next to the system clock or by clicking Start โ†’ All Programs โ†’ ESET โ†’ ESET Smart Security.
  2. Press the F5 button on your keyboard to open the Advanced Setup window.
  3. Navigate to Antivirus and antispyware โ†’ Protocol filtering โ†’ SSL in the advanced settings of your ESET product and click the Ask about non-visited sites (exclusions can be set) radiobutton. Click OK to confirm.
  4. Open Mozilla Firefox and in the Help menu select the Check for updates… option.
  5. A pop-up window will display informing you about the Firefox application trying to communicate via SSL. Click Exclude.
  6. This excludes the Mozilla Firefox certificate from being checked by your ESET product. To verify this setting navigate to Antivirus and antispyware โ†’ Protocol filtering โ†’ SSL โ†’ Certificates โ†’ Excluded certificates.
  7. After confirming the exclusion, navigate to Antivirus and Antispyware โ†’ Protocol filtering โ†’ SSL and revert the SSL filtering mode settings, i.e. select the option Always scan SSL protocol. Verify the option Apply created exceptions based on certificates is selected.
  8. Mozilla Firefox will be able to complete the update without interference after you finalize these changes.

Categories: NOD32 FAQ Tags: