I just took the latest patch from here, manually deleted the LogonController.bak file and tried apply the patch again..... it gave me error "Sorry, your LogonController.dll has an unknown MD5".
@BartHD Thanks a lot for that sh.., had to reinstall the machine. Even sfc /scannow from the recovery console did not work. Windows 10 Version 1703 Build 15063.138 hangs with black screen after applying that dll.
Wow 1st post "Thank you", 2nd post "Thank you for that sh.." you're really making friends there... Next time delete the patched dll and replace it with the backup dll. If you don't know how to do that, you shouldn't be using ANY 3rd party tools.
I concur. The creator's update has indeed nulled the patch... I'm beginning to get fed up playing a constant game of whack-a-mole with Microsoft on this. Their updates re Windows 10 seem to be becoming more and more frequent - with the logon controller DLL being replaced each and every time. Props to dobbelina for his efforts thus far but given the way in which MS seem to regularly overhaul W10 by way of update these days, I'm not sure we're ever gonna get a fix that lasts more than a month or two.
Works for the actually new Windows Update called: Creators Update (Version: 15063.138) Great work and thanks for it !!! BUT hard to find on this site between other posts, but please copy it to Threadstart, thanks, it works great. PS: cant post the link again, i must have 20 post to post and qoute links here in this forums. really bad, never see it this at hundred of forums and over 20 years over internet work.
On the other hand, I've seen this limitation in several forums: it's mainly to avoid spam, usually there's a 3, 5 or 10 post minimum before limitations are disabled. You can always split the link, it won't be clickable but we'll get the picture
Hate to say it I already pointed this out as it was available as a group policy edit in a couple of builds prior to 15063. Actually nothing new here just that MS stated it in those notes.
This regedit fixes it: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization] "NoLockScreen"=dword:00000001 Save above text as lockscreen.reg and apply.
Strange, how enabling the setting doesn't seem to make any difference... the lock screen still appears as normal
That's what I get for not reading your original post properly! Any idea when said build is set to roll out officially?
This appeared in the last KB4016240-Version 1703(OS Build 15063.250) Improvements and fixes Addressed issue that prevents the lock screen from being disabled using Group Policy on Professional SKUs.