That’s because you have a file reputation setting enabled which is disabled by default. I don’t think there is any easy way around it and is only partially related to HTTPS scanning feature (because without it, it wouldn’t even be scanning this stream).
Thanks for that. Being that the Windows update is such an integral part of the operating system I feel that this needs to be incorporated into the File Reputation logic somehow. If Reputation is there as an option then barfing at the operating system standard functions makes it pretty useless really. Why bother having it at all if it’s next to useless.
The extra protection is nice but it’s too easy for the average user to block a critical program.
Windows Updates aren’t items that you AV should be questioning when received from the
correct source.
Maybe the source is what should be authenticated, not the files in the case of Windows updates. ???
Since those files apparently aren’t signed by Microsoft, that’s the main problem. Otherwise avast! bases its findings only on the file age in the cloud and since it’s new, you’ll get the warning. If the files were signed by Microsoft signature and were new, avast! wouldn’t alert you about them.
Understood. It doesn’t fix the problem that a feature of Avast is breaking the standard windows updates and it should not do this. If the files aren’t signed then Avast should be able to understand what is a legitimate windows update and what is not.