booting windows 10 spends too long

Question

In august 2015, I have upgrade my laptop from windows 8.1 to windows 10. But it spends always 10 minutes to boot it. It is not normal that it spends so long. What can I do for boot him faster? Below some information about my laptop.

age: ⁺/_- 2 year (on august 2015)
edition: Windows 10 Home

^{File trace are removed.}

Update:

I must also say that always there comes a windows update, I have the same problem again form slow booting. Is it good that I turn off the updates? If yes, how can I do that?
Also it is in periods that my pc booting to slow. Some time it is like normal (a few seconds) and other times a few minutes. I don't know how it comes that it is fast or slow.

use the Win10 SDK/WPT (https://dev.windows.com/en-us/downloads/windows-10-sdk) and run this command to do a boot trace: http://pastebin.com/CYGqRZXE and share the compressed file. — magicandre1981, Sep 07 '15 at 16:17
@magicandre1981: I have uploaded a boot trace. Can you inspect it please? — H. Pauwelyn, Sep 22 '15 at 13:11
Some have said check if the SATA Mode is set to AHCI instead of IDE. — Noumenon, Oct 19 '15 at 15:59
If the prefetcher is broken you could try turning on Superfetch in msconfig. — Noumenon, Oct 19 '15 at 16:34
@kokbira: that's impossible long :), no it is the age of my pc. — H. Pauwelyn, Dec 18 '15 at 09:45

magicandre1981 · Accepted Answer · 2017-04-26T15:03:31.087

13

To see why Windows boots slowly you need to install the Windows Performance Toolkit, which is part of the Windows 10 SDK.

^{(all other entries can be unselected)}

Run WPRUI.exe, select First Level, CPU Usage, DiskIO, FileIO and under Performance Scenario select Boot. Number of iteration can be set to 1 and click to start.

This reboots Windows and captures all activity during boot. After the reboot let the countdown tick to 0.

Now make a double click on the generated ETL file to open the ETL in Windows Performance Analyzer (WPA.exe), click on Profiles->Apply->Browse Catalog and select the file FullBoot.Boot.wpaprofile you see this overview:

and see that the longest delay happens during the WinlogonInit phase. This takes 197 seconds to finish.

The WinLogonInit subphase begins when SMSSInit completes and starts Winlogon.exe. During WinLogonInit, the user logon screen appears, the service control manager starts services, and Group Policy scripts run. WinLogonInit ends when the Explorer process starts.

Visual Cues WinLogonInit begins shortly before the logon screen appears. It ends just before the desktop appears for the first time.

WinLogonInit Performance Vulnerabilities

Many operations occur in parallel during WinLogonInit. On many systems, this subphase is CPU bound and has large I/O demands. Good citizenship from the services that start in this phase is critical for optimized boot times. Services can declare dependencies or use load order groups to ensure that they start in a specific order. Windows processes load order groups in serial order. Service initialization delays in an early load order group block subsequent load order groups and can possibly block the boot process .

When I look at the disk IO table, I see that the slow Samsung HDD (SAMSUNG Spinpoint M8) is very busy. I can also see that the prefetcher ReadyBoost is not working, it only generates "misses". This causes slowdowns to starting services like the lmhosts which takes 129s to start.

As a workaround you can improve boot performance by running this command:

xbootmgr -trace boot -prepSystem -verboseReadyBoot

this reboots Windows several times, does a defrag and trains the prefetcher again. But to fully speedup boot, replace the 5400rpm HDD with a SSD.

edited Apr 26 '17 at 15:03

answered Sep 22 '15 at 16:00

magicandre1981

98,168
30
181
248

Your solution works very good, but there was a windows update and I have again the same problem again. I have run your command (xbootmgr -trace boot -prepSystem -verboseReadyBoot) in the command line but it didn't help. Can you help me? Later today I go upload a new etl file that you can use. – H. Pauwelyn Sep 28 '15 at 07:43
I need the new ETL file to see more details. – magicandre1981 Sep 28 '15 at 15:52
Sorry that I have it later than I have said, but the new etl file is uploaded. I have also added some more information about my problem. – H. Pauwelyn Oct 04 '15 at 08:27
1

same as before. The prefetcher is broken and the HDD is busy all the time. the optimization is only a workaround. Replace the HDD with a faster SSD. – magicandre1981 Oct 04 '15 at 14:53
It's still going to take three minutes to boot with an SSD, something still isn't right. – Noumenon Oct 19 '15 at 11:52
@Noumenon share a boot trace – magicandre1981 Oct 19 '15 at 15:52
I'm not the OP, I'm just saying the normal boot time is under 20 seconds so even if his hardware is 1/3 the speed of an SSD that's not his only problem. – Noumenon Oct 19 '15 at 15:58
@Noumenon no, his bottleneck is the disk – magicandre1981 Oct 19 '15 at 16:01
1

TIL SSDs are 3x as fast only for large sequential access. They're up to 50x as fast for small random access. So I believe you now. – Noumenon Oct 19 '15 at 16:33
@magicandre1981: I have executed the command (xbootmgr -trace boot -prepSystem -verboseReadyBoot) but the problem is now every time I startup my PC, the performance analyzer starts also. How can I stop that? For this moment I use every time the task manager for force it to exit, but it is not fine. Please can you help me again? – H. Pauwelyn Nov 01 '15 at 08:59
2

did Windows finish all 6 steps? if yes, run xbootmgr -remove to stop it – magicandre1981 Nov 01 '15 at 18:24
5400rpm drives: I can see the problem. – music2myear Dec 13 '16 at 17:51
1

ETL? WPA? Please expand your acronyms so that we all may understand your answer. – Lightness Races in Orbit Apr 25 '17 at 00:58
@BoundaryImposition WPA.exe = Windows Performace Analyzer. ETL = Event Tracing for Windows Logfile – magicandre1981 Apr 25 '17 at 04:19
1

@magicandre1981: I mean, in the answer. – Lightness Races in Orbit Apr 25 '17 at 09:01
@BoundaryImposition when you follow the steps from my comment you get a ETL file after Windows is booted. Here double click on the generated ETL file and open it in WPA.exe. Now you see the GUI and can apply the profile to see the same graphs like in the pictures. – magicandre1981 Apr 25 '17 at 15:44
Yes, @magicandre1981, I am asking you to incorporate this information into your answer. Comments are transient. – Lightness Races in Orbit Apr 25 '17 at 18:33
I added it and with the newer way via GUI, so it is easier for beginners like you. – magicandre1981 Apr 26 '17 at 15:04
@magicandre1981 the info about "xbootmgr -remove" should go into the answer, it is important... – FarO May 10 '17 at 16:14
@OlafM this is normally not required. This is only needed if you got an error and want to interrupt the tracing. – magicandre1981 May 11 '17 at 16:15
Is this method able to trace the full Kernel Phase of the boot up process? – Adam L. S. Jun 06 '20 at 20:28
@AdamL.S. What do you mean? – magicandre1981 Jun 07 '20 at 13:23
Is it possible to configure the tool for the trace file to detail the actions taken and for how long in the Kernel Phase, or would it always reports if a report exists at all that "I was in the Kernel Phase"? – Adam L. S. Jun 12 '20 at 23:07
@AdamL.S. it will show the time it takes to load drivers if you need this (look at picture it shows PreSessionInt, SessionInit) – magicandre1981 Jun 13 '20 at 10:52

KARTHIK M S · Answer 2 · 2022-09-18T07:49:52.533

This is where I found the solution.

https://answers.microsoft.com/en-us/windows/forum/all/windows-10-boot-times-slow-after-latest-update/36584441-ff4a-4ffa-b560-3db87019ea44

I too had similar issue, not though due to update from windows 8 but in the windows 10 itself (could be due to update). I have SSD, still it took 9 minutes to start fully and booting before welcome screen was 95% of it. I tried the above solution using windows performance tool kit but it never crossed run 2 out of 6, however long I waited. Finally what worked was windows upgrade option (not update). With this you don't have to install all apps again or take backup of files. It is very easy. Now it takes total of 42s with 12s for boot time before welcome screen.

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center. — Community, Sep 17 '22 at 01:39

booting windows 10 spends too long

2 Answers2

Linked

Related