WinXP SP3, Avast 7.0.1466
Personally I consider this problem as the only real weak point of Avast.
The file shield should not scan a file when renaming/moving it
(at least within the same partition of the same drive),
because only the path of the file is changed (a write operation in the MFT).
The content of the file is not written nor read by any application,
so avoiding this scan would not lower the security.
Rename/move is just what happens when a file is sent to the recycle bin :
the file path is changed so as to place it under '[Drive_Letter]:\Recycler\'
With EXE file there's the problem of the specific program icon which needs to be read inside the file.
But the problem also occurs with files with generic icons (for example a file with an unknown extension).
And the problem occurs repetitively (renaming A.blob > B.blob > A.blob) even with the transient cache active.
And the problem still occurs if I disable all scanning on 'file write'. (!)
In fact you don't even need to rename/move a file to trigger a file scan :
1. just begin to edit a file name (you are still editing it, no change yet done) and the file is already scanned
2. right-click a file to see its properties and the file is scanned EACH time, even with the transient cache active