The “intellect scanning” has nothing to do with evo-gen detections, it is how the web shield scans downloaded content. The “intellect scanning” means avast scans content as it is actually downloaded and not after the download has completed.
If you have a project folder for new complied files, etc. and add that full path to the avastUI > Settings > General > Exclusions - File paths. Whilst you can add a wildcard * to the end of the path which would exclude the whole folder.
I would suggest adding a more limited use of the wildcard function, to only exclude certain file types in that folder, e.g. G:\Drive-Images*.v2i This is an example I use so as not to scan my drive image files, which can be very large.
The evo-gen relates to files that are new and not seen on many systems, so considered suspicious - given these are new creations the file # is unlikely to be on the avast cloud database.
Many legitimate programs are getting detected like this and from the description above it looks like this should be an optional detection. Also, there is no way to ignore a file that was detected even if the default action is Ask. Not only does this block Git, MKVToolNix and others while downloading or extracting, it also blocks the program I am working on in Visual Studio 2013 and the exclusions list didn’t always work. I had to add 3 different folders to the exclusions before it let design or debug my program.
EDIT: In most cases Avast will delete the file without asking, regardless of the Actions settings!
If no way to disable this detection is added I will uninstall Avast. I have recommended Avast to many people an I am sad to see it become a nuisance for me. Please fix this issue!