My Dell laptop is taking about 10 seconds to login whereas it use to be much faster. I found a tip about setting the Group Policy Option "Display highly detailed status messages" as shown below. This shows most of the login time is spent on "Preparing Windows". Any tips on where to go from here?
Attachment 247436
You could..
- check your disk
- run chkdsk /scan
- compare login time after a clean boot
- create a new user, log in as that user and compare the login time
History:
What has changed from when the login time used to be shorter?
- updates
- upgrade
- change to installed programs
- sthg else?
Analysis: long winded tech approach- the Windows Performance Analyser (tutorial available, example threads with screenshots mostly centred on boot time analysis).
- run chkdsk /scan - no problems
- compare login time after a clean boot - no change - about 10s
- create a new user, log in as that user and compare the login time - same login time as other users
- What has changed - The laptop has been slow to login for a while. I can't pin point a specific time. The current installation is 3 + years old with many software installations / uninstallations and at least two recoveries from Reflect backups due to various issues
I'm thinking its's time to do a clean install to restore performance.
You could access a lot more startups with Autoruns (free from MS). (Categorised list with check boxes).
Avoid touching anything MS-related, best create a backup before trying. (Can do that with Autoruns).
Of course you're looking for something common to all users.
Autoruns is a great utility I've been using for a while. I did find disabling Classic Shell improved login speed but I want to keep it. Is the newer Open Shell more efficient? I also noted disabling the Classic Shell Logon entry in Autoruns doesn't stop Classic Shell loading at login. You have to deselect "Start automatically for this user" in CS settings to do that.
Just wondering, is file explorer crashing just after you log in?
Have a look at your Reliability History.
This is a characteristic problem with CS that a few have experienced over the years, but is next to impossible to identify. OS or CS- no difference.
Glad you found a way forward. Curious it's not mentioned as an issue by more.
If I look at my setting for that, it's ticked by default.
Did you try Open Shell to see if it makes a difference. Another thread on tenforums mentions the same delay with Classic Shell.
Would only take a few minutes to switch and see.
Quote