Download performance

[bob3160]

Hi, if you're willing to help, see: https://forum.avast.com/index.php?topic=237567.0

This is the link for the recorded data https://drive.google.com/file/d/1gxFUzQjtCZHSHB8iPVhPy_h_x-_Cj07N/view?usp=sharing

Reported to Avast. Unfortunately this is the start of the weekend so it may not get addressed till Mon.

[mhfrenew]

Hi, if you're willing to help, see: https://forum.avast.com/index.php?topic=237567.0

This is the link for the recorded data https://drive.google.com/file/d/1gxFUzQjtCZHSHB8iPVhPy_h_x-_Cj07N/view?usp=sharing

Reported to Avast. Unfortunately, this is the start of the weekend so it may not get addressed till Mon.

Thank you so much! I appreciate this a lot.

[jaroslav.nix]

Thank you for the report. We have analysed the issue and can confirm the slowdown is connected to HTTPS inspection by Avast. Unfortunately, it's not connected to Avast filtering itself but the common filtering framework in Windows OS (WFP). The very same impact would be visible in any other AV capable to filter the HTTPS traffic (by doing man-in-the-middle inspection). We are sorry about it, but the only way to workaround this is disable the HTTPS scanning.

[bob3160]

Thank you for the report. We have analysed the issue and can confirm the slowdown is connected to HTTPS inspection by Avast. Unfortunately, it's not connected to Avast filtering itself but the common filtering framework in Windows OS (WFP). The very same impact would be visible in any other AV capable to filter the HTTPS traffic (by doing man-in-the-middle inspection). We are sorry about it, but the only way to workaround this is disable the HTTPS scanning.

From a security standpoint, that's not a smart move.
Since virtually every website now is https, this would mean no more checking of websites.
Is another alternative being explored?

[RedFan]

There are more layers in an antivirus than https scanning, you should still be protected from other parts (shields).
Disable https scanning is not the end of the world!

Also read another article about this :

https://blog.vpn.ac/disable-https-scanning.html

https://support.avast.com/en-ww/article/Antivirus-HTTPS-scan-FAQ/

[bob3160]

There are more layers in an antivirus than https scanning, you should still be protected from other parts (shields).
Also read another article about this :

https://blog.vpn.ac/disable-https-scanning.html

Your link has no reference to Avast?

[Mr. Consumer]

Thank you for the report. We have analysed the issue and can confirm the slowdown is connected to HTTPS inspection by Avast. Unfortunately, it's not connected to Avast filtering itself but the common filtering framework in Windows OS (WFP). The very same impact would be visible in any other AV capable to filter the HTTPS traffic (by doing man-in-the-middle inspection). We are sorry about it, but the only way to workaround this is disable the HTTPS scanning.

From a security standpoint, that's not a smart move.
Since virtually every website now is https, this would mean no more checking of websites.
Is another alternative being explored?

Turning off HTTPS scanning doesn't mean Avast won't block HTTPS sites. Sites that are known to be malicious by Avast will still be blocked whether it's HTTP/HTTPS. Turning off HTTPS scanning means Avast won't be able to scan website contents, like scanning and analyzing scripts loaded by the site. But then again, if a site loads a third party script but if that third party host is present in Avast's database, then users will still be protected. Turning it off weakens the protection a bit but not a big loss for home users.
Many AV products on the market are against HTTPS scanning and will detect any such attempt as malicious, but that's another topic.

[bob3160]

Thank you for the report. We have analysed the issue and can confirm the slowdown is connected to HTTPS inspection by Avast. Unfortunately, it's not connected to Avast filtering itself but the common filtering framework in Windows OS (WFP). The very same impact would be visible in any other AV capable to filter the HTTPS traffic (by doing man-in-the-middle inspection). We are sorry about it, but the only way to workaround this is disable the HTTPS scanning.

From a security standpoint, that's not a smart move.
Since virtually every website now is https, this would mean no more checking of websites.
Is another alternative being explored?

Turning off HTTPS scanning doesn't mean Avast won't block HTTPS sites. Sites that are known to be malicious by Avast will still be blocked whether it's HTTP/HTTPS. Turning off HTTPS scanning means Avast won't be able to scan website contents, like scanning and analyzing scripts loaded by the site. But then again, if a site loads a third party script but if that third party host is present in Avast's database, then users will still be protected. Turning it off weakens the protection a bit but not a big loss for home users.
Many AV products on the market are against HTTPS scanning and will detect any such attempt as malicious, but that's another topic.

You're entitled to your opinion. It happens to differ from mine.
I'd still appreciate an answer from Avast to my post since that post was directed to Avast.

[Mr. Consumer]

Thank you for the report. We have analysed the issue and can confirm the slowdown is connected to HTTPS inspection by Avast. Unfortunately, it's not connected to Avast filtering itself but the common filtering framework in Windows OS (WFP). The very same impact would be visible in any other AV capable to filter the HTTPS traffic (by doing man-in-the-middle inspection). We are sorry about it, but the only way to workaround this is disable the HTTPS scanning.

From a security standpoint, that's not a smart move.
Since virtually every website now is https, this would mean no more checking of websites.
Is another alternative being explored?

Turning off HTTPS scanning doesn't mean Avast won't block HTTPS sites. Sites that are known to be malicious by Avast will still be blocked whether it's HTTP/HTTPS. Turning off HTTPS scanning means Avast won't be able to scan website contents, like scanning and analyzing scripts loaded by the site. But then again, if a site loads a third party script but if that third party host is present in Avast's database, then users will still be protected. Turning it off weakens the protection a bit but not a big loss for home users.
Many AV products on the market are against HTTPS scanning and will detect any such attempt as malicious, but that's another topic.

