abaelard

I got the original problem back. Obviously MS reintroduced the trojan-definition back in the latest definition 1.263.598.0 https://www.microsoft.com/en-us/wdsi/definitions/antimalware-definition-release-notes?RequestVersion=1.263.598.0&Release=Released&Package=AM The virustotal.com check of the file came up clean, yet i'm not going to take any chances. Looking forward to see this issue ironed out. cheers chris