Anyone using Avast or AVG can report the false positives here:
https://www.avast.com/report-false-positivehttps://www.avg.com/en-ww/report-false-positiveClick on File and fill out the form. I would do it, but I don't have an alert ID since I don't use either product. It seems only customers of Avast or AVG can report the false positive, grrrr. Anyways...
Two of the files (
JRiverASIODriver64.dll and
hh_portable.dll) that Avast and AVG seem to be flagging as malicious aren't signed with JRiver's Extended Validation (EV) certificate, so that could be why it's happening (for those at least, maybe, but I'm starting to think those AVs have lousy heuristic scanning engines, IMO).
Media Core Launcher.exe which during the install of MC33 is renamed to
MC33.exe is signed with the EV certificate and both Avast/AVG are flagging it. Honestly this is a little mind boggling to me that they don't automatically request/pull a sample and run deeper analysis as it's signed with an EV certificate, since malware creators aren't going to buy expensive EV certs and sign malware on it, as it can be revoked so easily and it'd be a waste of an EV certificate and money.
