Marcos

As long as it's valid it's possible to use any version of the product you purchased. However, since v2 was discontinued a long time ago I don't assume the license is still valid.

This issue will be fixed in the next firewall module build. You can work around it easily by installing v7 from scratch, just make sure the folder c:\ProgramData\ESET\ESET Smart Security doesn't exist prior to installing v7.

Please post detailed information from your Threat log (ie. the path to the file, the name of the threat detected, action taken and other additional information).

No, only business versions of the products allow for creation of a local copy of update files (so-called mirror). What's the approximate size of the files you have issues with? Are you able to download smaller files than 10 MB fine?

I'd suggest sending a couple of encrypted files to ESET as per the instructions here so that we can investigate if they can be decrypted.

No, it won't work. Firts, Document protection must be integrated in the system. Only after then you can control whether it scans documents or not. As I wrote, I wouldn't recommend enabling integration as it may affect system performance due to a bug in MS Office. Even with document protection disabled, real-time protection will scan MS Office documents anyway.

Enabling Document protection integration will effectively register it in the registry (due to a bug in MS Office causing performance issues, it's disabled by default). Enabling or disabling Document protection will enable or disable document scanning via VSAPI (possible only with integration enabled).

Ok, so what about disabling Web protection or firewall via gui or Protocol filtering in the advanced setup?

Please follow my instructions posted in the topic https://forum.eset.com/topic/693-failed-to-read-firewall-configuration-after-latest-vsd-or-module-update/

Couldn't it be that you enabled Parental control but DNS requests are not getting through? Does disabling Parental Control or Web protection make a difference?

Just to make sure, you mean scheduled scans and not scans that you run manually via gui, right?

Since antivirus software is deeply integrated with the operating system, any upgrade to a newer version may potentially cause issues. For this reason, ESET has never rushed with program components updates and pushed them to users within a short time. ESET cares about safety of their customers and we will never take actions that might jeopardize the stability of users' systems.

Please create a Process monitor log from a boot as per the instructions here. When done, compress it, upload it to a safe location and pm me the download link.

Should the above fail, see my advice in https://forum.eset.com/topic/692-era-server-failure-cant-connect-to-host-0x2101/.

I'd suggest carrying on as follows: - enable debug logging in ERAS setup - stop the ERA server service - delete the ERA logs in C:\ProgramData\ESET\ESET Remote Administrator\Server\logs - temporarily set the time interval for connecting to ERAS on a troublesome Endpoint client to 0 - start ERA server service If the client doesn't appear in ERAC, submit the logs from the aforementioned folder to Customer care for analysis. You can also upload them to a safe location and PM me the download link so that I can check them out.

It's a communication attempt within your computer. Make sure that you have logging of blocked communications disabled in the IDS setup.

For Firefox 22 and newer, you'll need to export the root certificate from ESS and import it to Firefox manually in order for https websites to open properly.

I thinik the question was regarding the untrusted ISP root certificate which is unrelated to ESET.

You can find this information in the header of file em002_32.dat.

Please compress the memory dump, upload it to a safe location and PM me the download link. No BSOD issues have been reported so far so it's likely it's caused by another driver.

The expiration date is synchronized with servers once or twice a day as far as I remember which could explain why a correct expiration date was shown on other laptops with a delay.

It has not been confirmed as a bug by engineers yet. If it's confirmed to be a bug, it won't be fixed before a service release of v7.

Of course these marketing statements must be taken with a grain of salt. Isn't it suspicious that popular rootkits / bootkits that died out a few years ago would be undetected by popular vendor after so long time? ESET basically protects against all of them but unfortunately it's not possible to verify them as the tester does not provide any useful information to other av vendors.

ESET stores temporary files in the system and user temporary folders pointed to by TEMP and TMP variables. Changing the variable values should do the trick.

I was able to reproduce it only once in the past. Since then the website opens fine with both older and latest Internet protection modules so I assume something has changed on the server or the occurrence of the issue depends on timing somehow.