You're entitled to your opinion. It happens to differ from mine.
I'd still appreciate an answer from Avast to my post since that post was directed to Avast.

This is not about opinion. I just explained in simpler term what is HTTPS scanning. Some people misunderstand the term thinking turning off HTTPS scanning means Avast won't block known malicious HTTPS sites, which is not correct.

[DavidR]

<snip quotes>

You're entitled to your opinion. It happens to differ from mine.
I'd still appreciate an answer from Avast to my post since that post was directed to Avast.

This is not about opinion. I just explained in simpler term what is HTTPS scanning. Some people misunderstand the term thinking turning off HTTPS scanning means Avast won't block known malicious HTTPS sites, which is not correct.

Your comment about "Some people misunderstand the term", well that is a guess, but even then they need to be warned abut that potential risk.

Your simpler terms aren't that clarifying.  If you want to go down the malicious sites route, then all you really need is the Avast Online & Security browser extension as that has all of the same malicious web site detections as the AV (Web Shield).

The problem is expounded in sites that have many 3rd party URL links, none of which are being opened as such so malicious site checks wouldn't be done by either the AV os the AOS browser extension.

So there is risk, the sooner any malware is detected the greater the chance of it not getting to your system.

[Mr. Consumer]

<snip quotes>

You're entitled to your opinion. It happens to differ from mine.
I'd still appreciate an answer from Avast to my post since that post was directed to Avast.

This is not about opinion. I just explained in simpler term what is HTTPS scanning. Some people misunderstand the term thinking turning off HTTPS scanning means Avast won't block known malicious HTTPS sites, which is not correct.

Your comment about "Some people misunderstand the term", well that is a guess, but even then they need to be warned abut that potential risk.

Your simpler terms aren't that clarifying.  If you want to go down the malicious sites route, then all you really need is the Avast Online & Security browser extension as that has all of the same malicious web site detections as the AV (Web Shield).

The problem is expounded in sites that have many 3rd party URL links, none of which are being opened as such so malicious site checks wouldn't be done by either the AV os the AOS browser extension.

So there is risk, the sooner any malware is detected the greater the chance of it not getting to your system.

I already briefly explained the limitation in my first comment. Check again. My assumption is an appropriate one because most people don't know what HTTPS scanning is. The name itself isn't obvious enough. Keep in mind, most people aren't tech-savvy.
Avast's extension is bloated, so I wouldn't recommend that to anyone. It used to slow down webpage loading also. Don't know if that has improved. Besides, I see that after installing Avast, they don't offer you to install the extension anymore. It didn't offer me at least and I've installed Avast for testing multiple times. Or, are they offering it to Avast One's customer only? You may know about it.
Also, as I said in my other comment, Avast can block third party connection even without HTTPS scanning enabled. Avast's web shield is capable of doing that just fine. A browser extension that can also block third party connection is "McAfee WebAdvisor" (available in Chrome and Edge Store, but sadly not on Firefox). I haven't found any other extension yet that can do it.
Scripts loaded by a browser can't be analyzed without HTTPS inspection. If a website "A.com" also connects to a malicious third party domain "B.com" then Avast can detect that without the help of HTTPS scanning. But if "A.com" loads a malicious script "A.com/malware.js" then Avast can't detect it without HTTPS scanning. So, HTTPS scanning is useful in this scenario.
Hope this further clarifies it. I'm not saying HTTPS scanning isn't needed. It's an added security feature (though has some downsides too including some security and privacy concern). HTTPS scanning is also known as HTTPS inspection/SSL inspection/SSL scanning/etc.

[bob3160]

Enough already, you've made your point.

[mhfrenew]

Thank you very much, now I need to find how to disable it, my question at all is: are more people having this issue? but not reported? Its a bit weird to me that I was trying to find this problem around internet and didn't find anyone having the same issue when a network connection tried to reach 1 gbs

[mhfrenew]

Thank you for the report. We have analysed the issue and can confirm the slowdown is connected to HTTPS inspection by Avast. Unfortunately, it's not connected to Avast filtering itself but the common filtering framework in Windows OS (WFP). The very same impact would be visible in any other AV capable to filter the HTTPS traffic (by doing man-in-the-middle inspection). We are sorry about it, but the only way to workaround this is disable the HTTPS scanning.

Would you really recommend turning it off? I really don't want to be unsafe, also is there any guide around in avast to disable it in a safe way please?

[bob3160]

Thank you for the report. We have analysed the issue and can confirm the slowdown is connected to HTTPS inspection by Avast. Unfortunately, it's not connected to Avast filtering itself but the common filtering framework in Windows OS (WFP). The very same impact would be visible in any other AV capable to filter the HTTPS traffic (by doing man-in-the-middle inspection). We are sorry about it, but the only way to workaround this is disable the HTTPS scanning.

Would you really recommend turning it off? I really don't want to be unsafe, also is there any guide around in avast to disable it in a safe way please?

Turning it off lessen your protection. As already explained, the slowdown is due to how Windows handles https.
To turn it off do the following:
Open the UI select Menu (upper right)
Select Settings > Protection
Select Core Shields
Scroll down to Configure shield settings (center)
Select Web Shield > unselect Enable HTTPS scanning


I personally will leave that setting on.