Click Start → Run and then type regedit in the Open: text field and click OK. (In Microsoft Windows Vista, click Start and type regedit into the Start Search text field.)
Right-click HKEY_LOCAL_MACHINE and select Permissions from the menu.
In the Permissions for HKEY_LOCAL_MACHINE window, click Advanced.
Make sure both check boxes at the bottom of the Advanced Security Settings for HKEY_LOCAL_MACHINE window are selected.
Click OK to confirm and OK again to exit the Permissions window.
The following DELL Latitude systems are known to be affected when Legacy BIOS is enabled, and SATA Operation is set to either AHCI or RAID On:
Systems starting in UEFI mode are not known to be affected. Certain versions of the BIOS in these DELL Latitude systems are known to have a bug, which causes Full Disk Encryption to be unable to access the disk correctly during start. A black screen with a flashing cursor displays when starting your computer. This can occur directly after the system is Full Disk Encrypted, but can also occur at a later time after numerous successful restarts. This not only affects ESET Endpoint Encryption (EEE) Full Disk Encryption, but also many other manufacturers of software disk encryption.
DELL has provided a BIOS update that fixes the issue.
loginwindow.pliston macOS 10.13 only works if you upgrade with products that have the same application bundle name.
If you encounter these or similar symptoms, we recommend you add a scanning exception for the problematic streaming address to the http directory of the ESETS configuration directory. To exclude a streaming address from scanning, use the following instructions:
Append the streaming address you want to exclude from scanning to the whitelist_url file. To add an exception, replace the streaming address example in the following command by the address you want to exclude and run the command:
echo "streaming.address.com:80/*" >> /etc/esets/http/whitelist_url
To finalize adding/removing URL addresses, you must restart the ESETS daemon. Use the following command to execute an immediate restart:
For more information, use the following command to read the esets_http man page:
Protection not working for up to 30 minutes after upgrade to Kerio Connect 8.1.0 or newer: In a case when upgrading from Kerio Connect 8.0.2 (or earlier) to version 8.1.0 (which is a version that officially does not support external AV protection) the upgrade process of Kerio does not preserve ESK's registration (dll and configuration) which renders EKS protection not to work and Kerio Connect is not protected even though the protection status is still Green. This is only for a period of time until ESK checks for its registration. This check is performed every 30 minutes. If ESK finds that the registration is not correct, it automatically registers itself, restarts Kerio Connect and resumes protection. This makes the protection to work properly again. Hence the Kerio Connect may not be protected for a maximum of 30 minutes after the upgrade.
You can register ESK to Kerio Connect manually after the upgrade. This will turn the protection on immediately.
File server protection displayed when using Kerio Control: On a system with Kerio Control, ESET Security for Kerio displays File server protection in its main program window in the Setup section. This is expected behavior, and when enabled, it means the Kerio Control is being protected by ESET Security for Kerio.