Marcos

It is important to know whether the files infected with the virus were detected or not, whether cleaning failed or succeeded but files became unusable after the cleaning. A malware infection shouldn't cause the scanner to stop scanning, perhaps it was scanning a large file and after a few minutes it would continue scanning other files.

Do you use the firewall in automatic mode with exceptions? Please enable logging of blocked connections in the IDS setup, reproduce the issue and then copy and paste here the recent ESET firewall log records.

Basically all relevant samples are processed quickly. We're seeing a lot of "rubbish" being sent to the viruslab so without checking your samples it's impossible to tell if that's the reason why your samples haven't been processed yet. Feel free to PM me your email address so that I can check out your samples.

Please create a SysInspector log and submit it to ESET along with a link to this thread as per the instructions here.

If you run an on-demand scan, are you sure there are no logs created if you select "Computer scan" in the Log files section? The best would be if you could save the entire log to a text file and upload it here so that we know what threat was actually detected, the location it was detected in as well as the action that was taken.

Importing the root certificate into Opera 15 is not currently supported as they've made substantial changes to the program. You'd need to export the root certificate from v7 and import it to Opera manually.

Exclusions are applied only to files on a disk. Please post the appropriate threat log record here.

You can only disable particular protection modules or uninstall ESS completely.

If disabling Advanved memory scanner makes a difference, this issue should be fixed in the next v7 beta build.

Why the path ends with a backslash and slash? Use either a relative path, e.g. mirror or an absolute path in the form c:\mirror.

Please follow these instructions for submitting suspicious files to ESET for analysis.

Hello, the only issues with Malwarebytes Pro were observed on Windows XP when the system hung after connecting a USB disk. We provided Malwarebytes with more information about the issue and informed them what they should fix but until now we haven't heard from them whether or when they are going to fix it. There's at least one vendor of such troublesome software who already issued a fix several months ago.

The website no longer contains the malware detected in the past. It will be unblocked in the next update. Next time, we recommend reporting blocked websites to ESET as per the instructions here.

Dump files are generated when ekrn crashes. If a computer crashes with BSOD, you need to look for the dump created by Windows, ie. by default c:\windows\memory.dmp.

Installation via the above mentioned batch file worked fine on Windows XP. Couldn't it be a problem of rights / UAC as administrator rights are required for installation?

To date, the following drivers have been identified to cause lockup issues on Windows XP when used concurrently with ESET products: %windir%\system32\drivers\wavxdmgr.sys 06.06.00.066 (WAVE EMBASSY® Security Center) %windir%\system32\drivers\InCDfs.sys 5.9.10.0 (Nero) %windir%\system32\drivers\sandbox.sys 15/6/2011 (Agnitum Outpost Firewall) %windir%\system32\drivers\mbam.sys (Malwarebytes paid version) %windir%\system32\drivers\PDFsFilter.sys (PerfectDisk OptiWrite Filter Driver) %windir%\system32\DRIVERS\YahooStorage.sys %windir%\system32\DRIVERS\xlkfs.sys (Easy File Locker) %windir%\system32\DRIVERS\PCTCore.sys (PC Tools Kernel Driver Suite) %windir%\system32\DRIVERS\FSPFltd.sys (FSPro Labs My LockBox 2) If you experience lockup issues after installing ESET NOD32 Antivirus or ESET Smart Security on Windows XP, check for the presence of the aforementioned drivers. If found, rename the driver in safe mode or uninstall the troublesome software to see if it resolves the issue. Should the problem persist, generate a complete memory dump from the point the issue occurs as per the instructions here. To enable manual generation of memory dumps, right-click this link, save the file on the disk and run it with administrator privileges. Once you have generated a memory dump, contact Customer care or an ESET moderator for further instructions.

This option will be added in the next v7 beta build that should be available for testing soon.

No probs here. Make sure real-time protection is enabled and v7 reports to Action Center fine.

There's no server displayed because no client has connected to the ERA Server yet. If you install a client locally and configure it to report to ERAS on localhost, will it appear in ERAC?

Yes, it works that way for security reasons. If it was possible to import configuration from xml files from the command line, malware could easily misuse it to disable the protection modules.

Passwords are not stored within the configuration xml for security reasons; this is a deliberate behavior.

The command line switches control the behavior of the msi installer, not the program itself. After upgrading to a newer version, a notification suggesting a computer restart is always displayed in the main window. Until the computer is restarted, old binaries will be used, hence a restart should be performed as soon as possible.

This is not a bug but a feature. Missing Windows updates are not supposed to change protection status, it's indicated by an tray icon with an exclamation mark.

ESET Endpoint Antivirus does not intervene in network communication as it doesn't contain an NDIS driver at all. Only HTTP and POP3 protocols are checked at WFP level.

If you go to Setup -> Network -> View temporary IP address blacklist, are there any IP addresses in the list?