Windows 10: Autologon never works on Windows 10 1709

Hi,


Its been a while we trying to resolve an issue with Autologon on Windows 10.


We set registry values as recommended by MS to get Autologon done for domain user. Issue is after a reboot of machine autoadminlogon reaches to value 0 and never login . Also default password value disappears. There are n number of articles exists in net but no suitable soulution yet. Can some one help?

:)

 

Creative X-Fi Soundcards and Windows 10 Fall Creators Update 1709 = Complete Disaster / Not Working

Thank you for trying to help , i did tried your suggestion but it did not work :/ , nothing seems to make it work on Windows 10 Fall Creators Update 1709. In the meantime i have bought a new SoundBlasterX AE-5 and it did installed flawlessly , no problems whatsoever. it is up to Creative ( drivers ) and Microsoft ( bug fix ) to fix this huge bugs with Audio.

Kind Regards: Chispy

 

AutoLogon not working in domain environment


I have a strange problem with AutoLogon in our domain environment:

we have several machines that are configured for autologon, where the registry entries DefaultUsername, DefaultPassword, DefaultDomainName are all verified as having the correct data, and AutoAdminLogon is set to a value of '1'....

...but the machine does not autologon to that account, but instead shows the LOCK SCREEN for the account, and it is asking for email address instead of username, like it is not in a domain environment.

This occurs whether we run the Autologon.exe application, or manually configure the registry.

My guess is there is something else amiss, like a security setting, because everything I am reading says autologon itself is configured properly.

Has anyone experienced this? Do you know where I should start looking?

----------------------------------------------
Windows 10 Enterprise, build 1709

 

AutoLogon is disabled after feature pack install

After windows 10 feature pack 1709 is applied, AutoLogon is disabled. This is happening going from 1607 to 1709 on all machines using Autologon. Is this a function of all feature packs? Is there a way of re-enabling without manually touching all our machines?
We can manually re-enable it using the same Autologon file that's still on the machine. We use the Sysinternals Autologon.

Moved from:
Windows 10/Windows settings