And for possible further clarification:
1. Do you have the Avast sandbox folder on the %system% drive that he has on his?
2. Have you ever found that that particular folder would not delete after running an uninstall?
3. 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.
Thanks.
These are very relavant things that Im surprised no one has goten out of what Iv posted. Thanks you. (1) No one has came and said they have this folder install on thier machines. (2) No one has confimred that it gets 'special permissions' that are not 'admin' (as stated even by the "hidden admin" account) changeable even after uninstalltion occurs. (3) If removal of this will cause system instability, then this needs to be stated, so I can not worry about that and just re-install Windows.
Well, I recognize that he wonders why the uninstall utility fails to clean it. As far as that goes, the "Why" is more or less pointless, the fact is the removal tool failed to remove it (I wonder if he has tried running it twice?), but yeah, the tool not doing a full clean up should probably be looked at.
But he asks;
I think it needs addressed how and why it got created, and apperntly by Avast! (if not, why it would be in an Avast! directory).
Thats the part I was confused over, it is from the Avast! sandbox, created by Avast!, and anything inside it is from running something sandboxed.
It probably wont go away easy, do to permissions.....you could as mentioned, try a Live CD to remove it but he wont because "nothing is unhackable", I have no idea what that means either, in relation to using a Live CD. The other option is what was mentioned by Support to him....installing Avast! again will let you get rid of it, as it is an Avast! file, the problem with removing it is that he uninstalled Avast! so no one is left in command of the file, its an orphan.
The first part is answered above. Secondly; I have tried running it twice... first thing I did actually. To the LiveCD query, why should I have to use something else, other than my original OS, to get rid of it. If I cant, then wouldnt you agree this needs adjustment within Avast development? Logic would dictate it does. Not to mention, Iv had issue with my last DL of the LiveCD, so Id like to just keep it to Windows.
Thanks for getting clarification.
Thing is the OP does not seem to want to be rid of Avast!....he wants the file gone, then he wants to re-install, but that is most likely not needed. Those files are probably there so things can run sandboxed, because when sandboxed, an application is cut off from parts of the system it might be dependent on, so virtual copies are probably needed in some cases.
I have already re-installed Avast!. I wouldn't think of using anything else... yet. That does not lessen this needing attention and fixing. I even tried to get rid of the folder by uninstalling again (along with a third attempt using aswclear)... by trying to change the settings for the 'Sandbox' folder; as it specifically states it will delete the orginal if changed... trying to modify its permissions from actual administrtive account.
Nothing has worked successfully, but more over I think this needs attention from the Avast developer team, along with a fix 'tool'.