Eset Smart Security 5 have Serious bug(chinese edition)

When I installed Eset Smart Security 5，everything is OK，but when I restart PC，The OS has been stopped in the welcome screen，Can not enter the desktop，Finally, I can only enter the safe mode uninstall ESS 5.Exchange Eset Smart Security 4，everything is OK.Many people have this problem,They also can not enter the desktop.
my OS ：windows 7 sp1 32bit

 

Does disabling automatic real-time protection make a difference?

 

The OS has been stopped in the welcome screen，I Can not enter the desktop,I can not enter the system, only in safe mode。。。

 

Ok, so try renaming C:\WINDOWS\system32\drivers\eamonm.sys in safe mode and let us know if it helps.

 

Hi ScoScorpio,
we already start a discussion about this problem in this thread:
https://www.wilderssecurity.com/showthread.php?t=307522

 

This method really worked! Thanks!

 

This is not a solution, I just wanted to confirm or deny that the issue is related to the real-time protection driver. Renaming the driver will effectively disable real-time protection which is the most crucial protection module.

 

Yes, I figured. And there is actually a tiny chance to finish log on process before I changed the file name. Not sure about the real problem tho.

 

This method really worked.my friends have same problem,they all use win7 X86 system,when they renaming C:\WINDOWS\system32\drivers\eamonm.sys in safe mode,it really worked.other people tell me,they use win X64 system, everything is ok.

 

Like Marcos said before, this is not the solution, but just a step to make sure where the problem is. By renaming eamonm.sys you basically disable your protection.

 

hmm i hope this helps but this happened to me but a little differently, i have slightly modified my winlogon.exe so i could have a picture everytime i log in, what happened with me is i was not stuck at log on screen instead i could go on my desktop but i could not open any programs, i could go in C Drive and go in folders but could not open. im taking a guess that the problem why this happen might be the Policy Base mode, but i dint check it cause i did a system restore in safe mode.

 

In order to run programs in the policy based mode, you need to create some allowing rules.