Who is affected?

If you installed DESlock+ Client 4.8.17 between August 3rd and August 24th, 2017 and performed a full disk encryption with this version, we strongly recommend that you back up all information on your systems and refrain from restarting unless you have already decrypted the system disc. There is a marginal possibility that the encryption was not done properly, which could cause your system to assume an unusable state under some circumstances. Systems on which full disk encryption was performed using earlier versions are safe, even after upgrading to the affected versions.

Solution and workaround

We expect to release updated builds of these solutions soon and apologize for any inconvenience.

Users who are already affected and who manage their DESlock+ Client using DESlock+ Enterprise Server should contact ESET or DESlock+ support immediately and ask for assistance, as it should be possible to create a unique utility for each system that reverts the problematic encryption. Standalone users who don’t use DESlock+ Enterprise Server unfortunately do not have this option.

Version log

Version 1.3 (Aug. 31st, 2017): additional information added
Version 1.2 (Aug. 29th, 2017): third version of this document