• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 125
  • Last Modified:

Long wait times before Ctrl + Alt + Delete Login Screen Appears?

Hello EE, I am trying to narrow down the cause as to why domain joined Windows 7 x64 Ent computers take a very long time to get to the Ctrl + Alt + Delete login screen?

Scenario, remote users off the domain power on their laptops and it can take anywhere from 5 minutes upwards of 30 minutes for them to reach the login screen.

The one variable I have found to work past these long wait times is to disable the wireless adapter either hardware switch of FN hotkey and it will resolve this issue.

Another variable I have noticed is that if the wireless network in their area, if they have never connected it to it before, this is not a problem, only if they have saved the wireless network does it present a problem.

My thought here is it could be related to our Check Point VPN software but have not yet had the time to test with this removed.

Anyone else run into this issue before?

How did you resolve?

Anything I can test on my side to narrow down the root cause?

Thank you
CheckThe Logs
CheckThe Logs
  • 3
2 Solutions
David Johnson, CD, MVPOwnerCommented:
turn off wait for network
This policy setting is located in Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon
Set this to disabled.
Nico SCommented:
Please check the event logs if Event ID: 65, 43, 5614 appear, you can try this KB2617858 update
CheckThe LogsAuthor Commented:
Thank you for the feedback, checking into this now and will send updates.
CheckThe LogsAuthor Commented:
Installed KB and tested and appears to have resolved for my PC, so going to test with some others.

Local GP does not show that setting to be configured at all yet but need to verify with server admin on the actual pushed GPO for this.

I would like to say issue resolved but please allow me a few more days to check on my end thank you for the help! Much appreciated!
CheckThe LogsAuthor Commented:
GPO was already set, running the Windows Update Patch resolved this issue thank you :-)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now