An error occurred communicating with the ESET Endpoint Encryption subsystem
The ESET Endpoint Encryption (EEE) client software includes a service component. If this service is not started then 3 minutes after EEE is launched an error will appear detailing "An error occurred communicating with the ESET Endpoint Encryption subsystem. The ESET Endpoint Encryption software may not be installed correctly."
1. Old version of EEE (formerly DESlock+) being installed on newer operating system
The most common cause for this error is when an out of date EEE client is installed on newer operating systems.
Installing EEE versions older than v4.7.5 on Windows 10, or on Windows 8.1 with the November 2014 rollup, will exhibit this problem.
Installing the current, most recent version of EEE will fix this issue.
If you still see the error after updating to the latest available version of EEE then you should check to see if the EEE service is present and running. To do this follow the steps below:
2. Service not present
3. Startup type incorrect
The Startup Type of the DESlock+ service should be listed as Automatic. If the Startup Type is incorrect follow these steps:
4. Service not started
If the service Status is blank or Stopped start the service using these steps:
5. Create/adjust a registry key to adjust the service start-up time allowance
If starting the service manually and rebooting the machine does not fix the problem, then perform these steps:
6. Other solutions
We have seen cases where some anti-malware and anti-virus systems incorrectly flag the EEE service and prevent it from being installed. You should check the logs of any such utilities to verify this is not the cause of the problem you are experiencing. If the software is being incorrectly flagged you should ensure that the EEE software is white listed and the install repair process performed.
We have seen rare instances where other software being installed recently prevents the DESlock+ service from starting. You should ensure you restart Windows again if this is the case as it may resolve the problem.
If the client in question is managed by an EEE Server you should also check the logs of any Firewall software to see if it has blocked the DESlock+ Service from starting.
KB200 - Recovering from a bluescreen caused by installing DESlock+ on Windows 8.1 with November 2014 Rollup.
Keywords: 0xC01C0007, timed, out, install