Technical support

ESET Endpoint Encryption Windows Installer (MSI)
Article ID: KB288 email a link to this article


The installation for ESET Endpoint Encryption (EEE) is a Windows Installer (MSI) package. This enables deployment using a variety of methods.

The EEE installation is provided as either a 32-bit (x86) or 64-bit (x64) package. Localised versions are available in various languages.

Aside from these differences the same package is used for all editions (licence types) of EEE and the same package is used for managed users.

When managing clients using our EEE Server a Merged Installation package must first be downloaded or pushed from an EEE Server. It is vital that a merged installation package is used as this pairs the client workstation with the EEE Server for secure communication. From the moment EEE is installed the Workstation Policy chosen when downloading or pushing the install package is applied for all users.

When downloading or pushing the installation from an EEE Server you can also enable Managed Uninstall Mode which will block the removal of EEE by all users (including Administrators) unless a unique Uninstall Code or optional password is supplied. 

Ways to deploy the EEE client software

If you forget to generate a Merged Installation and install the normal package on a workstation the following article describes how to fix that without having to uninstall and reinstall.

KB286: How do I convert a Standalone ESET Endpoint Encryption client to a managed client?

We do not support, or recommend installation via the use of software that attempts to capture and replay actions performed by our install. This may result in all or some components of our software being installed incorrectly and will remove additional safety checks we have in place to protect users. The most important of these prevents end-users removing the software when their workstation is Full Disk Encrypted. The Windows Installer package should come directly from our website, or be downloaded from an EEE Server.


Can I activate a user during installation?

No. Activation has to take place when the user being licenced is logged in to their Windows profile. EEE is licenced and managed on a per-user basis. During deployment, especially when using push install, installation is often performed in the context of an Administrative user meaning there is nothing to connect a licence to a user during installation.

EEE has a simple, single-click activation scheme described here KB216: How do I activate a managed version of ESET Endpoint Encryption? All that is required, providing options are set correctly, is for the user to click a link in an email.



EEE does not usually require the use of a Merged Installation package when upgrading.

The exception to this is where the Workstation being upgraded was originally installed using a package with Managed Uninstall Mode enabled. In this case it is only possible to upgrade by using an installation package that has also been generated from an EEE Server via Download Merged Installation with Managed Uninstall Mode enabled or through the use of the client updater.



See KB248: Removing ESET Endpoint Encryption from a workstation


Command-line parameters

As the installation is a standard Windows Installer (MSI) package all standard msiexec.exe command-line parameters can be used. 

Silent installation

To install silently you can use the /q command line switch when calling the client package as a parameter of msiexec.

This will automatically reboot once installation has completed.

Command-line: msiexec /i "EEE.msi" /q 

Silent installation without automatic reboot

Similar to the above, but with the addition of a parameter to stop it automatically rebooting. You will not be able to use EEE until a full reboot has been performed.

Command-line: msiexec /i "EEE.msi" /q REBOOT=ReallySuppress 


All uninstall actions require a unique identifier (UID). This identifier changes for every version of EEE, and changes each time a merged installation package is downloaded from an EEE Server.

Finding the UID for EEE. Easy way (can be slower)

  • Open an elevated (Administrator) command prompt
  • Type wmic product where "Name like 'EEE'" get Name, Version, IdentifyingNumber
  • Wait until result is displayed (On a fresh copy of Windows this can be instant, this can take a while)
  • Results similar to the following will be displayed:

    IdentifyingNumber  Name Version
    {09EEF587-681B-4974-8C02-22ED3EC3127A} ESET Endpoint Encryption  4.9.4
  • Take note of the UID. (In this case {09EEF587-681B-4974-8C02-22ED3EC3127A} )

Finding the UID for EEE. Advanced way (faster).

  • Run regedit.exe
  • Navigate to, and select the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products
  • Search for "ESET Endpoint Encryption"
  • The key selected is the Windows Installer entry for the EEE installation.
  • The UninstallString and ModifyPath values contain the UID

Starting uninstallation from the command-line

Command-line: msiexec /x {UID} 

Additional parameters when silently uninstalling

The same parameters that can be used during installation can be used when uninstalling.

Silently uninstalling from the command-line

This will automatically reboot once installation has completed.

msiexec /x {UID} /q

Silently uninstalling from the command-line without automatic reboot

In this case, re-installation of EEE will not be possible until a full reboot has been performed. It is also worth pointing out that although the workstation is not rebooted Windows Explorer will be restarted.

msiexec /x {UID} /q REBOOT=ReallySuppress

Removing ESET Endpoint Encryption with Managed Uninstall

An additional switch must be added when managed uninstall was used in the original MSI.

To locate the uninstall code, please see 'Obtaining the Uninstall Code' in this article: - What is the Managed Uninstall option?

Once you have both bits of information, your command line entry should look like this:


Diagnosing problems related to installation

If a problem with the installation, or uninstallation appears to be connected to the EEE Window Installer package we will need a log to investigate further. Details of how to create one can be found in KB224: How to enable Windows Installer (MSI) logging.

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