That doesn't make sense. Scan archives is *exactly* what the scan
archives setting is supposed to enable it to do.
Of course, if it is passworded it won't *shouldn't* work.
....and of course, a zip file cannot be infected as it is a data filetype.
Got an answer from AVG phone support. AVG will not catch an infected
file in a zip archive. When the setting says Scan Archives, it is
useless for finding crap inside an archive file.
Hmmm, ... still doesn't make sense.
What has to be done - I found on my own after hanging up with AVG, is
that one must have it set in the Shell Scan Settings to Thorough Scan.
That does it. The AVG person missed this.
I haven't used AVG for years.
Must be something peculiar in the way AVG names features.
Scan archives *should* scan archives, or the feature selection (Scan
Archives) should be disabled until the prerequisite "Thorough Scan" has
been chosen.
It is silly to have that feature selectable if it is not functional
until another feature is also selected.
[...]
Anyway, I just changed my mind and thought I'd try their support -
which didn't catch the problem, and in itself was thoroughly
misleading.
Problem solved.
So, am I right to assume that it was a difference between the on-demand
context menu (shell extension/right click) that wasn't scanning within
archives until you set the "Thorough Scan" on the shell extension scan?
Did the "Scan Archives" setting in the regular scheduled full scan work
as designed all along and it was only the right click scan a file that
didn't?
You're right, it does sound misleading. If I right click and choose to
scan an individual file - it *should* do its best most thorough scan by
default.
