There really hasn't been anything added that should of caused it to happen. My suspicion is that the client downloading an update for itself and launching the setup.exe for the new client is what the issue is. Moving forward the client will now direct you to the website to manually do an update. Hopefully this will solve the issue for a lot of people. I also made a change that registers the Tukui Client as a ClickOnce application.Kytak wrote: ↑Sat Sep 16, 2017 3:54 pmI uninstalled it and reinstalled again from the Tukui website. So far no warning from AVG during the installation.
I didn't get one when I installed it previously after the Tukui website rebuild. I'd have reported it otherwise.
The warnings only started appearing with very recent client initiated updates. I'll let you know what happens next time there is a Tukui Client initiated update.
History: Originally I had the Tukui Client from the previous Tukui website that got hacked, then that client got replaced by a new one from the new rebuilt Tukui website. No warnings were reported by AVG for any of those installs. IIRC there were a couple of updates to the new client in the first day or so of the new Tukui rebuilt website coming online and none of those new tukui client initiated updates caused any problems for AVG. Its only been the last 3 ( so the last week or so ??) of tukui client initiated updates that caused AVG to complain.
I have to ask what is it that you have modified in the clients source tree to introduce/remove this false positive?
ClickOnce applications are based on the .NET Framework and are subject to code access security constraints.
Basically it prevents the client from messing with system or registry files, as it doesn't anyways. My guess is that by executing the setup.exe it violates that, therefore this needs to be done manually.