Server starts to fast for autologon

Question

we use sysinternls autologon on windows server 2016/2019 vms with hyperv 2019.

sometimes after a reboot the autologon does not work.
we suspect that the reboot is too fast.
since our vms boot very fast.
is there a solution to delay the autologon

best regards
Thomas

Answer 1

I think there is no way to jump autologon even if the machine boot in 1 ms the windows code will look at the registry and will perform the logon..

I think you are just locked out by some other policy in place.. I mean, if you connect to the machine which appears to not have performed the logon, via TS, and will run Process Explorer, you will find 2 session on the machine, the first one with the autologon user and the second one with the remote user..

I think that the autologon is successful but the console get later locked and so you are under the impression it didn't work.

Try connect remotely with another user and check the running sessions..

HTH
-mario

Answer 2

In Windows 10, if a credential provider wants to automatically log the user on in a situation Windows does not think is appropriate, the system will display a sign in button as a speed bump. One example of this is when a user with an empty password locks the computer or signs out. In that scenario, Windows does not directly log the user back in.

(ICredentialProviderCredential::SetSelected (credentialprovider.h) - Win32 apps | Microsoft Learn)

Answer 3

Weren't you talking about Windows Server 2016/2019??
Windows 10 is something totally different...

Anyway did you try checking remotely the sessions on the server??
Youcan use qwinsta:

qwinsta /server:servername

and you will get back the numbers of session with the logged on user

HTH
-mario