Share via

Blue Screen occurs after sleep/lock (by inactivity) when I press CtrlAltEnd to attempt logon

Anonymous
2023-09-28T08:44:07+00:00

Hi,

I upgraded 2/3 Windows Server 2012 into Windows Server 2019, 0 issues except for one server.

I'm using VMWare, the issue occur on the console and only for one user : "Joe".

The session of the account "Joe" goes into sleep/lock after an inactivity period.

When I use VNC or vSphere/VMWare console to try logging in and wake the session up, the screen lights up and print me "Ctrl-Alt-Del to unlock". When I do that, the screen goes blue (#133765), without any text or anything.

The 2 ways to take control of the console again is either :

  • to restart the VM;
  • to login with "Joe" via RDP : after that the RDP session will close with a warning and the console will log into "Joe".

Moreover, when log on another session and checking which user are connected or not via Task Manager, "Joe" is connected when the blue screen occur. When I disconnect "Joe", the autologin clear the issue, just like RDP and connect "Joe" without any issue.

I cannot find anything on this and I got no issue with the other new reborn Win2019 server.

I need the autologin and 'ForceAutoLogon' on "Joe" for applications purpose. I do not have the issue when 'ForceAutoLogon' is off.

Max session at the same time : 2.

I tried to change regedit "ForceUnlockLogon" (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon) but it didn't solve the issue.

The problem isn't the 'Sleep' but the 'Lock' after inactivity. More specifically, the 'CtrlAltDel' menu.

If i deactivate the option, I'll just pretend that the problem is gone, I'm not actually solving it...

I hope my explanation was good and that someone will give me some clue.

Windows for business | Windows Server | Performance | System performance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-10-09T11:00:09+00:00

    Hello

    It seems like you’re experiencing a specific issue with the “Joe” user account on one of your Windows Server 2019 VMs. After the account goes into sleep/lock due to inactivity, attempting to unlock the session results in a blue screen.

    Here are a few suggestions that might help resolve this issue:

    Check for Updates: Ensure that your Windows Server 2019 and VMware tools are up-to-date. Sometimes, these kinds of issues can be resolved with a simple update.

    Check User Account Settings: There might be something specific to the “Joe” user account that’s causing this issue. Try creating a new user account and see if the issue persists.

    Disable Sleep/Lock: As a workaround, you could consider disabling the sleep/lock feature for the “Joe” user account. This might prevent the issue from occurring, although it won’t address the underlying cause.

    Check Event Viewer: The Windows Event Viewer might provide more information about what’s causing this issue. Look for any error messages or warnings that occur around the time the blue screen appears.

    Reference documentation:

    Blue screen on Server after loggin - Windows Server (spiceworks.com)

    0 comments