Jump to content

3x0gR13N

Moderators
  • Content Count

    2,461
  • Joined

  • Last visited

About 3x0gR13N

  • Rank
    Forum is my faith

Recent Profile Visitors

15,191 profile views
  1. You'll have to contact official support via https://my.kaspersky.com/ Online scanners don't use cloud detection (UDS) which the product uses, hence the discrepancy.
  2. Is the problem that the notification appears at all? By default, update notifications are hidden. You probably clicked the Restore notifications option in settings hence why you're seeing it. You can restore default settings from the settings page to re-hide the notification.
  3. Your windows Event log shows multiple errors related to Disk 3 having the same ID as another disk which could be problematic: One such event was recorded right before a BSOD occurred on 4th November @21:02 Go to Start>type diskmgmt, locate Disk 3 and right click>properties (on the leftmost label "Disk 3" instead of the partition label) to find which one it is. If it's an external drive disconnect it and see if the BSOD still happens.
  4. One last thing. Instead of excluding the folder like before, exclude the processes from being monitored by any protection component. In this screenshot select Specify trusted application (disregard the red rectangle highlight), select Java and MySQL and enable all exclusion options.
  5. Sorry for the oversight, the exclusions window confused me... The free version shouldn't have those components working in the background to my knowledge. -Try pausing protection completely for a certain period from the system tray context menu or -disable Self-defense from additional settings. It's possible the processes are accessing avp.exe in memory for whatever reason There's one more setting there is to try but first check these two.
  6. As a troubleshooting step try disabling System Watcher. If it doesn't help, disable Application Control/Firewall as well. It's possible the behavioral monitor is journaling file modifications made by those applications and using CPU as a result.
  7. Patch C which should fix this issue is currently being beta-tested. There's no ETA when it's going to be released, but drop in the beta section if you're impatient for a fix.
  8. Also, for b] you can configure the real-time protection to scan on execution, on access or on access and modification in Advanced FileAV options.
  9. The way I see it is if you have a compound file (an archive or multi-layered executable file), for ex. file.zip->(file1.exe+file2.dll+file3.sys), which was scanned and all its contained files (file1.exe, file2.dll etc) marked by iChecker/iSwift; then if you have Scan only new and changed files enabled, KIS would only look at the info/hash of the "root" file containing all the rest (file.zip) without actually unpacking it and assessing whether the contained files need to be scanned since the last database update. A database update contains information on which files could possibly contain newly discovered malware detected with the delivered definition files so iSwift/iChecker data will persist longer than 2 hours which is the default DB update frequency and not be completely reset/cleared. In theory, Scan only new and changed files could lower your security since it would allow a dormant compound executable to be undetected if for ex. file2.dll was deemed malicious with a new update, but if you execute said compound file it will be unpacked and its contents scanned on execution. The help file doesn't go into details of the option so this is some conjecture on my part.
  10. Unfortunately you'll need to reinstall KIS and make sure not to enable all notifications in KIS settings>additional>notifications. It's possible that the upgrade overwrote this default setting. Since KIS adopted the Windows 10 notification system you aren't able to selectively disable notifications, as you've already seen.
  11. Configure KAV in Interactive mode by disabling Perform recommended actions automatically in Settings>General and click Allow if available in the popup warning that happens when you launch the game. For standard signature false positives a couple of hours to a day, for issues like this a couple of days.
×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.