Contacted AVG Support on this matter, have copied an email I received from AVG support to back up fjwben's post, states the following:
Thank you for contacting AVG.
#1 C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Data\481a57315052f41e27eb10e2eb54b739\System.Data.ni.dll (Critical .NET framework file)
Those are the two the we are seeing more often as false positives. If you have deleted the System.Data.ni.dll a restart on that device might restore it but if not, then you will have to re-install the .NET framework.
It is "un-officially" being listed as a false positive. This issue was just discovered and reported to us on Friday and we have escalated it to the DEV team in Prague. We ask that you keep updating your definitions and scan regularly. As soon as the DEV team publishes the fix it will come through your updates. We do apologize for you experiencing this issue but ask that you have patience with us and our DEV team as we work on a solution.
AVG Customer Care
Hope this helps anyone who was debating allowing/writing an exception for the SCGeneric2.AOEH error - was advised over the phone to 'ignore' however have had a few customers calling in regarding this saying they have a Trojan horse and are running in circles in the office panicking. Advise probably writing an exception for this until the fix is released within 48 hours as I was told by Kevin.
Edited by Luke_Baylis, 26 June 2017 - 04:28 AM.