Note that there are some explanatory texts on larger screens.

plurals
  1. POAHK utilman script gives file not found error
    text
    copied!<p>I'm trying to create a simple backdoor for myself through utilman on my computer using autohotkey. Basically I want to have the ease of access button function normally in all cases on login screen Except when I hold down the M key, where in this case it opens cmd instead. No batch or cmd window should pop up, and one doesn't. The issue I'm having is that I get a file not found error from the script, I compiled the script into Utilman.exe and tested with a copy of the real utilman (renamed to lol.exe which is specified in the script to run normally) and this works fine in its own directory. However when I do this in the system32 folder it gives an error that lol.exe is not found, also executing lol.exe on it's own gives the exact same error, as if it reroutes to the script named Utilman yet again. Here is the script, should be short and simple:</p> <pre><code>SetWorkingDir %A_ScriptDir% Sleep 400 GetKeyState, state, m if state = D Run cmd.exe else Run lol.exe Sleep 200 ExitApp </code></pre> <p>Thanks for any pointers, alternative suggestions or ideas. This would be great to get working.</p> <p>EDIT: Changing Run lol.exe to Run, "C:\Windows\System32\lol.exe" now gives instead an exe corrupted error. This also happens if I run lol.exe on it's own, I'm really not sure what's happening.</p> <p>EDIT2: Running the script from a different location again gives the file not found error, rather than the exe corrupted error.</p> <p>EDIT3:</p> <pre><code>SetWorkingDir %A_ScriptDir% Sleep 400 GetKeyState, state, m if state = D Run cmd.exe else Run %A_WinDir%\system32\control.exe access.cpl Sleep 200 ExitApp </code></pre> <p>This works perfectly everywhere EXCEPT the system32 folder, where it gives the exe corrupted error even when run with elevated permissions, this is frustrating.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload