Hi all
I fully concur with dalchina’s comment below.
So let’s focus this thread on possible providing a SYSTEMATIC step by step procedure to troubleshoot performance issues, esp. during startup.
I.e. provide a systematic method to troubleshoot slowness by pinpointing possible performance culprits/bottlenecks.
I have not tried windows performance analyzer yet, however I don't see how to use this for startup issues?
br
Peter
Initially I understood the period in question was the boot time. Actually it's the time to stable desktop- after login, and to when the task manager shows little resource usage, if I now understand correctly.
Therefore I recommended the WPA. Whilst it could be used to analyse activity in a time period, I would now suggest the first thing to do - if it's not been suggested already- is to compare the time from login to 'desktop' for
a. normal boot
b. clean boot
If that shows no significant difference, then further startups could be disabled using Autoruns (free from MS).
However, the analytical approach may still be needed- using the WPA is non-trivial. Here's a guide I've just foudn for someone else who said they didn't know where to start:
https://docs.microsoft.com/en-us/win...-by-step-guide
Not that I'm saying it's easy- there's quite a learning curve. Example threads and screenshots can be found on tenforums.
Hi Peter,
If you discover booting to Safe Mode or a Clean Boot is much faster than a regular boot, the next best test is Autoruns.
https://docs.microsoft.com/en-us/sys...loads/autoruns
This video tutorial will assist in how to use Autoruns to analyze startup delays.
Advanced Autoruns Tutorial - How to disable programs that start with Windows - YouTube
Windows Performance Analyzer is the end-all definitive answer to solving startup issues, unfortunately, it can be difficult to interpret the results unless @zinou is your guide.
Win10 Slow boot time. Help debug with Windows Performance Analyzer
Last edited by W10 Tweaker; 29 Apr 2021 at 06:43.
Hi
I have now checked autoruns on the windows10 PC.
How do I see performance impact of entries, i.e. how do you identify entries which could safely be disabled?
So far I did not find this in the tutorial.
Br Peter
Screenshots from autoruns
Everything
Logon (1 of 1)
Services (1 of 2)
Services (2 of 2)
Last edited by plaurits; 29 Apr 2021 at 12:14.
Hi Peter, I apologize if I wasn't clear in my earlier post. As mentioned before by others, a Clean Boot would be the next step and before using AutoRuns.
There's little point to making this process more challenging by using complex tools if we can correct the behavior with simple tests. Likewise, WPA is the end-all and most definitive testing app available for Windows performance issues but knowing how to utilize the data it generates is close to an art-form like skill.
I get the impression from the AutoRuns logon tab info that there are numerous apps (including Avast) starting after a boot. Measuring boot time with many apps starting is a losing battle hence the directive to uninstall Avast and perform a Clean Boot.
All these apps may be starting on the XP computer but the only way to proof startup time is a clean boot on both machines, then, and only then, is the boot to desktop time comparison valid.
After a Clean boot, run the startup vbs again and post results.
Ok, will try.
One comment: seems that the restart-time.vbs script does not work consistently.
May be I should use bootracer instead?
One thing I would like to suggest is open Control panel and go to Uninstall a program and run through the list to see if there is anything you could uninstall and check that there is nothing unexpected.
It would also be helpful to fill in your hardware specification on your profile.
You`re not counting the time that your W10 motherboard uses to do self checks before booting to windows are you ?
Could you post a link to your W10 board ?
Quote
