• Become a Power user Intro to AutoHotkey Intermediate AutoHotkey Intermediate Objects GUIs are Easy w/AutoHotkey Painlessly switch from V1 to V2

Re-Associate AutoHotkey in Windows

Fixing Lost association of AutoHotkey executable

Fixing Lost association of AutoHotkey executable


The key idea of the video is that if AutoHotkey V2 scripts are opening with a text editor instead of running, there are solutions to fix the issue, such as dragging the reset Association script into the AutoHotkey UX executable or compiling the executable in 32-bit mode.

  • 00:00 🔧 If you’re running AutoHotkey V2 and your executable gets unassociated or changed to open with a text editor, there is a solution to fix it.
  • 00:47 🔧 Double-clicking on AutoHotkey scripts that have a hotkey installed will open them with an editor instead of running them, but you can change the default program to open them with.
  • 01:18 🔧 Installing AutoHotkey V2 and dragging the reset Association script into the AutoHotkey UX executable will fix the issue of files opening the site instead of running the script.
  • 01:59 💡 If you don’t have the correct version of AutoHotkey installed, a script designed for a different version will not run.
  • 02:15 🔧 Compiling the AutoHotkey executable in 32-bit mode and resetting the associations with the executable will fix the lost association issue.
  • 02:54 🔧 In AutoHotkey V2, running a script can reset lost associations and the V2 version of Studio will eventually have a feature to run V2 scripts.
  • 03:23 🔧 Use the V1 version of the studio for V1 nerve, and check out the “Edit Swap” script to easily change your default editor for AutoHotkey.

 

Comments are closed.