tsoilihoi

Tech support responded that they are sending the problem up the chain. The Exclusion is location specific and if the executable(s) are move to another drive or location then another exception has to be made. I copied an excluded file to 4 different drives having turned off protection and when it went back on the original exclusion held but the scanned deleted the others to quarantine… This is a similar behavior as with Bit Defender… but Windows Defender, ESET and Webroot whitelist the name, only and the file can reside anywhere on the system. Why is this important? Because I store older program executables on a drive in a folder tree arrangement and when I moved that three of stored executables to a new drive things got nuts. These were trusted companies, but older programs and they were false positives. The companies involved were Winzip 20+, Winzip 18, Quicktime , an Ashampoo Office 2018 file presentation.tbl in the program files folder. The latter file had zero bytes. I tried to develop a workaround with the techs but nothing prevented detection if the storage folder is moved and its too much hassle to house keep false positives. Kaspersky was receptive to looking into this. I think its important to white tag by name to give the operator control of one’s computer. Something Kaspersky works hard to allow. At least a global exclusion that is not location specific should be offered and the decision made by the operator. This was a deal killer for me. Paul

I figure that either a file is excluded be the path and filename or it's filename across the system. I asked on this board because I could not get an expedient answer. The screen print requested off the filter in a folder seemed rather unnecessary and it's pretty clear that a file will be seen as adware if it's location is changed. It seemed like the problems are screened before an expert will come on board. Regardless. The files I spoke of are not adware and it was impossible to keep them on a drive. save for that Kaspersky has a great product but location based exclusion killed it for me.

I have no problem with the above. The issue is that if the excluded file is located say on drive D and then you should copy it to drive E, then when you work with the new copy on E, that new file will be quarantined. The excluded file is not given global permission when it changes location or it duplicated on the system. It seems to be location registered.

Suspicious file quarantined... An Exclusion seems to be made by the files location and not by file name regardless of its future location on the system… Let me explain. The executable for Winzip 20.5 is seen by many as adware. It is not. It is stored on my external drive for future reference or use. When scanned Kaspersky sees it as suspicious and quarantines it. I make an exclusion to the location… e.g. e:\programs\winzip20.5.exe and I can store it there without it being re-detected. HOWEVER, Even though I can copy it to another drive, when I try to access the copy on that drive or the other drive is scanned, the file will yet again be seen as adware and be deleted to quarantine. So the exclusion is governed by the location of the file and not cleared for use anywhere on the system by its filename. And as a result any false positive or allowed file, rightly or wrongly must remain in the current location or it will be seen as adware once its location is changed. I was advised to pause the antivirus and then move it. That worked until I turned the antivirus back on and it went to work quarantining the copies. The same thing happens with Bit Defender whereas Windows Defender and ESET exclude the filename from detection across the whole system regardless of location. This happens with any installation executable stored on that the antivirus considers risky; Winzip, Recuuva, Undelete and an older Quicktime file. Unless and until the exclusion allows the file to be stored or utilized across other drives, then the deletion to quarantine resumes with a suspect file (cleared by exclusion) if it is relocated. Windows Defender and ESET validate the file across the system by name and not location. I called multiple time and support wanted to escalate the case. It seems like a straight forward situation. It exclusions are location based, then the antivirus makes anything it considers adware, useless on the system. Any thoughts or work-a-rounds? Paul