UserofEset 0 Posted November 23, 2015 Share Posted November 23, 2015 We have updated some clients to Endpoint 6 and some of our users are noticing a much longer startup time. I have tested the startup scan with the Scan Level=Files Run After User Logon and Scan Priority=When Idle and it doesn't seem to make a difference. My 2 part question is: What is the best way to isolate the actual duration of the Startup Scan and what is a typical acceptable duration for the whole process to complete. Any feedback is appreciated. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted November 23, 2015 Administrators Share Posted November 23, 2015 A startup scan should be completed within a blink of an eye, definitely not dozens of seconds if LiveGrid and Smart optimization is enabled. Does temporarily disabling both startup scan tasks actually make a difference? Link to comment Share on other sites More sharing options...
UserofEset 0 Posted November 24, 2015 Author Share Posted November 24, 2015 The disabling of the Startup Scans doesn't seem to impact the machine. If Endpoint is removed the boot time decreases by about 1:30 so startup 2:30 as opposed to 4:00. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,074 Posted November 24, 2015 Administrators Share Posted November 24, 2015 What about temporarily disabling automatic start of real-time protection? If disabling it helps, re-renable it and use Process monitor to create a boot log (https://www.msigeek.com/6231/how-to-enable-system-boot-time-logging-using-process-monitor-tool, step 1-5). When done, compress it, upload it to a safe location and pm me the download link. Link to comment Share on other sites More sharing options...
Recommended Posts