I'm fairly new to using the K2, and to scripting installs, but it seems in former scripted installs with previous versions of Windows, the autologon feature worked just fine (where you go into the "Setup Configuration: (Hidden)Show" area and in that screen specify to autologon with a username, password, and number of autologons).

And it seems like it even worked with previous versions of Windows 10. But when I started using the Creator's Update, the autologon no longer works. Every time during the scripted install when a reboot occurs, I have to manually log into the computer in order for the scripted install to continue. Very tedious.

I vaguely recall maybe reading something about the Creator's Update breaking something in this regard, but I can't find it after about a week of looking and trying everything.

Any help would be very much appreciated. Thanks!
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


this has been covered here already...

Answered 08/12/2017 by: Pressanykey
Red Belt

Please log in to comment
Pressanykey (Phil) gave me a partial answer.

That link says that Microsoft introduced the problem with a Windows Update, and had fixed it in a later Windows Update, that fix being:


That link says it's outdated, and has been superseded b:


When I try to install this, I'm told it's not supported on my system. I believe this is because in the time between the scripted install and the time I tried to install this as part of my testing, the machine had already picked up:


which had upgraded my OS Build from 15063.0 to 15063.540

I've not yet been able to test the script, as I've made another change to my scripted install that has me currently broken (foolish me, believing that ticking the "Add Powershell to the KBE" checkbox in the KBE Media Manipulator would actually add Powershell to the KBE. Pfft!), but I wanted to get this information in this thread so that others might be able to find what I've learned so far.


Answered 08/15/2017 by: kentwest
Third Degree Blue Belt

  • Hi Kent,
    as I've mentioned in another Post, I have the luck to be able to use an LTSB version of the OS, so OS patches / updates have minimal impact (I'm able to test thoroughly on my OSD deployment). I only get the jitters when critical security patches are released ;-)

Please log in to comment