Technical support

Knowledgebase: Software
Windows 10 Compatibility
Article ID: KB245 email a link to this article

Windows 10 is supported with ESET Endpoint Encryption client v4.8.0 and later, and ESET Endpoint Encryption Server v2.6.0 and later.


For Windows 10 machines running build version 10240 must have the cumulative updates installed. For more information read this article: KB273 - Error "The latest Cumulative Update for Windows 10 must be installed" displayed when installing  (This applies to the ESET Endpoint Encryption client only)


Full Disk Encryption

If you are upgrading or updating from Windows 7, 8, 8.1 or an earlier version of Windows 10 to the latest version of Windows 10, and have Full Disk Encrypted your machine, the upgrade will fail. To avoid this, follow this article here: KB462 - How to manually install Windows 10 Feature Updates on an Full Disk Encrypted (FDE) system 

Folder Encryption

If you are using ESET Endpoint Encryption encrypted folders with your existing operating system it is recommended you first uninstall ESET Endpoint Encryption before upgrading to Windows 10 as detailed here: KB329 - Uninstalling ESET Endpoint Encryption 

Once the upgrade of the operating system is complete the ESET Endpoint Encryption client can be reinstalled.

Failure to remove ESET Endpoint Encryption before updating may mean your encrypted folders will be not located in their normal location. Instead an empty folder will be located there instead.  The original encrypted folder, containing your encrypted data, will instead be found in the folder Windows.old on the root of the system disk. 

e.g. the folder C:\Users\"user"\Desktop\encrypted folder will be found in C:\Windows.old\Users\"user"\Desktop\encrypted folder

Known Issues

(Resolved in version 4.8.0 onwards)

When using the previous release version of DESlock+ v4.7.8 on test systems with Windows 10, we observed the following issues: 

  • Systems became unresponsive to keyboard input and would not redraw the screen correctly at the Windows login screen or when resuming from hibernate/standby. The problem was more likely to occur the longer the operating system is left at the login screen.
  • Some systems were not be able to shutdown correctly once full disk encryption has been performed and the system would remain powered on requiring a forced power cycle to clear.

We use cookies on our website to enhance your browsing experience. Read more