Thanks Pondus - I agree. Every time an AutoHotKey script is run, the interpreter must be in memory to interpret it, but Avast does not call out the interpreter (which starts at boot time) - it flags the script file, and it is the script file that gets put in quarantine. If I then try to run a different script file, it also gets flaggand quarantined, but the interpreter does not.
Asyn, to answer your questions
- Which Avast..? (Free/Premium/One) - Free
- Which version/build of Avast..? -21.2.2455 (build 21.2.6096.705)
- OS..? (32/64 Bit..? - which SP/Build..?) - Windows 7/64 pro SP1
Avast is under Program Files (as opposed to Program files (x86)), so I presume it's a 64 bit version.
- Other security related software installed..? - none that I have installed knowingly. I think there is an anti-malware in Windows
- Which AV(s) did you use before Avast..? - can't remember - it's a lot of years ago
This all probably seems a bit odd, so here's the story.
I have been running Windows-7 for many years (I think it's about 8 years), but I recently had a boot failure. I removed the drive and fitted another drive, formatted it and put a Win-7 OS on it from the installation DVDs. This installation is only a month old. It allows me to browse the web, send emails, etc. - do some of the essential stuff. I can't run many of the programs on the original drive, however (on USB). For example, Excel says "This program must be installed before it can be used"
The original drive is readable (but not bootable) on USB, so I copied the Program Files (also Program files (X32/86) to the "new" drive. Avast seems to be working as before, but is picking on my script files, which it wasn't before, so I thought a global exception for all .ahk files would fix it.
It probably seems to you that getting this info is a bit like pulling teeth, for which I apologise - but I really thought that somebody would give me a simple procedure to set a global file exception for all ahk files, and that would get me going again. It will be temporary in any case, as for several reasons, I am going to get another laptop - though I will probably still be using this one for a couple of months while I "move into" the new one.