Towards the middle of the article it states (I know it shows Vista but same idea for XP):
Yes, it is more or less the same for XP. I say this for OTHER users who might want to know about this, not because of mine OS, which is Vista, not XP.
This may explain the additional file in the scan. When you unblock it I assume that the file with this additional information is deleted.
It is not really an additional file, but an attribute of the SAME file.
NOTE: For anyone reading this, please do not confuse this "attribute" with the more common attributes:
r: Read Only
s: System
h: Hidden
a: ready for Archive
If there is any other "additional" file, is only a temporary one, created for the only purpose of scanning it (by Avast). I don't know "who" is responsible for that "additional" file, Avast or the OS itself.
However, when I unblock the app, the file size does not change. I suppose you would have to know inside windows programming to know exactly how this file information is attached to the downloaded file.
Well, *I* as a simple user, don't really *need* to know anything about this "additional" file. I don't even know if there *is* an additional file, or is some kind of issue in the Avast report.
As I said, *if* there is an actual additional temporary file, then the Avast report is "technically" correct.
My first intention is to see if other users can reproduce this same behaviour, or is it only my own system.
My second goal is to report this issue to Avast devs, so they can check / test this by themselves. I am just a simple user. Avast devs, as Avast programmers, should know where to look at, and eventually decide if this behaviour is adequate.
Even if Avast devs conclude that this type of Avast report (
"double" "+1" number of "Tested files" ) is technically correct, maybe they want to review this issue eitherway.
What I mean is, from a UI point of view, there are no "additional" files being scanned.
Of course, this is no different from reporting a number of "Tested files" different from "ONE" when Avast scans a compressed zipped file which actually contains, say, 100 files inside. In this case Avast will not report just "ONE" file scanned, since it also scanned all the content of that zip.
To be clear, I don't have any problem with the "block" attribute and I understand what's all about. I just wanted to share what I saw in my Avast report. This MOST probably will not even be considered as an "issue".
TIA.