Cant delete file named rescache.hit when uninstalling?

[system]

rescache.hit files can be found in windows>rescache folder in various rcxxx folders and is normal.These files cannot be deleted or modified(not recommended imo anyway) unless ownership is taken.I guess thats why they cant be removed from the avast sandbox either unless ownership is taken of them.Logging on as administrator is not ownership enough.

[system]

@miscreant post:41

rescache.hit files can be found in windows>rescache folder in various rcxxx folders and is normal.These files cannot be deleted or modified(not recommended imo anyway) unless ownership is taken.I guess thats why they cant be removed from the avast sandbox either unless ownership is taken of them.Logging on as administrator is not ownership enough.

That makes sense. But then doesn’t that beg the question: Why would Avast put a file in its Sandbox folder that it then can’t delete? Since other posters have stated categorically that if it’s in that particular folder, Avast had to have put it there, why put a file in an Avast Sandbox folder that then can’t be deleted? Isn’t the whole purpose of having a Sandbox feature to be able to temporarily house a suspicious file, and keep it from infecting the whole system, and be able to delete that file if it’s determined that it’s a Trojan or a virus? Is it a possible bug? (i.e. that file should never have been put into that folder in the first place?)

[system]

@Charyb post:25

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. I couldn’t delete the sandbox folder and the directories contained within after uninstalling avast. You need to be logged on as an administrator and change the ownership and permissions. From what I can tell, the crash caused it and it hasn’t occurred since then.

Like I said, the sandbox crashed which created this condition. It hasn’t happened since. Since then, the devs have increased the stability of the sandbox with each release.

There have been several options given to remove the folders/files. All are good options. I removed it in less than 5 minutes by manually taking ownership of it and changing permissions.

You could always create a support bundle under the maintenance tab and upload it to avast. Instructions on how to upload are given once you create the bundle. Add your support ticket # to it.

CharyB,

I would :-* LOVE :-* to take ownership of the file, but as you pointed out VLK explains this cant happen as it owns by ‘SYSTEM’ and not Administrtor. Also, I never said this file was what caused the conflict between Windows Security Center and Avast to be reported as not running… BTW, the icon didnt show anything wierd, like the red X-sign, but when opened Avast clearly stated it was not running.

But it was never declared that this rescache file caused that, it was simply stated that I uninstalled and reinstalled Avast after seeing the security notifiaction. After, I went to verify that Avast was completly cleaned and thats when I ran into the ‘avast! Sandbox’ directory. I could not delete the directory and started having inconsitent problems. I started at the top of the tree and started deleting files inside it to find out what file was stopping the entire tree from being deleted/cleaned. At this point, Im sure the PC in question has been compromised due to other inconsistencies so Im sure Ill just be re-formatting it, most likely, but I may try to duplicate the problem. If it doesnt then Id bet a kick in the jib that Iv ran across an exploit. If it does duplicate, then Im sure that the information can be used by Avast to remedy either the ‘Uninstaller’ or the ‘aswclear’ tool.

Either way, something good will come of this, Im sure of it!!! 8)