Enable or Disable Lock Screen in Windows 10  

Page 18 of 32 FirstFirst ... 8161718192028 ... LastLast

  1. meh
    Posts : 69
    Windows 9 (aka Windows 10)
       #170

    I get why you suggest restoring the original DLL first. But why not have the script look at the MD5 of the current DLL, and if there's no match, look at the MD5 of the BAK? If that matches, then you're good. Already have a backup and it just means the script has been run before; replace the current DLL as usual and of course don't replace the BAK.
      My Computer


  2. zil
    Posts : 33
    Win 7 Pro x64
       #171

    dobbelina said:
    I have updated the patcher to LogonController_Patchv2.zip
    Some users have an issue with the background image not showing behind the login screen from boot, fixed.
    I also realized that you can't have the secure sign-in option enabled!, (eg, press Ctrl+Alt+Delete)
    This is not a standard setting and the hack doesn't work, the new patch also solves that issue.

    Try this new patch and choose "Restore lockscreen" first when running Install.cmd,
    so the original dll file is restored before running the patcher again.

    Download:
    LogonController_Patchv2.zip
    Thank you! :) Works as expected and without problems.
      My Computer


  3. Posts : 12
    Windows 10
       #172

    meh said:
    I get why you suggest restoring the original DLL first. But why not have the script look at the MD5 of the current DLL, and if there's no match, look at the MD5 of the BAK? If that matches, then you're good. Already have a backup and it just means the script has been run before; replace the current DLL as usual and of course don't replace the BAK.
    Hi there "meh"

    The reason for that is because a user might have the patch in place, (And the corresponding LogonController.bak file)
    He then updates his windows to a new version via WU.
    Then the script might not recognize the new dll, but finds a match for the BAK file.
    Simply replacing the original without making a backupfile would then be a bad idea.
    Making a backupfile anyway would solve that issue, but a new one arises, and that is if a user hasn't updated Windows,
    but simply want to run a new version patcher, then making a backup would overwrite the original.

    I might add, If you update Windows to a new version dll, with the patch in place, you need to manually delete
    the bak file to run the patcher again.

    Believe me, I thought about this
      My Computer


  4. meh
    Posts : 69
    Windows 9 (aka Windows 10)
       #173

    If the original didn't match, the script would exit. Obviously. Did I suggest replacing a new, unrecognized DLL? No. Didn't think I needed to be that explicit. I get it. But never mind. Keep putting the onus on the user.
      My Computer


  5. Posts : 31
    Windows 10
       #174

    Thank You ! Great results with Windows 10 home 1607 from standby to desktop with no prompt.
      My Computer


  6. Posts : 48
    Windows 10/8.1/XP/7/Vista
       #175

    Thanks Brink...I have not needed to use this but am sending other Windows 10 users here.*john
      My Computer


  7. Posts : 68,655
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #176

    I'm glad it could help. :)
      My Computers


  8. Posts : 32
    Windows 10
       #177

    Yesterday: Installed Win10 over win8.1 on another laptop. Ran Patch V.2 and worked as expected!
    Today: Automatic updates installed and the Lockscreen was back on.
    I ran the Patch again and it said: Already Patched, worked fine after Hibernation, but not after re-boot. Still "suffering" from annoying LockScreen.
      My Computer


  9. Posts : 32
    Windows 10
       #178

    Found the solution: I am using Total Commander for File management. There is a registry "patch" called "Take Ownership". When running this patch it add's an option "Take Ownership" to the "Drop-Down Dialog Box".
    After "Taking Ownership" of the LockScreen.dll file and running the Patch V.2 again it worked as it should.
    This is the fore-mentioned reg file :

    https://www.tenforums.com/tutorials/3...dows-10-a.html
    Last edited by Brink; 19 Oct 2016 at 08:56. Reason: added tutorial link for more info
      My Computer


  10. Posts : 12
    Windows 10
       #179

    theo54au said:
    Found the solution: I am using Total Commander for File management. There is a registry "patch" called "Take Ownership". When running this patch it add's an option "Take Ownership" to the "Drop-Down Dialog Box".
    After "Taking Ownership" of the LockScreen.dll file and running the Patch V.2 again it worked as it should.
    This is the fore-mentioned reg file :

    https://www.tenforums.com/tutorials/3...dows-10-a.html
    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 backupfiles name.
    If you update Windows via WU, and you got a patched dll, you have to manually delete the LogonController.bak
    file from System32 if the LogonController.dll gets replaced, otherwise the patcher wont run again.
    (access denied message if you try to restore, or Already Patched if you try to patch again )

    I have updated linked #162 with this info not to cause confusion.
    Last edited by dobbelina; 19 Oct 2016 at 21:22.
      My Computer


 

Tutorial Categories

Enable or Disable Lock Screen in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:36.
Find Us




Windows 10 Forums