I am truly sorry, but I have to “necro” this post: after restarting my computer, the problem came back (Is Kaspersky’s System Watcher process really excluded via the rule?). Please, consider that users are also human beings who can be aware and take steps by themselves on those matters, because their needs and requirements with their own PCs are not necessarily the same as yours.Īlso, try specifying the exact detection in Object adding * → *”detection”* On my part, there were no conflict with KAV whatsoever, and it should be my decision to make KAV leave it alone or (worse) whether I should use it, not yours. The problem is looking at users issues from a single standpoint, ignoring everything else, which is not a “customer-centric” approach and can lead to conflict of interests.
More over, there weren’t any conflicts with KAV, until the last update would flag it as a false positive (not even allowing its exclusion in the simplest manner).
I am not using its protection/privacy/antivirus features, which is only a small part of many of its functionalities (and can be easily disabled). Systemcare from iObit is an “all-in-one antivirus utility” that can create conflicts with Kaspersky, personally i don’t recommend this additional protection layer ….
0 kommentar(er)
