![]() ![]() I seem to be having some problems with AVAST and these problems occurred after I updated to the 4.8 program. I removed the quarantine items in SuperAntispyware. you (c)ould do some housekeeping and delete old backup/recovery/quarantine entries (older than two weeks or so), this will reduce the numbers of files that can't be scanned.īy examining 1) the reason given by avast! for not being able to scan the files, 2) the location of the files, you can get an idea of what program they relate to.įiles that can't be scanned are just that, not an indication they are suspicious/infected, just unable to be scanned. When you run scans with the above programs and you delete harmful entries that they detect, a copy is kept (in quarantine/vault/restore) in case you need to reverse what you did. (and avast doesn't know the password, or have any way of using it even if it did know it). such as AdAware and Spybot Search & Destroy) password protect their files for legitimate reasons . Many programs (usually security based ones. Here is a response from DavidR of the avast! forum , interspersed with a few comments of my own: If the avast forum can't help you, then i'd try a uninstall/reinstall. a thorough scan, including archives, would take the longest time. but scan time is dependent on so many factors, including processor (CPU) speed, disk speed (rpm, DMA), number of files being scanned, as well as the nature of the scan: avast offers a quick, standard, and thorough scan which can include or skip-over archives. In terms of an 11 hour scan, i'll admit that seems very long. I've generally found the people there to be very helpful/cooperative. If i were you, before trying an uninstall/reinstall of avast, i would post your problem at the avast forum: i can't say that's the cause of your problem, but it's certainly best to take simple steps to rule it out. (if you prefer, ) there was a short-lived build 1287 which had a bug in it. but I don't know if that's making any difference here.ĮDIT: the first obvious thing to check is make sure you have the lastest avast build, 1296. Removing the quarantined items from SAS should take care of the "avast can't scan - password protected archive" issue.Īs for the rest, I have no first-hand advice to offer: I have no problems starting avast 4.8 and opening its "chest" (avast's name for "quarantine"). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |