Marcos

Since I don't know how exactly other anti-exploit solutions work, it's impossible for me to compare v7 with them. Basically it should protect browsers and certain system processes against malware exploiting vulnerabilities.

Just to make sure that Device control is not loaded, run the following command with elevated rights and post the output: "sc query edevmon"

Yes, but this could be a problem if you have several dozens of computers that do not connect to ERAS and have settings protected with an unknown password. In such case, you'd need to resort to installing an ESET product on clients while using a custom configuration with no password set or push an uninstall package on the clients and then install a product package on the clients with no password set.

Do those files have a special extension added, such as OMG, GOD, etc? It's likely that the files got encrypted with GpCode or a recent advanced Filecoder variant and the chance of recovering them is low. Anyway, send me 2-3 encrypted files attached to a personal message for analysis. For more information about Filecoder ransomware and the way they get into computers, please read these blogs: hxxp://www.welivesecurity.com/2013/09/23/filecoder-holding-your-data-to-ransom hxxp://www.welivesecurity.com/2013/09/16/remote-desktop-rdp-hacking-101-i-can-see-your-desktop-from-here

Regarding staggered releases, not only software has to be perfectly ready for release from the technical point of view but also all distributors worldwide have to be ready for the release on local markets (it also includes manufacturing CDs, marketing campaigns, etc.). Thanks to the staggered release, the second wave builds will have an issue with Outlook 2013 fixed.

ESET has always been fully compatible with Windows XP. Regarding the software causing incompatibility issues, it was confirmed by programmers that the problem doesn't lie in ESET products but in the problematic 3rd party drivers.

In order to download the engine ending with "P", you'll need to switch to pre-release updates in the advanced update setup.

Yes, you can schedule a scan via Scheduler which will be run in the background regardless if a user is logged or not.

Not, the mentioned programs use improperly written drivers causing issues in conjunction with ESET's drivers on Windows XP.

Is there a reason why you installed ESET Endpoint Antivirus or Security on servers instead of ESET File Security? Does the problem occur with protocol filtering disabled?

For me personally, Advanced memory scanner is the most valuable improvement in v7 as it can protect users against a huge number of zero-day threats without the need to update. It's supplemented by Exploit blocker (HIPS) and Vulnerability shield (firewall). Also it's much easier now to exclude addresses from active protection when an attack is attempted from a trusted remote device (firewall).

You can disable automatic updates in Scheduler. Of course, this will change the protection status as this action puts the computer at risk if the user forgets to update ESET on a regular basis (updates are usually released in 3-4 hour interval).

Even older versions have modules already fully compatible with Windows 8.1. If you have an issue with v5/v6 on Windows 8.1, please contact Customer care who will assist you like with any other issue.

In safe mode, try deleting the value HKEY_LOCAL_MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Info\WscState

When an attack attempt is detected by v7, it should offer you an option to trust the source address and to exclude it from active protection. Watch this demonstration video: IDSv7.mp4

Not sure what exactly you've deleted. Are you getting an error when ESET is loading upon Windows start ? Have you tried running update manually and restarting the computer?

Does clearing update cache make a difference? If not, try uninstalling v7 and installing it from scratch.

It's normal to release products in 2 or more waves. The 2nd wave will follow in a few weeks. If you can't wait, feel free to install v7 beta as it's perfectly stable and the final version will be released with minor changes or fixes.

Win32/Systweak fulfills criteria of potentially unwanted applications, ie. t's not FP. If you make changes to the application so that it no longer meets criteria for PUA detection, contact ESET at the above mentioned email address and request re-evaluation of the application.

The list shows program component updates that are available on the server your EFS updates from. Do you have the update server set to "Choose automatically"? At any rate, there has been only one program component update for Endpoint so far which can be installed per the instructions here.

An error communicating with drivers occurs after a fresh installation on Windows 8.1 because the HIPS driver included in the current installation package is not Win 8.1 compliant. However, after restarting the computer the error should be gone and everything should work like a charm. Should the problem persist after the computer restart, please post information about installed modules from the About window. We'd also like to ask you to create a new topic to tackle a particular issue as this topic is meant for posting suggestions for future versions.

Couldn't it be that you have Spector surveillance software installed? It's detected under that name.

Firewall settings are stored in a data file on the disk. If the computer is not shut down properly, it could obviously cause a loss of firewall settings, especially if writing to the dat file was unexpectedly interrupted by power outage.

The issue was also reported on a Microsoft's forum by a user with only MSE installed: I only have Microsoft Security Essentials running, you would think that Microsoft's own product wouldn't break Outlook.

Try sending a test email to yourself with the eicar test file attached to see if it's moved to Infected items.