Marcos

That's not possible. However, for scheduled scans you can choose whether users will be able to pause or cancel them. I for one don't see any sense in having such option; scans would then always end before they are completed if they started at a fixed time and had to be terminated at a fixed time too. Do the users have a lot of big archives or images on disks that scans take more than 7 hours?

Please remove all exclusions seen they are entered incorrectly. A full path must be used and exclusions like *.log will not work but may rather cause issues. The ERA CE validator will need to be adjusted to prevent such exclusions from being entered. If you want to exclude the mentioned PUA from detection completely, use an exclusion like this:

Please post the appropriate records from the Detected threats log as well as a screen shot of your exclusion setup.

Isn't it possible to exclude just the IP address of the server or application from protocol filtering?

Does temporarily disabling protocol filtering in the advanced setup make a difference?

With the change of the ISO to isohybrid, we stopped providing a SysRescue medium creator. Use an arbitrary application for that, such as UNetbootin, Etcher, Rufus, etc.

We already kindly asked you to stop trolling. If you are not satisfied with no 100% detection, you can use any AV you like. However, we live in a real world and there's no security software that could 100% protect you from malware so sooner or later you'll get disappointed with other AVs too if you don't accept that fact and if you don't contribute to safety by practicing safe computing. Here are some tips that one should practice to stay safe: 1, Patch, Patch, PATCH 2, Back up, back up, BACK UP 3, Install protective software and keep both the program and modules updated. Do not disable any of the protection modules. 4, Choose strong passwords. 5, Control access to your machine. 6, Use email and the internet safely, do not open unknown emails and attachments. 7, Use secure connections. 8, Protect sensitive data, use encryption. 9. Most importantly, stay informed. Since everything has been said, we'll draw this topic to a close.

The detection is correct. The application is correctly classified as potentially unwanted. If you want to continue using it, in the yellow window with action selection expand advanced options and select "Exclude signature from detection" which is safer than disabling PUA detection completely:

In case of issues with SSL related to ESET's root certificate, start off by carrying out the following procedure: - disable SSL/TLS filtering - restart Windows - without launching any browser or email application, re-enable SSL/TLS filtering - after 2-3 seconds, launch a browser and check if the issue has been solved.

Since HIPS is a very sensitive module that may cause sever system issues if released with a serious bug, its releases are staggered and it may take up to one month until all users will receive the updated module.

We'd need a complete memory dump from the point when the system is unresponsive to confirm it's indeed caused by a clash with MBAM. For instructions how to configure Windows to generate memory dumps and how to initiate a system crash manually, please refer to https://support.eset.com/kb380.

Since HIPS doesn't work, neither other HIPS-dependent modules Exploit Blocker, Self-defense, Ransomware shield do. No vendor can guarantee that their programs will work with newer Insider Preview builds of Windows 10. Therefore Insider Preview builds should not be installed on production computers or computers where security matters.

No. This was asked 2 days ago during weekend and today is the first work day after the weekend. It's not matter of minutes to make changes to the program code, test it and release it. We are working on it and will let you know once an updated module has been released on pre-release update servers.

Did you use a wrong topic name and you actually meant "Installing ESET Secure Authentication" or do you have any issues installing the ERA Server as well?

Was that a fresh install or upgrade? At any rate, try running the Uninstall tool in safe mode and then installing ESET from scratch. Should the problem persist, we'll need a Procmon log created during an install attempt and fresh ELC logs.

If you don't want any action to be taken at the end of the scan, select "No action" in the above screen.

Simply ignore them. Even if you run a scan as an administrator, there will be plenty of files that are exclusively being used by the operating system so no application has access to them, be it a legitimate AV scanner or malware.

I would check the list of installed applications and remove those that you don't 100% trust. It doesn't have to be necessarily malware, maybe it's just the ring sound played by an application for some reason.

I don't think that excluding any files or folders in ESET would prevent possible clashes. When troubleshooting issues, the only way how to 100% confirm or rule out involvement of a particular sw in the issue is by temporarily uninstalling it.

It's been tracked as bug/improvement. Anyways, I'd recommend anybody who considers disabling protocol filtering or HTTP scanning to watch the attached video to better understand that it's not a good idea to disable web scanning completely even if more web scanners are installed. Adguard_vs_ESET.rar

MBAM with its real-time protection driver clashes with ESET. If you want to use it in tandem with ESET, use it as an offline scanner without its drivers being loaded. For troubleshooting, I'd recommend removing MBAM at least temporarily. The best would be if you could provide a complete memory dump from the point when the issue occurs by manually generating a crash as per https://support.eset.com/kb380.

What kind of application is it? If it communicates with a specific server, it should be enough to exclude the IP address of the server.

It looks like upgrade from an older version is failing. What version of ESET do you have currently installed? Should the problem persist, uninstall ESET and install the latest version from scratch.

Please refer to my previous post: This is a known issue with Insider preview build 17704. We should have a solution soon.

Please post a screen shot of the "Certification path" tab.