G
Guest
I noticed that if i create a folder on root of C (drive formatted NTFS) the
read only attribute is set. Any attempt to remove the read only attribute
appears to work and I get no errors but when closing and reopening the
properties of the folder it is set back to read only. This behavior doesn't
happen on D drive (partitioned disk). I can however create/delete files in
the folder without problem.
In microsofts documentation on the knowledge base states that the FAT
attributes have priority over the NFTS permissions. Then my question is:
Why can't I remove the attribute on folders created in the Root? Why if the
FAT attributes superseed NTFS permissions and the read-only attribute is set
that i can create/delete files?
The issue arose when a client of mine copied files from a CD rom onto the C
drive and can't remove the read-only attribute as they were used to doing...
Thanks
read only attribute is set. Any attempt to remove the read only attribute
appears to work and I get no errors but when closing and reopening the
properties of the folder it is set back to read only. This behavior doesn't
happen on D drive (partitioned disk). I can however create/delete files in
the folder without problem.
In microsofts documentation on the knowledge base states that the FAT
attributes have priority over the NFTS permissions. Then my question is:
Why can't I remove the attribute on folders created in the Root? Why if the
FAT attributes superseed NTFS permissions and the read-only attribute is set
that i can create/delete files?
The issue arose when a client of mine copied files from a CD rom onto the C
drive and can't remove the read-only attribute as they were used to doing...
Thanks