Hi Eset. I'm currently using ESS 4.2.64.12 on Windows 7 32 bit. It's been 3 weeks that I'm experiencing slow startup. Starting Windows screen takes 15 seconds to complete and so does Welcome screen. After that my computer screen went black for 12 seconds before it shows my desktop. What's going on here? Thanks.
Hello encus, Just an idea you could try You could try to go into msconfig and disable everything (or one thing at a time,that is probably better) besides Eset and Windows operating system, and see if that will make a difference. Most often the msconfig is totally clogged with unnecessary startup commands.That sometimes, or most often, gives tremendous long boot time or other conflicts. ( have a nice weekend, encus) Cheers, Janus
The first thing I do when I install ESS or NOD32 is open the main program window, go to Tasks, and uncheck the box which says scan startup files upon logon. It's the second checkbox from the bottom. NOD32 / ESS will catch any harmful files on startup anyway no need for that option as it slows down start up dramatically
Does disabling HIPS or automatic real-time protection start followed by a computer restart make a difference?
Are you sure that this is safe? No fense berryracer, but can someone from Eset officially confirm this? Thanks.
I tried to disable automatic real time protection followed by a system restart and Yes! my computer doesn't slow anymore on startup. Enabling it again will bring back the problem. Thanks Marcos.
Please check if you use default real-time protection settings, especially that advanced heuristics is not enabled on file access (Setup -> Computer -> Antivirus and antispyware -> Real-time file system protection -> Setup -> Options -> Advanced heuristics / DNA / Smart signatures). If you attempt to access a network drive, does disabling scanning of network drives help as well?
Then generate a Process monitor boot log as per the instructions here, compress it, upload it to a safe location and PM me the download link.
Its funny that you say this as on my i7 computer, it only adds a couple of seconds to boot. I guess it really depends on how old your rig is.
Needless to say that disabling startup scans effectively removes an additional layer of protection (memory scans) and makes the computer more vulnerable to malware. If one runs into performance issues on certain systems, just report it to us and we'll do our best to figure out the reason and solve the issue.
A useful option I would like is that one could perform a start-up scan by right-click on the tray icon and choose "Run Startup scan". That way one can choose to do it whenever, and as often as one like. E.g one doesn't need to wait for an VSD update, or restart the computer. I guess I could open the GUI an perform an on-demand scan, but be able to do it via the right-click tray menu is faster. Just watch the tray icon spinn for a few seconds and the whole thing is over, without the need to open any windows
If I restart the computer, everything is back to normal again. This problem always occurs at the first moment I turn on my computer. So strange
The start-up scan is runned automatically a couple of minutes after the system has finished loading, plus after every VSD update.
You may find it helps to set the startup scan to run when the machine has settled down after loading initial startup items. You can achieve this by going to tools > scheduler > find startup check (user logon) > click [edit] > next > next > next > finish > change scan priority to "when idle." You may also find this KB article on decompression errors useful: http://kb.eset.com/esetkb/index?pag...earch&viewlocale=en_US&searchid=1350999575630 I hope this helps.
