Windows 10 slow logon preparing windows - Microsoft Q&A (2025)

2021-06-14T12:31:51.793+00:00

Hi everyone,

I know this issue is around for quite some time. But, from what I experienced in my testing, whatever I tried didn't exactly help.
Here is what my problem: A domain user logs into a domain computer. policy applies within 10-15 seconds which is good because we deploy preferences like drive maps, printers, file and folder options and internet settings. after applying the policies the display shows "Please wait for the local session manager" for a second or two and than we get the "Preparing Windows" message for 30 seconds.
I tried configuring the following:

1. Disabled logon script delay
2. Disabled run logon script synchronously
3. Added the DelayedDesktopSwitchTimeout DWORD registry and set the value to 0

Although the logon time got shortened I still get a black screen for 10 seconds or more which could alert the users.

Our active directory is 2016 but our domain functional level is 2008 r2 because of historic reasons.
our windows 10 are 1909 and above.

Don't know where else to turn to for help.

Rahamim.

Sign in to comment

1. 

   Anonymous

   2021-06-14T12:43:26.627+00:00

   Please run;

   Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txt
ipconfig /all > C:\dc2.txt
ipconfig /all > C:\problemworkstation.txt

   then put unzipped text files up on OneDrive and share a link.

   1. 

      Rahamim Levi 156Reputation points

      2021-06-14T13:52:03.63+00:00

      Thanks @Anonymous

      Here is the link: Ejj7fMpAYIdEi40KGFq8-EsBvMZtEqAgKbwTmiFNUedgsA

      Rahamim

   Sign in to comment

2. 

   Anonymous

   2021-06-14T17:54:17.453+00:00

   Looks like there may be some replication and KCC problems. You'll need to check the event logs for more details. Also if the 192.168.x.x addresses are not domain controllers then remove them from DNS.

   --please don't forget to upvote and Accept as answer if the reply is helpful--

   1. 

      Rahamim Levi 156Reputation points

      2021-06-14T18:53:01.237+00:00

      Thanks @Anonymous

      The 192.168.x.x are addresses of domain controllers on a different AD site.
      Also, I use the Active Directory Replication Status tool and it didn't report any replication issues.

      Can you explain please how replication and KCC problems affect the preparing windows issue?

      Rahamim.

   2. 

      Anonymous

      2021-06-14T18:55:13.41+00:00

      I was just reporting the issues I noted. The event logs should have more details.

      --please don't forget to upvote and Accept as answer if the reply is helpful--

   Sign in to comment

   See Also

   The ultimate guide to Windows logon time optimizations, part #11

3. 

   Vicky Wang 2,721Reputation points

   2021-06-21T08:17:22.03+00:00

   Hi,
   Just checking in to see if the information provided was helpful.
   Please let us know if you would like further assistance.
   Best Regards,
   Vicky

   1. 

      Rahamim Levi 156Reputation points

      2021-06-23T10:47:28.153+00:00

      Hi @Vicky Wang the information was not helpful in my case since I don't understand what happens during the "Please wait" stage.
      If someone can tell me what happens and how does it relate to active directory, I would be more than happy to check the issues that are coming from the KCC and replication that @Anonymous mentioned.

      Rahamim.

   2. 

      Anonymous

      2021-06-23T11:22:08.25+00:00

      Still waiting for the files.

   3. 

      Rahamim Levi 156Reputation points

      2021-06-29T07:08:51.82+00:00

      Hi @Anonymous and sorry for the delayed response.
      I have already sent you the files and you told me there was an issue with KCC and replication.
      I still don't understand the why replication and KCC issues are related to the "Please wait" message when a user logs in.
      If you need any more details please let me know.

      Rahamim.

   Sign in to comment

4. 

   Anonymous

   2021-06-29T10:58:04.763+00:00

   I have already sent you the files and you told me there was an issue with KCC and replication.

   Sorry, yes you did (buried in the threading)

   The event logs should have more details.

   --please don't forget to upvote and Accept as answer if the reply is helpful--

   1. 

      Rahamim Levi 156Reputation points

      2021-07-01T09:34:16.087+00:00

      @Anonymous I have run DCDIAG multiple times to check any issues.
      I did find a stale DC record which I removed since that DC was no longer active. Other issues are related to the backups being run on the servers. we have two systems that run backups on a daily basis and when the backup runs the server gets notified. That is why we have those DFS Replication errors.
      I also saw an alert about failing to delete the dcdiag DNS record which I believe is something I can ignore.
      The last thing I saw was schannel errors. I know where they originate from, but still, I can't see why this is related to my issue.

      I would appreciate it if someone knows what happens during the "Please wait" stage of the login.

      Rahamim,

   2. 

      Anonymous

      2021-07-01T11:34:42.637+00:00

      Sounds good, I'd still check event logs for more more details.

   Sign in to comment

Sign in to answer