Not running - DLL registration issue?
Opened this issue · 14 comments
I have "unblocked" both the .EXE file and the .DLL file, and even downloaded the latest version of the DLL, but the script still does not work. I put MsgBox statements in the script, and the problem seems to be in executing the "DllCall(GoToDesktopNumberProc, Int, n-1)" statement.
I am running on 64-bit Windows 10.
Any clues as to what else I can try?
More info:
Right after the call that loads the DLL, %ErrorLevel% has a value of zero.
Right after attempting the "GoToDesktopNumberProc" attempt, %ErrorLevel% is -4 (negative 4).
AutoHotKey documentation says that means "The specified function could not be found inside the DLL."
Did you ever get a resolution? I just downloaded / installed and it doesn't work at all. I'm also on Win 10 64-bit.
Hi. What is the version of your Windows installations?
@sdias: I have Win 10 Home, 64-bit. (The 'free' update from Win 8.x)
ver: Microsoft Windows [Version 10.0.14393]
I need to clarify... The EXE works. (Mostly, at least. Still checking some key assignments.)
Running the AHK file fails. The systray icon loads, I can right click it, etc., but the hotkeys don't work.
I think the problem is either related to admin permissions or with the latest Windows update. I'll have to investigate when I have some time.
@gityta That's strange. Maybe AutoHotkey isn't running with enough permissions.
For what it's worth, running the script as Administrator did not change the behavior.
I have version 1.1.24.00
Just updated to 1.1.25.01 and tired again. The script still loads the tray icon but does nothing else.
I'm sticking with the EXE, as it's working great.
@gityta Very strange indeed. The only other reason I can think of is that the script and the executable are running different code, but I recompiled the script into a new executable, and both still work on my machine. I'm glad the executable works for you though.
I'll leave this open to see if any other people are experiencing this, and based on what they report to see if we can debug this further.