Autohotkey Execute Bin Not Found

Question

Autohotkey Execute Bin Not Found

Closed this issue 2 years ago · 9 comments

HI, even if I have this set up:
"ahk++.file.executePath": "C:\Users\giuliano.peretti\AppData\Local\Microsoft\WindowsApps\AutoHotkeyU64.exe"

when I try to debug I have:

Any suggestion?

Answer 1 · 2022-12-24T18:17:24.000Z

All exe files has 0 KB size on screenshot. Why? Probably there are no actual files at all.

Answer 2 · 2022-12-24T18:55:04.000Z

Is it possible that AutoHotkey has been installed somewhere other than the default location of C:\Program Files\AutoHotkey? If so, the path will have to be changed in the settings.

Answer 3 · 2022-12-24T21:56:56.000Z

good point, true.
but there is something strange (I mean that I don't understand)...
i.e. if I execute "Ahk2Exe.exe" (has size 0) from that location:

If via "Task Manager" I open files location for this new process it opens:

I have to say that this installation is coming from "Microsoft Store"

Answer 4 · 2022-12-25T00:25:03.000Z

Beyond my knowledge. You may need to wait for @mark-wiemer to get back from Xmas break for his advice.

Answer 5 · 2023-01-17T03:25:27.000Z

Hey @perettigiuliano, the files you're showing in the 0 KB screenshots are shortcuts, that's why they're 0 KB. You'll want to change the path to the AutoHotkey.exe to that "poweredbyweatherlights" folder which contains the actual applications.

As a side note, I'm not sure where you got this installation from. The trusted installations always come directly from https://autohotkey.com. If you're not sure where this folder came from, I'd recommend deleting it and re-installing from the trusted site.

Closing this one as a user issue, feel free to open a discussion if you're having more trouble getting the extension configured :)

Answer 6 · 2023-01-17T05:14:56.000Z

Hi, the installation is coming from Microsoft Store. Is it not trusted?

Answer 7 · 2023-01-18T13:01:19.000Z

It's probably OK :) note I do work for Microsoft so I'm a bit biased, you're welcome to do your research into the publisher who put it on the store.

Answer 8 · 2023-08-03T21:34:19.000Z

Installed this today and had a sort of similar issue. Dropping this note here in case it helps anyone else. My problem was that the default install path was C:/Program Files/AutoHotkey/v2/AutoHotkey64.exe. Updating the settings as suggested by @fade2gray resolved the my issue. Also note that when I set the path to point to AutoHotkey64_UIA.exe, the debugger didn't seem to do anything.

Answer 9 · 2023-08-04T02:18:05.000Z

Hey @racingcow, UIA only works if the script to run is within the Program Files directory, that's probably why you had the issue. And yes, the defaults may need to be updated with the official v2 release now. Thanks for dropping this note :)