does the vrdb take up room on your hd if allowed to generate? and how much does it take up if it does at all?
Hi hello2007!
As far as I am concerned the VRDB only takes about 1 to 2 MB of disc space…
So its almost not noticeable. 
yours
onlysomeone
so do you recommend letting it generate whenever i’m away from the computer?
The VRDB doesn’t take up that much room (but it will be more than 1-2MB) as it isn’t a full backup, but just records information on the files that it covers to be able to attempt a repair if a file becomes infected.
This is the VRDB’s integrity file, C:\Program Files\Alwil Software\Avast4\DATA\integ\avast.int, mine is a little under 9MB.
Oh, you’re right DavidR!
I just noticed that I didn’t let it generate yet (reinstalled my computer recently…)
Now, after the generating process the file has about 30 MB…
Sorry for my wrong information :-[
I although recommend letting it generate. 
yours
onlysomeone
It depends on how many executables (.exe, .com) you have in your system.
My VRDB takes 18,9 Mb
thanks guys so will it continue to eat memory as it keeps generating or is there a cap where it doesn’t go past. I know it’s a novice question but I have no idea so I’m wondering
It only runs once every 21 days (or if you run it manually), so like any program that is running it will ‘use’ RAM and that is managed by windows, once finished that RAM is released as normal by windows. RAM is a resource and as such is there to be used if you keep running low you should consider increasing it as avast wouldn’t be the only application to benefit.
Are you possibly confusing memory (RAM) with disk space?
Not me. 18,9 Mb of disk space, not RAM
Sorry, that question was for Hello2007.
No need to be sorry
no, I remeber when I had windows recovery active it ate up huge amounts of gb’s. I have vista and every week my storage space would decreaase by 3-5 gb so I deleted the windows recovery so I’m assuming vrdb is the same like that so will it eat up mb after mb & gb after gb by the week as the weeks add up?
I don’t think so. It will add up slowly, replacing old information with new as files are updated, and adding more information as system files are added. That’s my take on it, anyway. Mine is at just under 29Mb, and I’ve had Avast on the computer over 2 years. Tiny percentage of disk space, really.
is there an option where I can delete the added files that were generated if I chose too?
You can disable the VRDB generation. Right click the system tray icon, select VRDB, mouse through to the appropriate setting.
I don’t know whether it will damage the installation to delete the actual Avast INT file or not.
I would assume that a brand new install of Avast with the VRDB disabled from the start would have a non existent or very small INT file. That may be the way to go.
But I don’t really understand why you would want to.
If your disk is so full that 20-30Mb reclaimed is going to make a difference, it’s way past the time you should have acquired more storage.
It retains three copies (within that file), constantly dropping the oldest generation, so If your system is relatively stable, e.g. you don’t constantly add new software it will reach a level and will stay in that area.
However, if you are a squirrel constantly storing nuts (new software) the last of your problems with regards HDD space will be the VRDB integrity file but the amount of space taken by the software added. The avast.int file is a drop in the ocean compared to your software.
I am running XP Pro on a U160 18 GB SCSI HD, and space for XP is at a
premium.
Normally, I run with about 3 GB to spare. and am very careful of installing
too many programs on the drive. (To keep space demands to a minimum,
I maintain my desktop and swap files on other volumes.)
When I realized the value of the VRDB in a future recovery, I innocently
presumed Avast would not require a huge amount of HD space for the VRDB,
since the VRDB is not an actual “copy” of the critical files.
After reading assurances from various forum posters that the VRDB was only
a few MB, I activated the VRDB feature by specifying “Generate VRDB Now!”
That was a mistake. Previously, I had about 3 GB of headroom on my 18 GB
HD, but now I have 1.5 GB-- very close to a crisis with a Windows boot drive.
Actually, I am overdue for one, and that is why I post this message.
What I need now, according to my reading of previous posts, is to remove
the single file avast.int, then reboot, and perhaps find all my missing 1.5 GB
available as headroom, for the original total of 3 GB free space.
Already, I have removed the file (copied it to another volume, just in case).
Rebooted, checked that the file was gone, but found no change in available
free space-- still 1.5 GB.
From all appearances, Avast creates many files associated with the VRDB–
not all visible to Windows Explorer set to reveal hidden, even system files.
What else could account for the sudden, gross increase in occupied file space
after generating the VRDB?
SUMMARY OF WHAT I NEED NOW–
-
Which files to remove to eliminate the VRDB added bulk, without damaging
Avast (latest version)? I want the VRDB to have a minimal space profile–
letting me recover the 3 GB free space that I had before generating the VRDB
on-demand. -
If there is no way to do “surgery” on an installed Avast, is the simplest
approach to remove and then reinstall Avast? -
But even if I UNinstall, then REinstall, that still might leave some hidden files–
which is the problem. If I UNinstall Avast, and do not gain 1.5 GB more free
space, where should I look for the remaining VRDB files, to remove them?
. But even if I UNinstall, then REinstall, that still might leave some hidden files-- which is the problem. If I UNinstall Avast, and do not gain 1.5 GB more free space, where should I look for the remaining VRDB files, to remove them?
[font=segoe ui]You may try using avast! Uninstall Utility to completely remove avast.
You may optionally disable VRDB now since it could not keep up to most of the threats that’s why it would be dropped for the feature lineup in avast 5.
alphaa10… VRDB will die in less than one month… It’s an obsolete technology. You can disable it.