Alright, thank you. By first opening the expert settings on the file shield and then manually finding the steam folder in my program files.
Report it as a false positive:
There is an on-line contact form, http://www.avast.com/contact-form.php?loadStyles for: * Sales inquiries; Technical issues; Website issues; Report false virus alert in file; Report false virus alert on website; Undetected Malware; Press (Media), issues.
- If you are reporting an FP, then you get another input field open, click Browse button and navigate to the file to upload for review, etc. A link to this topic also wouldn’t hurt.
I’ve reported it, but to be fair this really isn’t acceptable, they have falsely reported Steam files as a virus about 3 times in the past month, surely something as widely used as Steam should be on their test systems? From reading at other forums, issues like this will make people switch away from Avast.
The latest Stream update has fixed the last false positive.
I don’t know if these files that are being pinged are some sort of anti-cheat for the game as we have seen anti-cheat files be detected before because of their nature they are quite stealthy and what they are doing (to prevent cheating) may be considered suspicious.
To keep ahead of the curve any anti-cheat would be constantly updated.
I had this problem yesterday with FileSystem_Steam.dll as a “High Severity” Threat of: Win32:Malware-gen. After relaunching Steam (by using the short cut placed on your desktop during install), it updated once more, I imagine to replace the missing file of FileSystem_Steam.dll.
When I booted today, in the Steam folder, tier0_s.dll came up as a “High Severyity” Threat of Win32:Malware-gen. Again, booting up Steam updated again to probably replace the missing file of tier0_s.dll. After each file was moved to chest, all I needed was a simple boot of Steam for it to go again. While downloading, the shield never went off. After the first issue, I did a boot time scan as the little pop-up window suggested (after launching Steam again and letting it update). There was nothing infected on my system according to that scan. I don’t think I’ll rescan again after this incident as I find it being just an annoying false positive. According to Avast!, both of the originally “infected” files are sitting in the chest with the new ones that Steam downloaded in the Steam folder with a perfectly working copy of Steam.
This is the only issue I’ve ever had with Avast! picking up a false-positive, but it’s still a bit annoying. It’ll be extremely annoying if there’s a different file each day that it picks up as being a malwaregen, but I presume the issue will be fixed soon.
For those curious to see, here’s a screenshot of the “File System Shield Scan Logs”, showing both of the “infected” Steam files, severity, status, action and results of both: http://puu.sh/P99d
If they are still detected (ensure you have the latest virus definitions), then report them as false positives as outlined in Reply #21 above.
There have been lots of streaming updates this afternoon (10 see image), some very recently and some of those have been used to correct FPs.