Thanks for the quick response!
If you enabled the "OK files" to be stored in the FileSystem Shield's report to see what's being scanned, you need to restart the FileSystem Shield for the change to take effect.
Yes, I have had "ok files" enabled for a long time so I can track what Avast spins its wheels on. It showing lots of other OKs so I know OK logging is working
If the record isn't there even after that, then it's not really a scan that's going on.
Regarding the exclusions - what exactly did you put there? Is Z:\ a real drive?
Yes, Z is a real drive. It a local, FAT32 partition. Nothing special to it. I mapped it to Z so its always at the bottom of the list.
I actually went and turned off all the shields, and I still see the AvastSvc.exe reading the git.exe every time I access it through WebStorm. So it seems to be Avast functionality that is not contained in any of the shields. Is there some type of process monitoring that isn't contained in the shields?
I don't think its related, but I'll add I have rootkit scan disabled also.
Thanks,
d