New
#230
I came across this tip which MAY BE the solution we have all been looking for for AU version. I HAVE YET TO TRY IT.
Basically, it uses the debugger facility whereby the execution of an executable is redirected to run another application (basically does not check the debugger argumant is actualy a debugger - see quote below).
The rundll32.exe is chosen as it basically does nothing if it does not have a dll argument.
This is a variant on a method I saw where the lockapp.exe directory was renamed so it could not be found - however, that solution crashed on some pcs.
This is slightly different inasmuch to run lockapp.exe, it runs rundll32.exe instead so (IN THEORY) this should not crash.
----------------------------------------
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\LockApp.exe]"debugger"="rundll32.exe"
----------------------------------------
To add to registry, just paste text between dotted lines into a file e.g. lockscreen.reg and double click on it (needs admin rights).
Of course, USUAL CAVEAT - make image backup of Windows first, and backup of registry as well.
I am going to try it in an (unactivated) VM later, and then on my tablet and laptop if it shows promise. Will report back - maybe one of you guys are brave enough to give it a crack as well.
--------------- quote from a web site-------------
Windows doesn't verify that the "debugger" is truly a debugger - it just spawns the application in the debugger value. This means that you can put "notepad.exe" in the debugger value under calc.exe, and every time you try to run "calculator", notepad will run instead.
EDIT: Failed miserably 😥
Last edited by cereberus; 09 Mar 2017 at 14:47.