I have never experienced this in over 16 years of using Avast and the Web Shield, mind you the https scanning hasn't been in play for all 16 years.
But certainly it has been present for many years and to the best of my knowledge it is a default setting.
In a conflict, removing one element of that conflict should stop it, but that doesn't confirm the guilty party, it only stops the conflict.
If it has only just started to happen, what else has changed:
What is your browser and what security add-ons does it have ?
What other security based software do you have installed ?
Can you give a url to a download you were making that failed and I can check it ?
The only recent change in the secure scanning side of the web shield related to a new standard in development for secure connections QUIC/HTTP3 and avast has also started scanning that for sites using it.