Hi
@TheArkive, thanks so much for getting back......
TheArkive wrote: ↑15 Sep 2021, 16:44
Do you run anti-virus? Some AV may detect AHK as a "potentially unwanted app" and can then quarantine it.
yes, I have MS shipped protection. AHK 1.1 has run for 2+ years on this laptop with no problems.
Are you on a personal laptop or a work laptop?
Have you restarted before without issue? Or is this the first install/restart?
Personal laptop. Owned 2+ years, with multiple restarts that caused no problem with AHK 1.1.
The fact that the legit installer isnt working points to some other issue. The legit installer should overwrite all my app settings in the registry.
That's what I thought, so imagine my horror when this didn't work. Now completely lost understanding what next things to look at.
EDIT: do you have any weird scripts/cleaners/tuneup programs running?
No - at least not to my knowledge!
EDIT2: Did you enable fully portable mode, or no?
Left it as fully portable.
DaveT1 wrote:
Could it be something in the registry has gone wrong?
It sounds very much like something in the registry is wrong. But it also sounds like something else may be tampering with the registry. Something that doesn't like AHK for some reason.
#runsscreammingintotheseanevertobeseenagain
BUT - I think I fixed it
(got most of the way through replying above, so have left those in case useful to others). Something you said above prompted me to check the file associations and it seemed these got bummed - which I think might have been me
. I'd ended up with
.ahk being associated with VSCode! Once I changed the file association back to
autohotkey unicode 32-bit, double-clicking the ahk file ran it as expected, and ahk context menu items returned.
I'll go through and re-implement your app later today. Then I just have to understand how to make the ahk VSCode extensions I use work between ahk 1.1 and ahk 2!
Thanks so much for your willingness to help
, and sorry to have wasted your time.