I have a networked NAS that I backup my files to. Every time a file is copied to that share, Avast puts a couple errors in the Error Logs saying that there was an error scanning the file on the share. It’s error 00000035. I believe this is because the Avast service doesn’t have permission to scan that share, as it is running as the LocalSystem, instead of an account with rights to access the share.
The thing is, I don’t want Avast to scan the network at all, so I don’t want to have to modify the service just to get rid of the errors. I have excluded the network in both the overall Program settings’ Exclusions list and in the Standard Shield’s Exclusion list. In both, I’ve added “\[nas]*”, where [nas] equals the name of the device. Despite these exclusions, the errors continue to show up in the error logs.
Is there anything I could be missing? Is there anyway to just completely disable network scanning?
Try putting the eicar test file in one of the NAS locations and see what path is returned in the alert and use that as the basis of the exclusion. Sorry I don’t us NAS so have no practical experience of how to exclude it.
Is the NAS mapped to a physical drive? I’m sure it isn’t, but you could exclude that drive letter if it was. Other than that, I don’t know, I don’t have a NAS at home to play with either… sorry!
Yeah, it’s mapped to a physical drive, but the logs reference the UNC path (\[nas]). Am I excluding properly? If one adds \[nas]* to the exclusions, should that include all files and subfolders on that share?
I’m not completely sure whether the exclusions are checked before or after the expansion from the mapped drives to the network path. So, I’d suggest to put also the mapped drives (e.g. as X:*) into the list of exclusions.