Total Security - Scan Questions

johnrs

I have a bunch of questions regarding Total Security scans. Support has been unable to help me with these so far, so I thought that I'd see if anyone here could help me.

=== Antivirus Menu

Why do Quick Scan and System Scan show up twice? Is there anything that can't be done from the second appearance that can from the first? After all, a Custom Scan only shows up once.

=== Scan logs

I have file, folder, and file extension exceptions. The scan logs, in "Scan options", show both "Scanned extensions" and "Excepted extensions" are "not configured". Are these referring to something different?

=== System Scan vs Custom Scan

I created a Custom Scan which I wanted to be the same as a System Scan, but ignoring one additional drive which I have. It runs fine. If I dismount the additional drive, the System Scan and my Custom Scan (all options on) should be doing the same, exact things.

But running both scans, multiple times each, the System Scan consistently takes about ~50% longer, and finds 74K more files, than my Custom Scan. Why? Is there something that the System Scan does that a Custom Scan cannot be configured to do?

=== Flakey Behavior

Using System Scan, I've seen an archive file with a Trojan (false-positive) get caught when Scan Archives is disabled. Even stranger - The same archive was on 2 locations, on each of 2 drives, but the scan only caught it on the first location of the first drive, and on the second location of the second drive. Then, after replacing the file from an offline backup, and rescanning just the first drive, the Trojan wasn't caught at all.

There was also another, unrelated, archive file with a Trojan (false-positive). The scan caught it on one drive but not the other.

The two drives were my main system drive, and an exact, bootable clone (updated nightly) of it.

So, the behavior was not only different when running the scan again, it was also different for the two identical drives during a single scan.

Why is this?

With Scan Archives disabled, does scan perhaps do some small percentage of archives anyway, hoping to get them all done over multiple scans? If so, that would explain part of what I saw.

=== Archives

During my tests, I had no problem restoring individual files which were quarantined. Archives, however, all refused to restore. The error message was always "Failed to find the specified path." Which path is it referring to: quarantine, original location of the archive, target location for the restored archive?

I assume this refers to the destination path, since the path choice was limited to my user directory, which did not include the path to the failed file.

What am I doing wrong, and what if I'd like to restore the file to its original path or elsewhere?

=== (end)

Thanks in advance for any help answering these!

johnrs

Followup: Of the original 8 questions…

I've edited the original post to remove 4 of them. After a few tries Support was able to answer them.

Of the remaining 4: The first is a confusing design decision. The 2nd is a bug, and has been reported. The third is undocumented behavior, but not a problem. The 4th is a bug which prevent Archives from being restored. Support hasn't figured this out yet.