Boot time analyzer for Win10?

Topic

New Reply

Looking for a program that will help me identify why Win10 now takes 60s to boot up… Any ideas?

Reply | Quote

Replies

What version of Win10 are you running? 1809, 1903, 1909, 2004? Home or Pro?

Reply | Quote

You could start by checking your msconfig for startup apps/programs (or Sysinternals autoruns) ensure faststart is switched off, adjust performance settings for quicker rendering, set services to manual for apps you do not use, just to start with.

edit: on a quick search found bootracer (free)
Note: Have no experience on this program, although there is an edition for W10.

Windows - commercial by definition and now function...

Reply | Quote

Microfix wrote:

ensure faststart is switched off

That makes booting slower.

Reply | Quote

Agreed, but easier to troubleshoot things now, as well as boot-time could also be misinterpreted on analyisis for this topic issue.

Fast start can be switched back on once bootime issues have been resolved, should the OP wish to do so.

Windows - commercial by definition and now function...

1 user thanked author for this post.

b

Reply | Quote

GC wrote:

Looking for a program that will help me identify why Win10 now takes 60s to boot up… Any ideas?

Have you tried TechNet/Sysinternals’ free, portable Process Monitor (ProcMon)? It’s a little complicated to interpret results but includes boot logging as an option, including event timers.

Very generally:

1. If it’s the first time you’ve used ProcMon, make sure you run it using Run as administrator, accept UAC and the EULA (which only appears the first time you use ProcMon) and, when the ProcMon window appears, quickly use CTRL+e to stop capturing events then CTRL+x to clear the display.

2. In the Options menu, choose Select Columns and tick ‘Date &Time‘, ‘Duration‘ and ‘Completion Time‘.

3. Consider removing the tick from ‘Time of Day‘ (The fractional seconds are very granular and often difficult to interpret. IMO you probably only need the full seconds shown by ‘Date &Time‘ when you’re trying to work out a boot delay.).

4. Move the timing columns to the left to make them easier to view.

5. Still in the Options menu, choose ‘Enable Boot Logging‘; DON’T tick the checkbox… just click on the OK button.

6. Close ProcMon (and any open Explorer windows) and shut down.

7. Restart your device.

That’s it, basically. When your device restarts, it will load ProcMon very early in the system process and begin logging events (like drivers loading, etc.) well before the user process (Sign in…) begins.

8. After you sign in, run ProcMon again. You’ll see the following dialog:

9. Click the Yes button and save it. (I tend to save the log to the desktop for convenience.) Note that it can take quite some time for the data to be written to the log…

… then filtered…

… before being displayed in ProcMon.

I suggest you pay particular attention to the Duration and Result columns. Duration is obvious, i.e. shows how long each event takes. Result is very useful though. For example, deselect the category filters (the 5 right-most icons in the toolbar) so only Show File System Activity is active. It’s then much easier to spot failures caused by missing/corrupt files or locked files… which leads to retries and thus delays.

For a useful summary, click on the Tools menu and choose Process Activity Summary. Again, it will take a while for the large amount of boot log data to be analyzed before display.

You’ll see a huge number of svchost.exe events but, if you click on each event, you can see what actual commands are being hosted by the service manager. You can also click on any of the column headings to re-order the lists. Double-click on any process and you’ll see a breakdown of the summary categories.

PS – Note that Boot logging is only carried out once. If you want another boot log then you’ll need to enable it again.

Hope this helps…

1 user thanked author for this post.

RetiredGeek

Reply | Quote

I forgot to mention… ProcMon’s saved bootlog files are BIG and it’s common for several to be created, each one several hundreds of MB!

Reply | Quote