This is probably already covered in previous posts and/or the Help file, but humor an old man …
When generating a fresh VRDB, does it ensure that the latest data “version” it’s saving for any given file is clean? I’d assume so, since there would be no point in saving data from an infected file.
Interestingly enough my VRDB generation duration (around 7 minutes) isn’t much different to my local disks, standard scan without archives (8.5 minutes), so it could well also be scanning those files covered by the VRDB.
I would have though that they would have to be scanned otherwise there isn’t much point in recovering to a possibly infected file. Since I do both on-demand scans and VRDB generation manually as part of my regular system maintenance, I usually do the on-demand scan first and then the VRDB generation.
Files are not scanned.
The three ‘last’ versions are saved. So, if the VRDB period is too short, you can store three infected/damaged file info there… :
???
The default period is 21 days.
Actually, they are. I.e. yes, infected files are not inserted into VRDB.
Thanks for the confirmation Igor.
Did this change lately?
I mean, I’ve read that the VRDB period couldn’t be so short that you’ll get all infected versions in it…
No, it’s been always like this.
But of course, you can’t guarantee that avast! detects this threat as soon as it appears (the VPS update might take a while).
Sure. Thanks Igor. I’ll change a little the explanation of avast4.ini file thread with this ‘new’ explanation in mind.