Author Topic: Why does avast 5 no "vrdb, as avast 4.8  (Read 3247 times)

0 Members and 1 Guest are viewing this topic.

caki

  • Guest
Why does avast 5 no "vrdb, as avast 4.8
« on: February 25, 2010, 07:21:20 PM »
One of the best features avast 4.8 was vrdb, why is not transferred to avast version 5

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89061
  • No support PMs thanks
Re: Why does avast 5 no "vrdb, as avast 4.8
« Reply #1 on: February 25, 2010, 07:32:58 PM »
Because it is old technology that has depreciated with the new malware on the block that is very complex in terms of cleaning. There are other cleaning routines within avast and more in development.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

caki

  • Guest
Re: Why does avast 5 no "vrdb, as avast 4.8
« Reply #2 on: February 25, 2010, 08:04:00 PM »
I understand what you say, but what will happen when a new virus damage windows, avast later discovered the virus and outlines it, and after remaining holes in the system and system crash, vrdb was a good tool for recovery is system.
« Last Edit: February 25, 2010, 08:08:47 PM by caki »

caki

  • Guest
Re: Why does avast 5 no "vrdb, as avast 4.8
« Reply #3 on: February 25, 2010, 08:06:31 PM »
I understand what you say, but what will happen when a new virus damage windows, avast later discovered the virus and outlines it, and after remaining holes in the system and system crash, vrdb was a good tool for recovery is system.
« Last Edit: February 25, 2010, 08:11:48 PM by caki »

Online DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89061
  • No support PMs thanks
Re: Why does avast 5 no "vrdb, as avast 4.8
« Reply #4 on: February 25, 2010, 09:03:52 PM »
In the 6 years using avast and the forums I never once saw the VRDB even be used to repair an infected file.

The VRDB wasn't a recovery tool nor a backup tool, it retained a small piece of data about a file (not a copy of the file) that was covered by the VRDB (very limited file sub-set, see ~~~~ below) to attempt to repair an infected file.

~~~~
Trojans generally can't be repaired (either by the VRDB or avast virus cleaner), because the entire content of the file is malware, so it is either move to chest or delete, move to the chest being the best option (first do no harm). When a file is in the chest it can't do any harm and you can investigate the infected warning.

The VRDB only protects certain files, mainly .exe files, it doesn't protect data files or all files, it is not a back-up program, so there are going to be many occasions where repair won't be an option.

Only true virus infection can be repaired, e.g. when a virus infects a file it adds a small part to it, provided that file is one that avast's VRDB would monitor and you have run the VRDB, then it may be possible to repair the file to its uninfected state.

However, for the most part so called viruses, trojans (adware/spyware/malware, etc.) can't be repaired because the complete content of the file is malicious.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

tfcra

  • Guest
Re: Why does avast 5 no "vrdb, as avast 4.8
« Reply #5 on: February 26, 2010, 05:00:48 AM »
This may waste a lot of disk space and, sometimes it could not repair the infected files?