Question Windows ELAM preventing booting of OS

[EternalDB]

Hi there.

So, recently i have been bugged by an issue where my PC will not boot into windows. When i boot the pc, it performs an "Auto Scan" where it "diagnoses" my pc for errors. I then get a pop-up stating that my PC "did not start correctly" and asks me to restart my system or go into advanced options. I then change the start up behavior to skip ELAM (Early launch antimalware) and my pc boots perfectly fine after this. I don't recall downloading anything as of late, so i am unaware as to how this virus got on my computer (or if it even is a virus, is it possible the boot sequence is corrupt? Would i have to fix it using bcdedit in the command line?)

Thanks for the help!

 

[onespeedbiker]

ELAM is not a virus, it is a Windows utility usually enabled in your bios. Go into your bios boot section and disable "Secure Boot Control". If that doesn't work you might want to try disabling ELAM https://www.tenforums.com/tutorials...nch-antimalware-boot-start-driver-policy.html

 

[EternalDB]

ELAM is not a virus, it is a Windows utility usually enabled in your bios. Go into your bios boot section and disable "Secure Boot Control". If that doesn't work you might want to try disabling ELAM https://www.tenforums.com/tutorials...nch-antimalware-boot-start-driver-policy.html

Ok so i disabled secure boot, and even tried disabling ELAM through gpedit.msc but still nothing. It requires me to basically boot my machine twice, once to let the scan fail so i can activate the advanced startup, and then after it boots again i have to disable ELAM by pressing 8. It only disables it once though, so i have to waste about 2 minutes waiting for the scan to finish each time i start up my PC.

 

[ex_bubblehead]

I would spend far more time correcting the boot problem and far less time trying to mask the issue by disabling things. There's a reason it's auto scanning the system on every boot. Fix that and the other issues will magically disappear.

 

[onespeedbiker]

Okay, try this. If it does not solve your problem than ELAN is not the issue; as mentioned above it may be a symtom fo something else. https://winaero.com/blog/permanently-disable-early-launch-anti-malware-protection-windows-10/

 

[onespeedbiker]

Your problem may also be with Fast Start-up. Fast Start saves the system state in flash memory (or similar) which is not supposed to be volatile when powered down. When the Fast Start fails (and does not shut down properly), your computer reboots without fast start, which may be why it is successful the second time (have you ever not changed anything and just let your computer e-boot?). To turn off Fast Start go to the control Panel, choose Power Options>Choose what the power buttons do> Change Settings that are Currently Unavailable> and uncheck "Turn on fast start up".

 

[EternalDB]

Your problem may also be with Fast Start-up. Fast Start saves the system state in flash memory (or similar) which is not supposed to be volatile when powered down. When the Fast Start fails (and does not shut down properly), your computer reboots without fast start, which may be why it is successful the second time (have you ever not changed anything and just let your computer e-boot?). To turn off Fast Start go to the control Panel, choose Power Options>Choose what the power buttons do> Change Settings that are Currently Unavailable> and uncheck "Turn on fast start up".

First of all, sorry about the late response, i do not get any notifications for some odd reason so i have to check here manually.

Second, i did the command prompt thing you suggested via that link, still no success. Same goes with disabling fast start up. However, i did end up taking a look at the log file. This is what it says. Now please note, the fourth line from the bottom confused me. It said that the boot file is stored on e:\windows but my windows installation is located on my C drive... very odd if you ask me

--------------------------------------------------------------------------------------------------------
Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎5/‎8/‎2019 7:25:05 PM (GMT)
Number of repair attempts: 1

Session details
---------------------------
System Disk = \Device\Harddisk2
Windows directory = E:\WINDOWS
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 109 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 844 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for installed LCU
Result: Completed successfully. Error code = 0x0
Time taken = 3515 ms

Test Performed:
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code = 0x0
Time taken = 2406 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code = 0x0
Time taken = 625 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms

Root cause found:
---------------------------
Boot critical file e:\windows\system32\drivers\mbamelam.sys is corrupt.

Repair action: File repair
Result: Failed. Error code = 0x57
Time taken = 1485 ms

---------------------------
---------------------------