[KB8103] Resolve ESET Endpoint Encryption Pre-boot screen repeatedly prompting for credentials (5.0.0 only)

Issue

ESET Endpoint Encryption (EEE) Client and EEE Server are separate products from ESET Full Disk Encryption (EFDE)

The article below applies only to the EEE Client or EEE Server and not EFDE.

Visit What's new in ESET Full Disk Encryption to view EFDE content.

  • Resolve an error where you cannot log in to your Full Disk Encryption (FDE) pre-boot screen in ESET Endpoint Encryption (EEE) version 5.0.0 
This is a specific solution for EEE 5.0.0

This problem only affects systems that meet the following criteria:

  • ESET Endpoint Encryption version 5.0.0 is installed
  • Version 2.3.62 is displayed in the bottom right corner of the pre-boot screen
  • The system is UEFI
  • The system has a disk that supports OPAL encryption

This issue will be resolved in the next version of ESET Endpoint Encryption.

Details

On a system with UEFI and Full Disk Encryption (FDE) with ESET Endpoint Encryption version 5.0.0, when you type the correct FDE username and password, the system does not boot and prompts you to type your username and password again. This appears as the system is looping.

Windows or another software package has taken partial ownership of the OPAL disk in the machine and that causes EEE to incorrectly assume that OPAL encryption is in use.

If your bootloader version does not match the version in the image below (v2.3.62, ignoring US or UM) do not follow the solution in this article. Instead, contact ESET technical support for further assistance.

Solution

  1. Create a bootable UEFI USB device on a different machine
  2. Recover the workstation with this issue with the USB Device
  3. Confirm the USB script has replaced the bootloader
Prerequisites
  • Ensure that the system that requires recovery matches the criteria listed at the top of this article. You may cause further damage if you apply this solution inappropriately. If in doubt, contact ESET technical support for further assistance.
  • Before proceeding, perform a full sector-by-sector backup of the machine.

Follow the steps below to resolve the issue.

I. Create a bootable UEFI USB device on a different machine

ESET provides a hotfix EFI script that will replace the v2.3.62 bootloader with the previous version. You need a blank USB device formatted as FAT32. Ensure any important data is moved off the USB device before formatting it as FAT32.

  1. Download the hotfix file.

  2. Unzip the file and copy the efi folder to the root folder of the formatted USB drive. Your USB device should look like this:

    Figure 1-1
    Click the image to view larger in new window

II. Recover the computer with this issue with the USB Device

  1. On the computer experiencing the problem, enter the system UEFI settings and turn off Secure Boot. This is temporary.

  2. Save and exit the UEFI settings and turn the computer off.

  3. Insert the USB device and boot the computer holding the necessary key to access the boot menu.

  4. Select the USB device from the boot menu and press Enter to boot from it.

  5. The EFI script on the USB device will run automatically, replacing the v2.3.62 bootloader with v2.3.53.

    Figure 2-1
    Click the image to view larger in new window
  6. If successful, the script will prompt you to restart your system. To do this, press any key on your keyboard.

  7. Enter the system UEFI settings again and turn Secure Boot back on. Save and exit the UEFI.


III. Confirm the USB script has replaced the bootloader

  1. After restarting the machine, you should now see bootloader v2.3.53 in the bottom right hand corner of the screen.

    Figure 3-1
    Click the image to view larger in new window
  2. Log in with your FDE username and password to boot Windows as normal.

  3. If this has not resolved your issue, contact ESET support for further assistance.