Exclusion list doesn't work, asc.exe still blocked.

[Ulmo]

Since the latest KAV update, Advanced Systemcare from iObit is getting flagged but it's a false positive (no update took place from iObit and I've checked with them). However, even though I've included the whole iObit folder into the exclusion list (thus along its subfolders), Kaspersky keeps on blocking its processes whenever I start ASC.exe. What's left for me to be done in order to oblige KAV to stop blocking this software?

 

[Berny]

@Ulmo Welcome.

Advanced 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 ….

[andrew75]

@Ulmo, try to set the path in the "Fiile or folder" field like this:

E:\Program Files (x86)\iobit\**

[harlan4096]

Also, try specifying the exact detection in Object adding * → *”detection”*

[Ulmo]

@UlmoWelcome.

Advanced 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 ….

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). 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).

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. 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. 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.

@Ulmo, try to set the path in the "Fiile or folder" field like this:

E:\Program Files (x86)\iobit\**

Also, try specifying the exact detection in Object adding * → *”detection”*

Thank you, I will try that

EDIT, yes, adding “**” to the path seems to have resolved the issue! Thanks again.

Note that I’m also using iObit Anti-Malware engine, which is a very good complement to KAV (using a good engine, unlike iObit ASC’s protection features that are useless). Hopefully you won’t flag it in future updates… xD

[Ulmo]

@Ulmo, try to set the path in the "Fiile or folder" field like this:

E:\Program Files (x86)\iobit\**

Also, try specifying the exact detection in Object adding * → *”detection”*

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?)...

I then tried to fiddle for quite a while with all combinations of andrrew75 and/or harlan4096 suggestions (with or without “**” at the end of path; starting from IObit subfolder or Advanced SystemCare  subfolder; “*” or “*Trojan.Win32.Generic*” or “PDM:Trojan.Win32.Generic*” -without quotes- in the Object box; by checking “All” or by selectively checking everything in the “Detected components” section)... But nothing worked.

In the following screen capture, I’ve included the message I get after Kaspersky has blocked the process (an error dialog box that’s shown above Kaspersky's report and exclusion parameters windows). It’s in French (as my Windows is), so here’s the translation:

For the file E:\Program Files (x86)\IObit\Advanced SystemCare\ASCFeature.exe
Windows cannot access the specified device, path or file. It may be possible that you do not have the appropriate permissions to access the item.

It appears after Kaspersky’s System Watcher has blocked some process. Note that Kaspersky’s System Watcher process was checked in the exclusion rule (either manually checked, either via the “All” selection)

Any suggestion (apart from “don’t use IObit...”), would be welcome.

[Ulmo]

I am truly sorry (also for the double post), but I have to roll back this post to a “Question”: after restarting my computer, the problem came back (It looks like Kaspersky's System Watcher is still taking place even if it's been checked out from the exclusion rule)...

I then tried to fiddle for quite a while with all combinations of andrrew75 and/or harlan4096 suggestions (with or without “**” at the end of path; starting from IObit subfolder or Advanced SystemCare  subfolder; “*” or “*Trojan.Win32.Generic*” or “PDM:Trojan.Win32.Generic*” -without quotes- in the Object box; by checking “All” or by selectively checking everything in the “Detected components” section. Note that it was actually )... But nothing worked, since it seems to actually be a matter of having Kaspersky still processing a System Check on the files (ASC.exe doesn't get deleted along some registry entries, and for that matter harlan4096’s suggestion works well).

In the following screen capture, I’ve included the message I get after Kaspersky has blocked the process (an error dialog box that’s shown above Kaspersky's report and exclusion parameters windows). It’s in French (as my Windows is), so here’s the translation:

For the file E:\Program Files (x86)\IObit\Advanced SystemCare\ASCFeature.exe
Windows cannot access the specified device, path or file. You possibly do not have the appropriate permissions to access the item.

It appears after Kaspersky’s System Watcher has blocked some process, even though it was checked in the exclusion rule (either manually checked, either via the “All” selection)

Any suggestion would be most welcome.