Whilst that is entirely possible, see below, but the best thing is to a) conform it is a false positive, b) report it, e.g. send the sample to avast, c) avast should confirm it is an FP and correct the signatures.
I don't use the server version for avast but this is the procedure for avast Home/Pro version, presumably there is an equivalent in the server version.
You can add it to the exclusions lists:
Standard Shield, Customize, Advanced, Add and Program Settings, Exclusions (right click the avast ' a ' icon).
Restore it to its original location, periodically check it (scan it in the chest), there should still be a copy in the chest even though you restored it to the original location.
When it is no longer detected then you can also remove it from the Standard Shield and Program Settings, exclusions.
Confirmation of detection:
You could check the offending/suspect file at:
VirusTotal - Multi engine on-line virus scanner and
report the findings here the URL in the Address bar of the VT results page. You can't do this with the file securely in the chest, you need to extract it to a temporary (not original) location first, see below.
Create a folder called Suspect in the C:\ drive, e.g. C:\Suspect. Now exclude that folder in the
Standard Shield, Customize, Advanced, Add, type (or copy and paste) C:\Suspect\* That will stop the standard shield scanning any file you put in that folder. You should now be able to export any file in the chest to this folder and upload it to VirusTotal without avast alerting.
