Yep, that is correct, then you have to "re-apply" it. Kinda ridiculous that MS took away the option to disable this, BUT, there will always be a solution from the community
Multi OEM/Retail Project has addressed the lock screen, login background and the login user picture from oobe mode. Doing it from desktop will take Alphawaves tool once updated. Doing it from desktop is a different ballgame compared to oobe mode. When Alphawaves returns I am sure he will update his tool. I sent him the info but like I said doing it from desktop is more difficult and requires his knowledge in .net to address it. Give him time and he will address this from a desktop environment.
If you remove all of these listed packages in 1607 the lockscreen is still there. You can also sign in with a local user account password, hence the login function is not affected.
I am aware of what's going on, and I wish him well, but Alphawaves had a really elegant solution for non AU systems. I think I'll just wait for the AU updated version.
Sorry for the late reply. By 'lock screen gone' I meant the part that scrolls up and reveals the login screen. After removing the components it just showed the login screen. I used a regular local account with password, no autologin, no M$ accounts or PIN logins or biometrics. I don't know how different login types might or might not affect this. I don't have this installation anymore (because of other tests), I doubt this is a 'safe' mod to use in production.. I might just settle with the scheduled tasks trick.
With win10 anniversary versions of the lock screen, login screen and user pic on login screen can easily be changed with some tweaks. The images are no longer in a file that needs updating all the time with Alphawaves tool. That was the problem with it, if windows updated it more then likely reverted or broke login. At least now that isnt a issue any longer. With this being said, doing it from desktop environment is more difficult because of windows storing the images in system locked folders. Doing this from oobe mode is easier since you are the system when installing windows. I am sure Alphawaves will update his tool when he gets time. I sent him info on how the new images are stored and how to manipulate it without system instability or windows update breaking it. The multi oem/retail project accomplishes this while in oobe mode of windows install.