up vote 5 down vote favorite
2
share [g+] share [fb]

When a Windows 7 32-bit PC attached to a domain comes back from standby mode and has no user logged in, if I log in once, it jumps back to the login screen. If I log in for a second time, then it actually logs in.

This happens on multiple PCs, and is not a hardware issue. The PCs are also free of viruses/malware, and are otherwise Problem-free.

Why does it do this, and is there a way to prevent this annoyance?

link|improve this question
56% accept rate
I've seen this once before but haven't been able to figure it out either – Brenton Taylor Oct 14 '10 at 2:12
I've seen this as well. It started happening on my family's desktop, and drives them nuts. (This is on a computer not on a domain, but otherwise same problem. So cached credentials as suggested below can't be it.) I spent hours looking into it, never figured anything out. I'd love to know what solutions people can think up. I may even return to post a bounty... – nhinkle♦ Oct 14 '10 at 3:46
3  
@Brenton and @ForceFlow, I finally figured it out! There is a KB article for the problem, and a hotfix released. See my answer below for details. – nhinkle♦ Dec 22 '10 at 20:41
feedback

2 Answers

up vote 8 down vote accepted

It turns out that this is a known issue.

KB2345131: The logon screen appears two times when you resume Windows 7 from Sleep or Hibernation

The logon screen may appear two times. Therefore, you have to enter your credentials two times.

This issue occurs when there are multiple pending lock signals to be processed when the user is logging in. In this situation, the WinLogon state machine logs the user off.

Microsoft has released a preliminary hotfix. Because it is only preliminary, and most installations do not experience this problem, the hotfix has not been released in the normal automatic updates channel, which is why the problem hasn't been fixed automatically yet. You can download the hotfix from Microsoft and install it manually.

I installed the hotfix on our computer which was experiencing this issue, and after three days the problem has yet to reappear, so it looks like this fix works.

link|improve this answer
Nice find! I wonder when it's going to be rolled out over auto-updates. – Force Flow Dec 22 '10 at 22:46
Hard to say. Seems like the sort of thing which may be included with SP1 when it eventually gets released, but who really knows. – nhinkle♦ Dec 22 '10 at 23:18
feedback
up vote 0 down vote

Cached credentials are probably meeting some pre-defined rule or policy for timing out, and trying to renegotiate with the domain controller. That's a guess, but I've seen the behaviour before in a similar environment.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.