New
#140
There are some very sharp tools looking for the solution, MS must have really fixed it so that it is really hard to prevent. I'm confident some one will find the solution sooner or later, hoping for sooner here too.
There are some very sharp tools looking for the solution, MS must have really fixed it so that it is really hard to prevent. I'm confident some one will find the solution sooner or later, hoping for sooner here too.
As far as I know so far on 1607 (AU) yes
I assume you are on Au? you system specs say Win 7x64.....
Shame MS removed the persistent registry value for this. Having to run Reg.exe at each login is not ideal. Hope better options come along.
If anyone's interested, I put together this PowerShell script for creating the Scheduled Task from step 3. Just paste this into an elevated PowerShell prompt:
I tried doing it purely with the various Scheduled Tasks Cmdlets, but there isn't yet a New-ScheduledTaskTrigger for "On workstation unlock", so XML it is.Code:$SID = ((New-Object System.Security.Principal.NTAccount("$env:UserName")).Translate([System.Security.Principal.SecurityIdentifier])).Value Register-ScheduledTask -TaskName 'Disable Lock Screen' -Xml @" <Task version='1.4' xmlns='http://schemas.microsoft.com/windows/2004/02/mit/task'> <RegistrationInfo> <URI>\Disable Lock Screen</URI> </RegistrationInfo> <Triggers> <LogonTrigger> <Enabled>true</Enabled> </LogonTrigger> <SessionStateChangeTrigger> <Enabled>true</Enabled> <StateChange>SessionUnlock</StateChange> </SessionStateChangeTrigger> </Triggers> <Principals> <Principal id='Author'> <UserId>$SID</UserId> <RunLevel>HighestAvailable</RunLevel> </Principal> </Principals> <Settings> <DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries> </Settings> <Actions Context='Author'> <Exec> <Command>reg</Command> <Arguments>add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\SessionData /t REG_DWORD /v AllowLockScreen /d 0 /f</Arguments> </Exec> </Actions> </Task> "@
Last edited by Michael; 15 Sep 2016 at 22:19.
I didn't yet.. and I'm a bit afraid to try dangerous things that can taff up my PC.
Disable Lock Screen Even on Reboot / Restart - Tested / Working
********************************************************************
SEE UPDATE from Author at TenForums Right Here:
Lock Screen - Enable or Disable in Windows 10 - Page 17 - Windows 10 Forums
The only way to disable the lock screen on startup (boot) is to modify LogonController.dll with a hex editor. A programmer created an automatic patcher.
WARNING: Downloading system files or patchers from unknown sources is extremely dangerous. Do so at your OWN RISK.
This patch has been scanned by virustotal.com and here are the results:
https://www.virustotal.com/en/file/e...f334/analysis/
I have reviewed the script and in my opinion it looks OK. I used a binary file comparison utility, and in my opinion the files are identical except for the changes mentioned below (Offset: 0xBF50 48 89 5C 24 08 -> C3 90 90 90 90). I have also scanned the patched file LogonController.dll with VirusTotal and here are the results:
https://www.virustotal.com/en/file/e...is/1474064629/
I've tested this with Windows 10 Pro Anniversary 64-Bit version 1607 build 14393.187. This is the latest. It worked fine. The author states it will work with earlier versions of Windows 10 Anniversary as well.
How to Disable Lock Screen, even on Boot
Bundled the 2 architectures into 1 installer script.
-- It's now very easy to use, Just run Install.cmd as Administrator (Right Click and select Run As Administrator).
I also made a restore script.
-- To restore the backed up LogonController.dll run Restore.cmd as Administrator.
Works for both Home & Pro and all Languages 32bit & 64bit.
Architecture x86
(Patches Offset: 0x1C680 8B FF -> C3 90)
Architecture x64
(Patches Offset: 0xBF50 48 89 5C 24 08 -> C3 90 90 90 90)
DOWNLOAD PATCHER : SEE NEWER PATCHER HERE:
Lock Screen - Enable or Disable in Windows 10 - Page 17 - Windows 10 Forums
Old Patcher:
LogonController_Patch.zip
https://drive.google.com/open?id=0ByXxjI18DZC5VE8xalJKSGJ3SXc
Also Attached to this Message: LogonController_Patch.zip.
As a safety feature you can't apply a patch twice, as you would then overwrite the backup file.
The script looks for LogonController.bak in the system32 folder which is the backup file name.
In the future, if MS updates the dll file, manually delete that backupfile in order to run the autopatcher again.
I would then also suggest to move/copy the Restore.cmd file to the root of your systemdrive, as it will then be quite easy to restore the dll from bootable installation media, should the need occur.
Note: You may still need to use the Disable_Lock_Screen.reg file to disable the screen when locking (not rebooting).
Additional Notes: If there is a major Windows update, and the dll patch location is moved (or the dll is rewritten) the patcher engine will fail and not allow a patch to be made. That's by design.
If necessary, just visit https://forums.mydigitallife.info/th...creenGone-v1-0 for a new patcher.
Source / Author - Thank You Dobbelina at gHacks Technology News!!!
See comment by Dobbelina September 15, 2016 at 10:02 pm (very bottom of page):
http://www.ghacks.net/2016/08/05/disable-windows-10-lock-screen/
Last edited by Intrepid1; 14 Oct 2016 at 12:39.
Yes, this works just fine. Many thanks to the creator(s).
Let's hope this unofficial fix doesn't cause problems after future Windows updates.