Windows 10: Slow boot on Win10 compared to Win7

I noticed one thing: when windows loads, it loads some services, usually network, Kaspersky, sound and all that basic stuff, then pauses for about 20sec, at which point the rest loads. It also the point where my external USB devices light up. They become dark when profile loading starts, and then light up at the end of the boot. I can't remember W7 doing that - anything known about that?

 

If you look under the services window, you will see several services that are designated as "Delayed Start" and "Trigger Start". These services that load after a delay.

 

Clean install of W10 on my desktop pc. Windows 7 (I missed out the 8s) was always pretty fast but 10 is dead slow. I get the Asus Screen then the post sound then the black screen with the blue window graphic and the circle of dots. After about 12 secs I get the blue metro menu (I have Macrium as second choice) then i get a black screen for about 10 secs then the logon (pin) screen. After I enter my pin I get the circle of dots for about 8 to 10 secs before the desktop appears.

Drivers are up to date.

Samsung 850 Evo and 16 gb ram.

 

do we have anyone on this forum actually trained in Windows 10? [serious question, not a dig] - I have no idea what to do with the MMC/Eventlogs/Applications&Services/Windows/Operational info. If someone could help decode we might make progress in helping one another out. image below:




as best I can tell most if not all of these errors are internal to windows: windows services that for a variety of reasons miss timing thresholds and get tagged

 

I am far from an expert on Windows, but here is some information that can help.


Event ID 100 is essentially a list of time taken by specific steps during the boot process. Expanding that particular warning and comparing the Windows between different occasions off ID 100 will help you identify steps that are causing delays.
Event ID 101 –10x refer to specifically outlined events/processes etc. that have caused unexpected boot delays. These warnings pretty much always point to a particular program.
Event ID 200 is the warning related to shut down processes. Very similar to event ID 100, comparison of different occurrences of event ID 200 can help highlight areas of delay.
Event ID 201 –20x are very similar to the event ID 101 – 10x and help pinpoint specific system delays.


Event IDs 100 Generally tend to occur when the boot process exceeds 20 seconds. Once they disappear you have achieved Boot nirvana. Most of the time they will be present. Don't be surprised if over time, as Windows tunes itself, these lags/delays will tend to disappear with no effort on your part.


The number off 100 – 200 errors showing on your post are not excessive however expanding each of these warnings will give a lot more information regarding the length of delays associated with them. Try posting your last batch of errors in the expanded format.

 

What I noticed right now: I did a cold boot - I mean I turned off the computer at 23:00 and then turned it on now, at 03:00. The boot was lightning fast, just like it ever was in W7. From first sign of W10 sign until ready desktop probably around 15 seconds.

Why did that happen? The common messages that usually appear in Eventlog were not there, however I did get:

Faulting application name: ShellExperienceHost.exe, version: 10.0.10525.0, time stamp: 0x55cc09c6
Faulting module name: StartUI.dll, version: 10.0.10525.0, time stamp: 0x55cc0217

and
A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect.
and
The Steam Client Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

But the computer started really fast.

Is there any difference between "restart" and "shutdown" in W10?

 

Is there any difference between "restart" and "shutdown" in W10?





"Fast Startup (aka: hybrid boot or hybrid Shutdown) is a new feature in Windows 8 to help your PC start up faster after shutting down. When turned on, Windows 8 does this by using a hybrid shutdown (a partial hibernate) method that saves only the kernal session and device drivers (system information) to the hibernate (hiberfil.sys) file on disk instead of closing it when you shut down your PC. This also makes the hiberfil.sys file to be much smaller than what hibernate would use (often 4GB or more). When you start your PC again, Windows 8 uses that saved system information to resume your system instead of having to do a cold boot to fully restart it. Using this technique with boot gives a significant advantage for boot times, since reading the hiberfile in and reinitializing drivers is much faster on most systems (30-70% faster on most systems tested). If you have a motherboard with UEFI, then fast startup will be even faster."

I know SSD space conscious individuals who turn off fast start up and delete hiberfil to save upto 10GB or more on Win 8.1. It appears to be less on 10 approx 6GB.

 

Funny how you posted that, I just turned off hiberfil.sys and pagefile.sys to test the reboots.
I can safely say that both cold boot and reboot are faster now.

The thing with UEFI though: I have the UEFI, but never really saw to it - meaning I don't know if it's working as it should. I even think I installed Windows not through UEFI but like I ever installed Windows 7 - I pressed F8 at BIOS, got my screen to select boot device, and usually there I have two options: Stick-Boot as usual, and UEFI-Stick-Boot - I went for usual, not UEFI.

In any case, turning off those two files, and I have 8GB RAM, the reboots are now quite OK - not delayed like they were. Maybe they could be even faster than W7, but right now, there is some kind of a bug in there.

 

Well, I think it's safe to say I got my boot-performance back:
- powercfg -h off
- HiberbootEnabled = 0 under HKLM\SYSTEM\CCS\Control\Session Manager\Power

 

anyone know how to actually ACT upon the System Diagnostic logs regarding Boot and Shutdown performance [non-performance]? *.evtx event logs?
I would attach if I could, but I'm sure everyone on this thread has such whether you know it or not: Mgmt-Console/SystemTools/EventViewer/Applications&Services/Microsoft/Windows/Diagnostics-Performance/Operational

 

Hahaha this is a funny result: previously my boots took way longer than they do now (yes, I did the stopwatch thing) - until I had my main programs loaded. I consider main programs stuff like Teamviewer, Input Director, Logitech Program and my shares. However, the Diagnostics Performance says my boots are taking twice as long as before.
Sometimes it's really funny how Windows "thinks". And so much about "let Windows manage".

It says my boots are now taking 96 seconds (which is an utter nonsense), and before, they were pausing at least 20 seconds at the login screen, and it said previously my boot was 45 seconds.

So, there is no act here. There is only nonsense.