Windows 10: Cannot get folder permissions...

Hi, I removed an old Windows 10 user account, but its folder in C:\Users did not disappear. When I investigated, I found that there is a folder inside that I just cannot delete (in spite of being Administrator):
C:\Users\test131\AppData\Roaming\AVAST Software\Avast\Cache

I searched the web for solutions but they were all about changing the permissions in the Properties->Security Tab. However, I cannot even do anything there:




If I click the "Advanced" button, I get this:




So I seem to be stuck.

Does anybody know how to solve this by means of legitimate Windwos operations. That is without any third party software or boot images?

Here is a full video of the behaviour:
[youtube]0MvFKF847Os[/youtube]

:)

 

Permissions

Cannot get permission to open "my Documents "folder in Windows 10

 

Windows explorer in window 10

I tried the above but no luck, I still cannot open my files. I wonder if this is a folder or file permission issue, if so how do I change permissions so that all intended users get full permission. But then why cannot the computer not find my file?

 

We have a tutor and a tool for this so you can take ownership Add Take Ownership to Context Menu in Windows 10 - Windows 10 Customization Tutorials

 

In your second screenshot (the 'Advanced' one) click 'Change' next to the owner. Make yourself the owner and you can give yourself 'full control' permissions. Then you'll be able to delete it.

 

The "Change" you are referring to is greyed out...

 

Try taking ownership of the \AVAST Software\ folder first.

 

There may be a much simpler solution than permission changes. Restart your computer, and then see if you can delete the user directory you are trying to delete. It may still be in use because it may have been in use at one point during your current session. That has worked for me in the past when struggling with deleting user directories after removing the user through the account management interface.

 

I am already owner of all parent folders.

 

Already tried that, even while disabling AVAST. I deleted that user months ago.

 

A very good suggestion. If that fails, start at the top and take ownership of the deleted user's folder. Inherited permissions may be preventing you taking ownership lower down.

 

Have you tried deleting the directory through the recovery environment?

• Use Advanced Startup Options to choose Command Prompt
• Type Code: C: dir[/quote] to see if the C: directory has a Users directory. Keep trying other drive letters until you find Users
• Assuming you find it in the C: directory, try Code: rmdir /s /q C:\Users\test131[/quote] Substitute the appropriate drive letter for C: if need be

 

Try taking ownership of the full directory tree for that user. Even if you have already done this, Id suggest doing it again.

When you click on change and change the owner, you type in the name for your account and click OK (or add, Im not sure right off hand). When you come back to the advanced permissions screen, you should have a check box saying something to the effect of "Also apply changes to all containers and objects within these containers."

Click apply and let it change owner on everything within that tree. Then you go back to the folders you were trying to delete. You may have to go back in and add seperate permissions for yourself and disable inheritance.

 

• to see if the C: directory has a Users directory. Keep trying other drive letters until you find Users
• Assuming you find it in the C: directory, try Code: rmdir /s /q C:\Users\test131[/quote] Substitute the appropriate drive letter for C: if need be

[/quote] Thank you all for your suggestions. But Xilink's method solved it for me. Thanks a lot!

I was just curious, if there had been a way to "regularly" delete the directory without rebooting or anything. But I'm glad it worked quite easily with this Advanced Startup.

 

Yes, the 'nuclear option' is to boot into another OS that doesn't care about your OS's permissions. The Recovery Environment is a good one to use, as is the frequently suggested idea of booting from a Linux Live USB.

Glad you got it sorted.