Im down it was a false positive. Most likely from some Gmail servers having the new log in so when you’d end up on a server not yet updated; it would give the UNKNOWN info to Avast (as far as webrep) and set off an alarm because Avast knew the screen didn’t match current Google server records (that were updated BEFORE the servers).

Regardless, Im having issues that I cant explain. I can only get Chrome to run on one profile, the others give the error in the screenshot below. As well, my Avast Miniport NDIS driver reports it cannot run (I have a thread on that one). Il take the Chrome issue to Chrome support.

Im not fanning this subject; If Avast is comfortable enough to say it was ONLY a FP and could not have been anything else, then this thread can be locked from further commenting but I still have a pile of inconsistencies that started AFTER the Avast False Positive warning of a Trojan.