The boot selection failed due to missing or corrupted SymELAM.sys error after uninstalling Endpoint Protection and rebooting.
search cancel

The boot selection failed due to missing or corrupted SymELAM.sys error after uninstalling Endpoint Protection and rebooting.

book

Article ID: 218274

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

When rebooting the client after uninstalling SEP, the following error shows on the Client screen:

 

Windows failed to start.  A recent hardware or software change might be the cause.

 Info: The operating system couldn’t be loaded because a critical system driver is missing or contains errors.

Status: 0xc000000f

File:\windows\system32\Drivers\SEP\xxxxxxxx\xxxx.xxx\x64\SymELAM.sys

Environment

Release : SEP 14.x

Cause

The SymELAM (Early Launch Anti-Malware) drivers got removed from the uninstall process but the service failed to unload which cause the reboot failure.

Resolution

Solution 1: Disable SymELAM service in the Registry

From the Windows Recovery screen Go to Troubleshoot > Advanced options > Command Prompt

  1. Type in Regedit
  2. Got to the following Services Hive
  3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
  4. Select the SymELAM service
  5. Change the DWORD Start value to 4 (Disabled)
  • 0 = Boot
  • 1 = System
  • 2 = Automatic
  • 3 = Manual
  • 4 = Disabled

      6. Close and reboot

 

Solution 2: Copy the content of the folder x64 from a working system

 Option 1:

  1. Go to a system that is running the same version of SEP
  2. Copy the contents of the x64 directory to the same directory on a system that is not booting.
  3. C:\Windows\system32\Drivers\SEP\xxxxxxxx\xxxx.xxxx\x64\
  4. Reboot the system after restoring the files

 Option 2:

  1. Restore the files from the Full Installation CD 
    • ..\Symantec_Endpoint_Protection_14.3.0_Full_Installation_EN\SEPx64\System32\Drivers\Name\Version\BuildNum\x64
  2. Reboot the system after restoring the files

 

Additional Information

First need to create a Temp folder ..load the hive and then make the changes on the registry and then unload the hive to make this resolution work.

Please see the screenshot as mentioned below 

You can run the command 

reg load HKLM\temp

reg unload HKLM\temp