Windows 10: Login takes 2.5 minutes with multiple timeout errors

Hi, has anyone any advice for dealing with the following errors which seem to be delaying the login phase (computer boots, and then logs directly into my account).

The UI during that time is largely unresponsive (desktop is missing icons, mouse cursor is a spinning blue wheel only visible on the taskbar).

1 Event 7009: A timeout was reached (30000 milliseconds) while waiting for the HomeGroupProvider service to connect.
2 Event 7009: A timeout was reached (30000 milliseconds) while waiting for the DmEnrollmentSvc service to connect.
3 Event 10005: DCOM got error "1053" attempting to start the service DmEnrollmentSvc with arguments "Unavailable" in order to run the server: Windows.Internal.Management.Enrollment.Enroller
4 Event 7009: A timeout was reached (30000 milliseconds) while waiting for the CDPSvc service to connect.
5 Event 7011: A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.
6 Event 10010: The server Microsoft.Windows.ShellExperienceHost_10.0.16299.15_neutral_neutral_cw5n1h2txyewy!App did not register with DCOM within the required timeout.
7 Event 10010: The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout. (This is "HomeGroup Provider Service" for user WinPC\rob)
8 Event 10010: The server {9C38ED61-D565-4728-AEEE-C80952F0ECDE} did not register with DCOM within the required timeout. (this is "Virtual Disk Service Loader" user System)
9 Event 10010: The server {EA022610-0748-4C24-B229-6C507EBDFDBB} did not register with DCOM within the required timeout. (this is "Setting Sync Task Factory" user WinPC\rob)

I was able to do the fix described elsewhere to fix the Dcom errors 10010/10016 for srunmon and RuntimeBroker which where causing the Start Button / Search field to become unresponsive for a time, however I am unsure what to do about these issues.

Issues 1, 7, 8 & 9 don't appear on every boot. The account is an Administrator account and in the Administrators group.

Issue 7 in dcomcnfg, "HomeGroup Provider Service" has Launch and Activation Permission (Local Launch & Local Activation) set for the Adminstrators group which I'm a member of.

Issue 8 in dcomcnfg, "Virtual Disk Service Loader" has Launch and Activation Permission (Local Launch & Local Activation) set for the System user. (and Administrators and Interactive)

Issue 9 in dcomcnfg, "Setting Sync Task Factory" has Launch and Activation Permission (Local Launch and Local Activation) set for the System user (as well as Administrators and Interactive, and a weird user that is sometimes marked "Account Unknown" and sometimese not S-1-15-3-1024-4013343662-1780.....)

I guess they are maybe a knock on from the earlier timeouts? The others I haven't found how to tackle, and I'd be grateful for advice.

:)

 

windows 10 lockscreen

Try going to Account settings and change from Microsoft Account login to Local Account login and for me, everything then worked as expected - no more 1 minute timeouts

 

Windows 10 blocks my kids login access and no email sent when more time is requested

My kids login is denied, or timeout after a few minutes. This is still a problem when restriction time is not in force or restriction is disabled

 

Hi,

What is you user account type? a local user account, a MS account or an Active directory acount ?

If you're not opening your session with a local account, try to create a local acount, open a session with this account and see if you have the same issue. If not that mean there is a network bind issue !

To do an accurate diagnosis of the problem you have to take a boot trace with Windows Performance Toolkit;

-Download and Install windows Performance Toolkit https://docs.microsoft.com/en-us/win...ed/adk-install . Choose the package corresponding to your Windows version.
-Record a trace using Windows Performance Recorder using these options: JustPaste.it - Share Text & Images the Easy Way
-Compress the resulting file
- Shareit through TransferNowor any other file sharing platform.

I'llanalyze your trace file and give you a feedback.

See you…

 

Cheers Zinou.

It is a MS Account, and not a local account. (Seems like too much hassle to switch over now). It used to log in snappily, but I can't remember when it started being so slow.

I will give it a shot, and then look at doing the boot trace & get back to you.

 

Just to followup, I got to the bottom of this problem. All of the issues where because I had an ExFat partition. (Machine is a dual booting hackintosh, wanted a partition that worked on both OS's)

As soon as I removed that disk, the system booted and fully logged in in around 20 seconds (9 seconds from boot to login process starting). I reconnected the disk, and many of the above errors occurred again & the really long login phase. So I backed up the contents and I've reformatted it as NTFS and the system now boots cleanly*.

* There was 1 error "Crash dump initialization failed!" but I'll google that.

Thank you for your offer of assistance zinou, I'm grateful.