Delayed startup in Windows 10

[DinGo 22]

Running NOD32 version 8.0.319.0 in windows 10, I get a delay of up to 50 seconds after reaching the desktop before NOD32 appears in the tray.

 

I realise this is probably a Win 10 issue but is anyone else experiencing the same?

Edited August 3, 2015 by DinGo

[SMK 0]

I have the same issue in cases of Windows 10 startup and Shutdown/Sleep.

 

I have a PC with Intel Core i7 3.4GHz CPU, 8 GB memory (RAM) and 500GB SSD drive.

I've upgraded it to Windows 10 Pro from Windows 8.1 Pro.

 

After I installed ESET Smart Security 8.0.319.0 (30 day free trial) on this machine (Windows 10 Pro), it starts up and Shuts-down/Sleeps remarkably slower than before. And, sometimes, the computer does not responding for minutes when it goes to Sleep mode (either manually or automatically when it is left idle for long time) or when I click Shut down button on start menu. Sometimes, it does not resume at all from that states and I have to shut down the pc manually by pressing the power button for seconds.

 

I'd faced the same issue with ESET SS 8 on windows 8.1 before upgrading.

​

Knowing that, I'd uninstalled ESET SS 8 from Windows 8.1 Pro before upgrading to Windows 10 Pro. Then I installed a new copy of ESET SS 8 (free trial) on Windows 10 after upgrading.  ​

[shocked 60]

i use win 10 and eset ss 8.0.319.0, there is a slight slow down but i guess it must be the OS  since it's new and there might be issues untill several updates are released and solve most of them.

[SMK 0]

Thank you for your reply.

 

No, it is not the OS, because it was working normally and smoothly with Windows Defender, before installing ESET SS 8. In addition, I had the same issue in Windows 8.1 Pro before upgrading to Windows 10 Pro. Moreover, it slows down not just the computer Startup but also the computer Shut down and Sleep, and sometimes the system (Windows 10 Pro and Windows 8.1 Pro before upgrading) does not respond at all when it goes to shut down and sleep.

 

I suspect this caused by SSD hard drive. I think ESET SS 8 does not like SSD.

Edited August 3, 2015 by SMK

[Marcos 5,070]

Let's try disabling automatic start of real-time protection and reboot the computer to see if that makes a difference. If so, re-enable it and reproduce the issue with boot logging enabled in Process monitor (for instructions, see hxxp://www.msigeek.com/6231/how-to-enable-system-boot-time-logging-using-process-monitor-tool).Once you have rebooted the computer and saved the log, compress it, upload it to a safe location and pm me the download link.

[MikeD 0]

I believe this is a wider issue as on upgrading to Windows 10 I have found that numerous processes fail to start amongst them the Eset Remote Administrator Server of v5. However...

 

The list of failed services includes Net Pipe and SQL Server so, whilst it is something that needs to be addressed from a security perspective, I do not believe it is a problem within Eset that is causing the issue

[MikeD 0]

After further work on this I found that several pieces of software that I had installed before the upgrade to Win 10 were not compatible but I was not warned during the upgrade.

 

I have now removed SQL Server 2008 R2 and replaced it with SQL Server 2012 (and also removed several other packages which I no longer need or use) and set some of the problem processes to "Delayed Start" (not eset). The PC is now booting ok and all processes start ok

[SMK 0]

Windows 10 upgrade software (Get Windows 10) tells you if you have some software it does not support.

I have SQL Server 2014 Express on my machine since before upgrading to Windows 10, on Windows 8.1. And still there and working fine.

 

ESET Smart Security 8 supports windows 10. Moreover, I removed it from Windows 8.1 before upgrading to Windows 10. Then re-installed it on Windows 10. In both Windows Systems (8.1 and 10) I faced the same issues.

 

But I think that this is normal during software development cycle if you are a developer as I guess because you SQL Server. Knowing that ESET SS 8 and NOD32 works fine and smoothly except in Shut down and Sleep modes, which sometimes the system does not respond. Also, it makes the system a little slow on both Startup and Shut down.

[SMK 0]

Let's try disabling automatic start of real-time protection and reboot the computer to see if that makes a difference. If so, re-enable it and reproduce the issue with boot logging enabled in Process monitor (for instructions, see hxxp://www.msigeek.com/6231/how-to-enable-system-boot-time-logging-using-process-monitor-tool).Once you have rebooted the computer and saved the log, compress it, upload it to a safe location and pm me the download link.

I have downloaded the Process Monitor software in the link you sent, but, when I click on Enable Boot Logging menu item, an error message appears saying “Unable to write PROCMON23.SYS. Make sure that you have permission to write to the %%SystemRoot%%\System32\Driver directory.” Therefore, I could not complete the other steps.

 

I put the “Procmon.exe” in the mentioned directory but the same message appeared. In addition, I tried to disable ESET SS 8 temporarily.

Knowing that always I run it as Administrator from R-Click context menu.

 

I have SQL Server 2014 Express Edition installed on my computer. I do not know if this makes the issues because I think ESET SS uses SQL Server as data storage.

[DinGo 22]

I had the same problems as you when trying to set up Process Monitor for Boot Logging SMK.

 

I tried to take Ownership of Driver directory to get around the problem but it was having none of it.

 

Any ideas Marcos?

Edited August 5, 2015 by DinGo

[SMK 0]

I think this is because of Windows 10 Security. May be we have to change some configuration or we have to have newer version of the Process Monitor software. I am waiting for Marcos to replay what to do.

[SMK 0]

But I think your problem will be solved if you stopped startup scan in schedule tasks if there is a little bit delay (such as  5 to 10 seconds more than usual). I think this causes the delay and it is normal. Moreover, the startup scan is not important if your computer is clean. just run the smart scan for first time when you installed NOD32 and real-time protection manages the rest of time.

 

But my issue on computer Shut down and Sleep, the delay is remarkably for a long time (measured in minutes) and sometimes It does not respond on sleep mode and I have to shut down my computer by pushing the power button for 5 seconds. this happens some times not always. knowing that my system's hard disk is SSD which should be much more faster in startup and shut down.

[dom1da 10]

this is how i resolved this issue removed nod32 completely and used the eset uninstall tool as well in safe mode

then downloaded the latest version 8 installer and that seamed to do it for me

 

i have a Seagate Momentus® XT SSHD hybrid drive  2.5" 1 TB (5400rpm) + 8GB SSD in my laptop a Lenovo G50-70

and i am running Windows 10 pro 64bit

 

hope this helps

Edited August 6, 2015 by dom1da

[SMK 0]

Last time when I shut down my computer was around 6 AM. The computer screen turned off but the power and HDD (SSD) drive LEDs was still lighting until around 2 PM. Therefore, I pressed the power button for seconds to turn off my computer improperly.

 

I think ESET is one of best computer security systems. However, for now, I have to uninstall the trial version from my computer and I shall use Windows Defender with Windows Firewall instead. I shall wait to the next release or version of ESET because this power-off may by crash my computer system and I have many works to do.

 

I cannot complete the test. Please, accept my apologize.