I had this and spent £129.99 on Avast Total Support when I tried to report the bug. They went into Control Panel , Programs, and did a Repair installation of Avast.
If the guy on the phone had told me there was a known problem with Avast and the Windows 10 Anniversary Update, then I could have done this myself. Unfortunately this forum seemed to be down at the time so I phoned Avast.
Most certainly. The problem is that if my setting are such as to protect me from most of my computer usage,
I stand to wind up with a failed Windows 10 update.
MY AV should also realize where the download is coming from and not simply block something because it deems what its being downloaded as new and not seen much
You don’t show an image of the avast detection, so it is hard to say what the reason might be.
Because of what some windows updates do avast could well think it suspect, more so when these updates come out, they are essentially unknown and some are unsigned.
Having the Heuristics and or Suspicious behaviour (HIPS) set to the highest levels could have an adverse effect.
Bob3160 I apologise for appearing to be trying to hijack your thread. The fault described does sound exactly like I was experiencing, and I was trying to help, since nobody had told me whether Avast Total Support were genuine or not. My original intention was to come onto this forum to report it when I found the bug, just like you have done.
Thanks Eddy for confirming what I suspected, that I’d been duped by a third party. I still don’t know how that happened as I thought I had found the number within the Avast program. The number I called was 0203 318 2676. Their website was ts(dot)avast(dot)com with their support being on eng-remote(dot)avast(dot)com
I’m now wondering whether the Reputation warning had been engineered by these shysters, in conjunction with installing a modification to Avast to remove any reference to the forum and to provide their telephone number.
If Bob3160 is getting the same warnings that started this for me, and I don’t have a Skylake processor so shouldn’t have been affected by the bug, then I’m puzzled.
Ah - just spotted that DavidR says Microsoft do sometimes use unsigned update files. Wish I’d known that before.
These files are being triggered in Avast because they are new.
The worst part is that the detection comes after the system reboots.
At this point, my only option is to turn the shields totally off, wait for the update to finish completely
and than manually turn them back on.
I am getting a warning and have the option to allow the file but, it’s very easy for the default option to occur.
If that happens, it would result in a corrupt install.
Thanks Asyn. Ticket opened. Interesting that the ticket system does show a product called Total Support, so I’m still not sure whether it was genuine or not. I’d better start my own thread when I find out what’s really going on.