![]() Instructions on how to upload are given once you create the bundle. You could always create a support bundle under the maintenance tab and upload it to avast. I removed it in less than 5 minutes by manually taking ownership of it and changing permissions. There have been several options given to remove the folders/files. Since then, the devs have increased the stability of the sandbox with each release. Like I said, the sandbox crashed which created this condition. From what I can tell, the crash caused it and it hasn't occurred since then. You need to be logged on as an administrator and change the ownership and permissions. I couldn't delete the sandbox folder and the directories contained within after uninstalling avast. Quote from: Charyb on March 08, 2012, 06:01:47 PM How did you decide that rescache.hit is the problem? I had avast crash and it left a sandbox folder with multiple directories on c drive. Is it time for me to STOP sharing my great opinions of Avast with the veterans I meet with each month, as once its bought we are left to mostly or own devices and knowledge? One is simply having to re-state and put into slow, childlike phrases to get ANY help at all. I dont get it, when the product is so above the rest, why the support seems the same if not worse. Is there a problem with these agents and their comprehension? Is it something I said? Is Avast simply biased against the country of orgin? These are files CREATED by Avast, apparently. I have files that were NOT cleaned up in by unisntalltion OR aswclear (posted on the forum: ). If an ACTUAL Avast team member gets this, please read the following ticket THROUGHLY (Ticket #OXW-598354). It seems as though they read the first part and then decide what the rest 'must' be relaying. They continually combine tickets that have NOTHING do with each other. I paid for the product and expected the same top notch support that the software demonstrates. However, the suport via the Support Ticket site is less than sub-standard. Quote from: UserA789 on March 07, 2012, 05:13:09 PM I have been dedicated to Avast for a number of years. Are you saying that since it's an Avast generated folder, it's safe to remove, if at all possible, without harming the OS in any way? So that using a program like File Assassin might work? (if in fact the file he boiled the delete problem down to is actually the file that's keeping the folder from being able to be deleted) Because I know that File Assassin comes with Malwarebytes, and a lot of folks have Malwarebytes on their systems already. Have you ever found that that particular folder would not delete after running an uninstall?ģ. Do you have the Avast sandbox folder on the %system% drive that he has on his?Ģ. So you're suggesting that the one option available, in lieu of using the Linux Live CD, is to re-install Avast, then run the aswclear uninstall utility afterwards, and see if that removes the now orphaned folder? Does he need to install the same version of Avast that he originally installed, or will the current version do? And are there any particular settings in aswclear that will help to assure that the folder in question will be removed? (And would Revo uninstaller in aggressive mode be an option as well?)ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |