Shebuka

(imo) no, release notes are a very high-level description of what was done, they have no low-level information, internet protection like software work on a very low-level, we are speaking hardware I/O disk access, tcp/ip packets inspection etc… KIS team just added official support do Edge (on 6th) and one week later (on 13th) Edge drops a HUGE update that changes everything… If there is such a huge patch note they can have communicated it in a timed manner to various antivirus teams for them to update. @Shebuka, I agree with with some of (your) analysis, however, when Kaspersky publish patch & version release notes, they don’t runaround to every other 3pty stake holder, apprising them of the changes, and vice-a-versa. I hear your point, and it’s reasonable too. But KIS is analyzing the traffic of Edge (and other browsers), not the other way around. If Edge changes their policies on cache handling (or whatever) it may be a good idea (never said must/required) to communicate this to interested parties. But if the fix is to clean cache and you are good to go... ?‍♂️ Terminology is hard… For me: high-level is the most human-like: In KIS Patch notes J “We have added the support of Microsoft Edge based on Chromium”/”Several application issues were fixed” there is no specification of what was done to do this; low-level is the nearest to code/machine language-like: Along the lines of “Fixed thread locking issue in internet protection module when accessing cache data ids hashed on disk with AES256 in a tight loop with mail protection module” (or even more specific). Your mileage may vary.

Shebuka, so does Kaspersky operate on Windows or the other way around? From Apr 13 until now, Kaspersky has time to analysis and rectify their incompatibility… otherwise, don’t claim to be compatible with Windows 10. Isn’t it? PS: It is highly likely that these changes are already communicated prior to their official build release. Kaspersky will already be aware prior to Apr 13. There is no excuse. Either officially say that Kaspersky is not supported on Windows 10 or rectify their software to make it compatible. How does this make any sense??? Windows 10 incompatibility? There is one issue, with one standalone application, only after the latest huge update, resolved by clearing the cache!?!?!? Never said Windows or Edge must do anything to adapt to other software… p.s. I’m also out, problem solved for me. Issues and bugs may happen. If I rage quit on any small issue I’ll be using pen and paper now, not a pc/mac.

(imo) no, release notes are a very high-level description of what was done, they have no low-level information, internet protection like software work on a very low-level, we are speaking hardware I/O disk access, tcp/ip packets inspection etc… KIS team just added official support do Edge (on 6th) and one week later (on 13th) Edge drops a HUGE update that changes everything… If there is such a huge patch note they can have communicated it in a timed manner to various antivirus teams for them to update. Correct, speaking of the timeline of Updates: Microsoft Edge Stable Channel releases: Version 80.0.361.111: April 7 Version 81.0.416.53: April 13 (HUGE features path notes) Version 81.0.416.58: April 17 https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel Wrong. I uninstalled and reinstalled Kaspersky (removing all settings) just this week. Reset my Edge browser (not just clearing the cache but all the settings). Same problem exists. Do you know you can uninstall the current version of Edge? I did. Same problem exists. KIS protecting - yes. Doing it correctly - No. Any functions or applications running under Edge holds the same certificate signature. Are you saying that if any browser adds a new code procedure or process, Kaspersky will deny execution? Kaspersky has to follow how Windows 10 or Edge operates; not the other way around. There are things like temp/cache hidden folders (where you can place eg. browser cache hash verification ids eg. by KIS) that are not cleared on typical software uninstallation and can be used again if you reinstall the software right away. Same goes for Edge. Things like Display Driver Uninstaller exist because when you uninstall graphical drivers not everything is cleared, and if you have any problem you may need DDU to scan your temp/cache hidden folders for more files to clean. I don’t know what’s going on with your system, but for me, resetting cache solved the issue (and for many others who have it solved and didn’t report any regression)

Microsoft Edge Stable Channel release Version 81.0.416.53: April 13. The same day me.kis.v2.scr.kaspersky-labs.com issue began. The changelog contains interesting things that possibly alter how cache is handled before vs now: Added support for Windows Information Protection (WIP), which helps enterprises protect sensitive data from unauthorized disclosure. Application Guard. Extensions support now available in the container. Policy updates: Enable globally scoped HTTP auth cache. (and many others)

Correct, speaking of the timeline of Updates: Microsoft Edge Stable Channel releases: Version 80.0.361.111: April 7 Version 81.0.416.53: April 13 (HUGE features path notes) Version 81.0.416.58: April 17 https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel

[cut] I think you are completely misunderstanding the problem here. It all started with a release of the latest version of Edge. My speculations here but, presumably, they updated some keys or certificates that validate the cache, they also implemented a procedure to update from old to new keys/certificates via a helper process. When you visit a webpage that has a cache on disk, Edge tries to update it with the helper process, this helper process was never seen before by KIS and the manipulation of the cache by an unknown process is considered as a malicious act (or a man in the middle attack) and is blocked. This process goes in an endless loop… So KIS is doing the right thing, it protects an unknow process from manipulating browsers cache. When we hit Shift+F5 we force to bypass the cache and fresh new pages that use new keys/certificates are written in the cache. No more unknown helper process that is trying to update the cache, no more hanging. And this is also why disabling Internet Protection, reload the page (and thus refreshing the cache with new content signed with new keys/certificates) and enabling Internet Protection back solves the issue. This could have been avoided if Edge developers communicated to antivirus providers of this change so that they can whitelist the helper process. edit: the actual workflow of what is hanging on what step can be incorrect, but you must get the idea... No, this problem doesn’t exist with Norton and AVG (which are the other two antivirus software I’ve tried). There’s W3C standards and every company that creates browsers either follows it to the latest standard, implements part of it or is still lagging in some earlier versions. Let me ask you: Does application developers follow Google specification for Android OS or we simply say that Android OS should accommodate application developers’ approach? Ask this to any software developers in OSX or iOS. You have to follow the platform’s rules and specification, not the other way around. You also have to understand that any helper process in Edge will have been duly signed. This is also how security apps like Applocker works. This is obviously an erroneous implementation by Kaspersky. PS: Why does this problem exist for downloading with Yahoo mail and Netflix streaming then? Why doesn’t the caching issue not happen when I conduct online banking or when I stream Amazon Prime or when I tried downloading with Onedrive? PPS: What’s this helper process that you mentioned? What’s the process name? You are again missing the point, it’s a cache modification issue. You Norton and AVG, either installed or launched after the issue, has no previous knowledge of cached pages before vs after Edge update. They have no ground to evaluate if there is something wrong with it. KIS is protecting you from malicious attacks. W3C has nothing do to with protecting you from an unauthorized cache modification attack... It’s like comparing HTML protocol with Elliptical Curves… There is nothing obvious about this issue. All previous updates of Edge worked perfectly, the last update screwed thing up. For me, it’s obvious that Edge developers have done something in the last update without considering all the ramifications that resulted in this issue.

[cut] I think you are completely misunderstanding the problem here. It all started with a release of the latest version of Edge. My speculations here but, presumably, they updated some keys or certificates that validate the cache, they also implemented a procedure to update from old to new keys/certificates via a helper process. When you visit a webpage that has a cache on disk, Edge tries to update it with the helper process, this helper process was never seen before by KIS and the manipulation of the cache by an unknown process is considered as a malicious act (or a man in the middle attack) and is blocked. This process goes in an endless loop… So KIS is doing the right thing, it protects an unknow process from manipulating browsers cache. When we hit Shift+F5 we force to bypass the cache and fresh new pages that use new keys/certificates are written in the cache. No more unknown helper process that is trying to update the cache, no more hanging. And this is also why disabling Internet Protection, reload the page (and thus refreshing the cache with new content signed with new keys/certificates) and enabling Internet Protection back solves the issue. This could have been avoided if Edge developers communicated to antivirus providers of this change so that they can whitelist the helper process. edit: the actual workflow of what is hanging on what step can be incorrect, but you must get the idea...

I was having the same issue with Hotmail on the latest Edge 81.0.416.58 (Official build) beta (64 bit) and latest Kaspersky Internet Security 20.0.14.1085(j). Hitting Shift+F5 fixed the issue.