Windows 10: Startup takes too long at Winlogon Init

My laptop with Windows 10 1909 used to show desktop immediately after typing in the password. Recently after doing updates, it takes about 25 seconds to get to desktop after entering password. Laptop is using NVME drive. I have traced the boot using WPR and couldn't figure out what is wrong. Really appreciate any help.
Trace: Dropbox - boot trace.zip - Simplify your life

:)

 

Slow Boot Windows 10. Session Init and Winlogon Init times are high.

Hi,

I am experiencing slow boot on windows 10. The boot time was close to 200 seconds initially when i started diagnosing it. Now, after reading few posts here, i have manged to reduce it to 82 seconds. Thanks Zinou!

I followed this post and executed the xbootmgr -trace boot -prepSystem -verboseReadyBoot command. (High CPU when first starting the laptop). This brought down my boot time from 200 seconds to 82 seconds.

Can this boot time be reduced further? I still see high boot time in Session Init and Winlogon Init.

My config:
Dell Inspiron 5770
Intel i7 8550U
1 TB HDD
AMD Raedon 530

Before xbootmgr CMD:




After xbootmgr CMD:




Trace of boot 6:
Download - TransferNow

Please have a look. Thanks

 

Can't get GPU-Z to start with Windows 8.1 startup

I'm not sure how to do that. Could you list the steps for a noob?

 

Windows 10 takes a LONG time to login

A couple weeks ago, my Windows 10 computer started taking a LONG time to login. The times have been going up and down, with a max of about 15.5 minutes, which happened today. Here's what I've tried to solve this issue:

1. Do a clean boot (no startup programs or services other than Microsoft services).
2. Defrag/optimize hard drive (not SSD).
3. Run CCleaner and Malwarebytes.
4. Check the Event Viewer.

Here I found multiple warnings and errors:

1. Event 6005, The winlogon notification subscriber <Profiles> is taking long time to handle the notification event (Logon).
2. Event 7022, The Connected Devices Platform Service service hung on starting. (and a few like it, only with different services)
3. Event 6006, The winlogon notification subscriber <Profiles> took 936 second(s) to handle the notification event (Logon).
4. Event 6004, The winlogon notification subscriber <GPClient> failed a critical notification event.
5. Event 6001, The winlogon notification subscriber <Sens> failed a notification event.

After some googling, I continued with the following steps:

5. Disable "Always wait for the network at computer startup and logon" and "Run logon scripts synchronously" in the Group Policy Editor.
6. Do an in-place upgrade/repair.

There are probably some other steps I've missed, but I think that covers most of it. I'm fed up with this problem, but I really don't want to have to reinstall Windows. If anyone has any solutions or ideas, I'm open to anything at this point.

Thanks in advance!