Windows 10: Slow boot time on SSD (during OS loading screen)

In your boot trace Your desktop is shown after 15s !

For me it's a correct boot time.

 

Ok,

here is the boot trace.

The benchmark and S.M.A.R.T. info here





Also zinou it is not correct. It doesn't show after 15 secs. Look at that post boot event that takes 35 seconds. That is it! The culprit! But I don't know how to find what exactly it is. I know it is because in my event viewer it also says post boot 35 seconds and it is the longest value there. Does it mean my POST is taking too long? Or is it post windows boot? Like after windows booted

 

The post boot phase occurs after the explorer is loaded (so session opened and desktop shown).
This phase consist of running services marked as auto-delayed and other scheduled taskes...etc.

it can be improved though...

 

Ok so I uploaded a video so you can see it takes over 15 secs. Over a minute. Keep notice on the power button it is also the HDD indicator, as soon as it starts being red again, the OS loads in 2,3 seconds. Just how it was before, when I didn't have that stupid delay.
20180101_120734 - Video Dailymotion

 

The sppsvc (Microsoft Software Protection Platform) is using a lot of CPU overtime !

Disable this service and see if there is any improvement (See Methode 3) How to Fix High CPU Usage by Sppsvc.exe on Windows 10?

 

I disabled it and it is a bit faster, a few seconds, but nowhere near where it was. Also I don't see it in task manager anymore so it's not malware

 

Can you take another boot trace. The first one doesn't really reflect what I've seen in the video.
Question: are you using fast startup ?

 

Ok so I made a new trace.

I typed : "wpr -disablepagingexecutive on" into an elevated command prompt.

The settings I used




Also fast boot and hibernate are both off. The file is here

 

Unfortunately it doesn't look like the delay got captured in the trace. You see that you get to post-boot phase after ~15 seconds.

So that means that either you didn't hit the issue on this boot or the delay is so early in the boot process that it's not getting logged.

 

I had the issue for sure. So if it isn't logged do you think it is down to bios level? It was the same in the performance report I posted earlier. You can see the issue in the video I posted. It's so strange it logs only 15 seconds when it takes a lot more..

 

The tracing starts in the pre-session phase, which is when the kernel is getting loaded. So it's down to the BIOS or early Windows boot phases.

Do you see this issue in safe mode?

 

Yes it is present in safe mode too

 

Can you redo the video showing just the screen. Moving the camera gives us zero idea what is going on. Check your startup items in Task Manager and see what else is loading. 15 seconds is not a lot, unless you also have it rebuilding the Page, Hibernate, have Delay Boot to 0 or grayed out in msconfig. Do not disable Write Caching, etc., that some people state improves things, but disabling certain cache with a SSD will actually slow it down.

 

So what things should I look into if it's BIOS level? Also @bro67 if the camera was on the screen the whole time you would just see the spinning circle for a minute or so, BIOS is done loading in a few seconds. I am kinda lost, I feel this is a Windows bug =/

 

You used to be able to view the drivers being loaded during boot on the screen but it looks like that no longer works, at least on my system. Can you give it a try just in case? In MSCONFIG:





If you don't see anything on the screen then you can look at the boot log file in \Windows\ntbtlog.txt and see if there's any error messages. The log is concatenated on every boot so another thing you can try is:
1. Enable MSCONFIG settings as above.
2. Delete any existing \Windows\ntbtlog.txt file.
3. Reboot system. Keep track of the time when BIOS starts booting and when you see the spinning wheel.
4. While system is stuck during boot, press the reset button or forcibly power off the system.
5. Boot up the system normally and check the log to see what was the last driver loaded before you pressed the reset button on the previous boot.

You can post the log file somewhere. This will tell us if Windows is stuck loading a driver.