Unable to delete read-only attribute folder - access denied

[Regine]

Hi,

I've been trying to remove quite a few (>10) read-only folders & their
subfolders by following the workaround instructions found at
http://support.microsoft.com/kb/256614, but I'm still unable to remove the
folders.

I created a new registry key UseSystemForSystemFolders and modified the new
value to Type 1 in Registry Editor. Then I tried to use the attrib command
prompt to change the read-only attribute by using attrib -r +s C:\V\Vids. But
it says Access denied.

What else can I do to get rid of these folders? Someone please help me out,
thanks very much in advance!

Sincerely,
Regine

 

[Newell White]

Hi,

I've been trying to remove quite a few (>10) read-only folders & their
subfolders by following the workaround instructions found at
http://support.microsoft.com/kb/256614, but I'm still unable to remove the
folders.

I created a new registry key UseSystemForSystemFolders and modified the new
value to Type 1 in Registry Editor. Then I tried to use the attrib command
prompt to change the read-only attribute by using attrib -r +s C:\V\Vids. But
it says Access denied.

What else can I do to get rid of these folders? Someone please help me out,
thanks very much in advance!

Sincerely,
Regine

Login to an account that has Administrator privileges on the computer, and
take ownership of the folders first, before trying to remove them.
If you are unsure how to take ownership, search the kb for an article on it.

 

[Regine]

I'm already logged in with Administrator rights..

 

[Michael Bednarek]

I'm already logged in with Administrator rights..

As Nigel wrote: "take ownership of the folders first".

 

[Jim]

Hi,

I've been trying to remove quite a few (>10) read-only folders & their
subfolders by following the workaround instructions found at
http://support.microsoft.com/kb/256614, but I'm still unable to remove the
folders.

I created a new registry key UseSystemForSystemFolders and modified the
new
value to Type 1 in Registry Editor. Then I tried to use the attrib command
prompt to change the read-only attribute by using attrib -r +s C:\V\Vids.
But
it says Access denied.

What else can I do to get rid of these folders? Someone please help me
out,
thanks very much in advance!

Sincerely,
Regine

As all folders in the NTSC file system have the read only attribute (and
which it is stated that XP ignores the setting anyway),
it is rather hard to see what the attribute has to do with your problem.

I have deleted lots and lots and lots of folders with no problems at all.
Of course, my unprivileged account owned the folders,
or I was using an administrator account.
Jim

 

[Michael Bednarek]

[snip]

As all folders in the NTSC file system have the read only attribute

That would be unsusual; they don't here. Some - yes, all - no.

(and
which it is stated that XP ignores the setting anyway),

The RO attribute is not ignored, it just doesn't mean what it says.

it is rather hard to see what the attribute has to do with your problem.
True.

I have deleted lots and lots and lots of folders with no problems at all.
Of course, my unprivileged account owned the folders,
or I was using an administrator account.

Even administrator's have (temporary) problems deleting stuff where they
don't have access rights. Taking ownership usually helps.

 

[haggis]

hi newell (shucks)

 

[dsfsdf]

(and

The RO attribute is not ignored, it just doesn't mean what it says.

the setting = UseSystemForSystemFolders. It has no longer any meaning on
Windows XP and above.

 

[Twayne]

Dont know if anyone is reading this, but I too experienced the same
problem.

I followed the instructions in Microsoft KB256614, and that did not
work. I also took ownership of the folder/files, eventhough I didnt
need to. The files and folder still show up as read only. I played
arround with the attrib command in the CMD window, and that was no
help......I need help.....Thanks

The read-only attribute on a folder doesn't mean the folder is read-only
to the user, as it does with files. Read-only files are deletable, and
so are folders UNLESS they are system files or have had their attributes
set to be system files. Windows won't allow you to delete a system
folder or a system file.
If it's a user-created folder/file then the user can change the
attributes to remove the read-only from the files but it's not necessary
to do so to delete t hem. You'll simply get an extra confimation
message asking if you really want to delete that read-only
file/filter/whatever.
But if it's marked as a system file, windows will not allow the
deletions.
Unless they've been marked as system files/folders, I know of nothign
that would prevent a user from taking ownership if he were admin and had
the privileges, and deleting them. Again, as long as they aren't system
files/folders etc.. Windows won't allow them to be deleted because
system files are what the system IS and may crash without them.

http://support.microsoft.com/kb/326549
You cannot change the read-only attribute on folders in XP.

http://www.annoyances.org/exec/forum/winxp/t1065875615

HTH,

Twayne`

 

[ChrisBedford]

Old thread and out-of-support OS but I thought I'd just toss in my 2 cents' worth on the offchance it might still help someone.

In fact I had this issue with Server 2003 (same code base as XP) which at time of writing is less than one year out of support but I know is still in fairly widespread use.

I tried all the remedies suggested here and in several other forums but nothing helped. The command-line utility "attrib" reported "access denied" attempting to change any of the attributes of 5 left-over files in a DropBox sub-folder, and nothing else was allowed access to them for any other purpose either (such as reading the files or taking ownership).

Eventually, suspicious of the lack of reference to this being a problem for anyone else, I rebooted the computer. Bingo, not only was the problem solved, but the files disappeared (which was the operation I was trying to achieve anyway). Maybe I could have achieved the same result by just suspending / restarting DropBox, but either way, hooray.