unable to recursively remove read-only permissions

When I right click on a particular folder and select Properties from
the resultant menu I see that the Read Only checkbox is checked and
grayed out. I uncheck it, hit Apply, and select the "Apply changes to
this folder, subfolders and files" option. When it's done I right
click on the folder, again, and the Read Only checkbox is still
checked and grayed out.

If, in cmd.exe, I type "attrib foldername", I see that no permissions
are set on it. So why is the folder, in Windows Explorer, appearing
as though it does have the read only permission enabled?

yawnmoth wrote in

:

When I right click on a particular folder and select Properties
from the resultant menu I see that the Read Only checkbox is
checked and grayed out. I uncheck it, hit Apply, and select the
"Apply changes to this folder, subfolders and files" option. When
it's done I right click on the folder, again, and the Read Only
checkbox is still checked and grayed out.

If, in cmd.exe, I type "attrib foldername", I see that no
permissions are set on it. So why is the folder, in Windows
Explorer, appearing as though it does have the read only
permission enabled?


It's because the "Read-only" bit that you see in the Properties
window has a different meaning for folders. It means that the folder
has been customized. For a complete explanation from Microsoft, read
the following KB article:

"You cannot view or change the Read-only or the System attributes of
folders in Windows Server 2003, in Windows XP, in Windows Vista or in
Windows 7"
http://support.microsoft.com/kb/326549

HTH,
John

On Dec 19, 6:21*pm, yawnmoth wrote:
When I right click on a particular folder and select Properties from
the resultant menu I see that the Read Only checkbox is checked and
grayed out. *I uncheck it, hit Apply, and select the "Apply changes to
this folder, subfolders and files" option. *When it's done I right
click on the folder, again, and the Read Only checkbox is still
checked and grayed out.

If, in cmd.exe, I type "attrib foldername", I see that no permissions
are set on it. *So why is the folder, in Windows Explorer, appearing
as though it does have the read only permission enabled?

Some folders are like that on purpose so you don't shoot yourself in
the foot (break your system accidentally) by poking around. Windows
system folders for example.

For example the System Volume Information folder behave like you
describe and it is that way on purpose. You can still get into it,
but not using conventional methods that work on other folders. They
make it harder. Sometimes people are compelled to get inside the
mysterious SVI folder though...

If it is not an invasion of your privacy, what is the "particular
folder" and maybe we can be of more assistance.