keyboards Posted February 15, 2021 Posted February 15, 2021 We've come in today and loads of machines are taking ages at the please wait bit for at least 10-20 seconds, normally it's instant, any ideas? Driving us a bit nuts
Michael Posted February 15, 2021 Posted February 15, 2021 I've seen this happen with January and February 2021 updates.
Davit2005 Posted February 15, 2021 Posted February 15, 2021 (edited) Issues with a Domain controller?? Have you more than one DC, compare a few clients that work OK and some that don't. At the run box after logging into domain and type %netlogon% and see what DC you have authenticated against. Mind you 10secs is nothing I've seen issues with DC cause 10mins of delay. You could also test logging in under safe mode with networking. Does it happen on same clients after initial delay? Edited February 15, 2021 by Davit2005
jthompson Posted February 15, 2021 Posted February 15, 2021 Do you have the verbose startup messages on? Those replace the generic 'Please wait' with whatever the machine is up to prior to reaching the login screen. Often that would be applying certain types of policies, completing updates or installing a deployed application.
keyboards Posted February 15, 2021 Author Posted February 15, 2021 Cheers guys, think might have solved it, we replaced printers last week and I think it might've still been looking for the old printers via GPO and scripts, so was just going round in circles then eventually just going no, can't find it.
Sheridan Posted February 15, 2021 Posted February 15, 2021 I've seen this happen with updates, software install, AV updates and issues as well as just sheer randomness with W10. Can you connect to the PCs event viewer when its in this state?
jthompson Posted February 16, 2021 Posted February 16, 2021 Yeah, I've seen dead printer connections hold up Windows like that before. For a lot longer that 10-0 seconds, though.
Michael Posted February 16, 2021 Posted February 16, 2021 I should add that once the January/February 2021 patches are applied, the startup sequence then returns to normal.
keyboards Posted February 17, 2021 Author Posted February 17, 2021 Worked this out in the end, on the DC a process was running at 99% of a four cpu four socket vm, killed the process then we went back to lovely quick times
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now