Well well well...Kaspersky free with system watcher.This will give a tough time to other vendors.Considering the rollback actions is so effective.
I uninstalled KFA2019 because of too many errors on website's : ERR_SSL_VERSION_INTERFERENCE (in Chrome) There is a solution in chrome to disable TLS 1.3 but i don't wanna do that anymore! this issue is not solved in Patch B. Now 1 week with BD free and it runs realy stable and light (v 1.0.12.41) Issue K forum : https://forum.kaspersky.com/index.p...ving-host-delays-on-chrome-cross-post-merged/
it's funny how the forum thread you posted has a temporary solution that solve this even more hilarious how you went to bugdefender
That solution was not helpfull (disable TLS 1.3 is not that smart, because chrome is not that safe anymore), by the way solution or issue is still not solved in Patch B.... still have errors visiting most webpages! that other option "Do not scan encrypted connections." is also not the way it should be ! PS: its not bugdefender .... its Bitdefender , as i said this latest version works stable and light. I know you are a K fanboy , but issues like this aren't that funny to surf the web with errors. For now BD is working better and trouble free ... than KFA. https://malwaretips.com/threads/kaspersky-free-causing-err_ssl_version_interference.85177/
the solution is disabling the encrypted connection scanning, not disabling TLS. it is bugdefender, eventually you will realize it.
I know the solution is disabling the encrypted connection scanning... but i don't want to do that, you loose other functionality with doing this. I also have used BD free in the past many times and i know it was always buggy, but this version is now stable and no problem, i can't say that for KFA that give me more problems.... If BD starts doing stupid things i can always switch to another AV (not KFA) l You just try to push Kaspersky to people.
i would call this pushing away people from bugdefender i kinda agree that 2019 kaspersky products are bug ridden right now.
Why do you think they made Patch B ? to get rid of Bugs ! so why didnt' they solve this bug issue instead of advise people to disable TLS1.3 or disable encrypted connections ? If people install this KFA out of the box they will complain about these errors visiting websites (its very annoying) , people have to go into setting and disable things to make it work. And i was disapointed that this was not solved in patch b.
IMO this bug is kind of serious, it should have been already fixed by now, I wont use or recommend Kaspersky until they solve this problem.
It appears Avira doesn't scan https. https://blog.avira.com/evil-nasty-https-handshakes/ "The WebGuard component in Avira AV is scanning the unencrypted HTTP traffic and not intercepting or breaking the HTTPS handshakes (avoiding the horrible side effects)."
As a temporal workaround, just add the affected URLs to Settings -> Additional -> NetWork -> Encrypted Connection Scanning -> Manage Exclusions
It seems that this issue is resolved for me with a Google Chrome update. New version 68.0.3440.75 is out. Thanks @Minimalist https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html