Files showing up as "Read Only" and unable to change this.

Our problem started by accesses the Windows 7 machine with a Windows XP machine.  We also had extremely slow internet.  I am not sure if either of those affected our situation.  We were accessing a database on the Windows 7 machine using the XP machine, and the files were actually not accessible (Not just grayed out).  Then trying them from the Windows 7 machine they were no longer accessible.  The slow internet seemed to effect our ethernet network data rate.  We have upgraded our internet, and have not been brave enough to use the XP machine with the database again.  The taking ownership instructions will come in very handy.

Hi Guys,

AFTER I UPDATED my Vista SP2 64-bit some 10 days ago ALL the files in ALL my drives also got "by magic" (another word to BAD CODE) a READ-ONLY attribute and thE attribute kept reversing back to Read-Only after I changed them (which took me a 14 HOUR work to PROCESS for my 16 TB of data!).

I then tried everything suggested on this post and nothing worked. In essence I had a QUITE HUGE collection of GARBAGE on my drives and lost DAYS trying to fix it. Because I use them for work I had to BUY a new laptop (NOT running any kind of Windows, of course...) in order to copy my files and keep on with my life.

Finally I was able (AFTER 10 DAYS OF HELL) to find a post somewhere else talking about a FREEWARE program (named "Attribute Changer" and available from its pubisher at http://www.petges.lu/home) and it was the easiest thing in the world to instruct the program to get rid of the Read-Only attribute of ALL my files in ALL MY DRIVES with only a few clicks (although it took some 12 hours for my computer to finish the process). 

And so, thanks to Mr. Romain Petges, [ who is: (1) NOT AFFILIATED with Microsoft, (2) NOT ON Microsoft payroll and (3) without any access to the proprietary code of Microsoft ], I was able to fix a SITUTATION CAUSED BY MICROSOFT itself and for which NO FEEBLE-MINDED MICROSOFT PROGRAMMER was able to take any interest whatsoever in the THREE years this post is open to fix the complaints of so many Microsoft's PAYING CUSTOMERS. So, now my DEFINITE solution to you is written on my nickname to this post! And it´s FREE.

The improperly formatted parameter is because the file name has a space in it.  The command prompt worked after I was able to rename the file (replaced the space with an underscore).  It asked me if I really wanted to rename a file that was read-only, and I said "yes". 

attrib -r class path.doc 

Parameter format not correct

attrib -r class_path.doc

no error message

So then I'm guessing that the attrib command is the same or similar as the chmod command in a POSIX OS?

I have Windows 7 Ultimate. A couple of weeks ago I had a big issue with some of my user permissions being changed (not sure how I did it but it happened) so i was unable to access programs and files, after some time with a MS tech on chat and a system restore (unsucessful), I just created a new user account and deleted the old one.

Everything seems to be working fine now, however before I created the new user account I copied some files I had on the desktop to a flash drive and put them with my new user desktop. The file property keep showing up as "Read only" even after unchecking the box and applying it just reverts when I close it.

This also happens when I create a new folder on the desktop, its default property is "Read Only" - why would this be, and how can i change it?

I GOT IT!!!! after 3 hours hehe

All those "attrb" never works with me, do this and it will works:

When looking at Folder Properties, the Read Only (RO) box will ALWAYS be shaded (With a Classic Theme it will be a grayed check).

This box does not indicate the current attributes of the folder, or the files it contains. Instead, it shows what action will be taken when you click Apply or OK.

• If Checked, the RO attribute will be set.
• If unchecked, the RO attribute will be unset.
• If shaded (blobbed) there will be no change.

As noted, this only applies to Files in the folder, it will not change the RO attribute on a folder. That has to be done from the Command Prompt.

Adding the Attributes column in Details view, or using the attrib command in a Command Prompt (or comparable command in VBScript/jscript/etc) is the only way to see the current setting of the RO attribute on a folder.

To take ownership of the drive and reset permissions:

Right click the drive, click Properties.

Click the Security tab.

Click the Advanced button (not the Edit button).

Click the Owner tab.

Click the Edit button.

Highlight your username.

Check the box for Replace owner on subcontainers and objects.

Click OK to close each dialog until it begins applying permissions.

If you get any errors, click Continue.

When done, close the Properties dialog. It must be closed and re-opened.

Right click the drive, click Properties.

Click the Security tab.

Click the Advanced button (not the Edit button).

Click the Permissions tab.

Click the Change Permissions button.

Add your account if needed.

If Administrators, System, and your account do not show Full Control for This folder, subfolder, and files, highlight each and click Edit.

Change the permissions to Full Control, and the Apply to: box to This folder, subfolder, and files.

The Users group should have three entries:

1. Read & Execute for This folder, subfolder, and files.
2. Create folders / append data for This folder and subfolders.
3. Special for Subfolders only

Select/add each one and set the Apply to: box as needed.

Use this list to set the permissions.

1. Full Control
2. Traverse folder / execute file
3. List folder / read data
4. Read attributes
5. Read extended attributes
6. Create files / write data
7. Create folders / append data
8. Write attributes
9. Write extended attributes
10. Delete subfolders and files
11. Delete
12. Read permissions
13. Change permissions
14. Take ownership

For Read & Execute, check #'s 2, 3, 4, 5, and 12 only.

For Create folders / append data check # 7 only.

For Special check # 6 only.

Everyone should have one entry shown as Special. It will have the same permissions as the Users Read & Execute except Apply to: is This folder only.

Creator Owner should have one entry shown as Special. It will have Full Control permissions and Apply to: is Subfolders and files only.

OK back to the Permissions tab if needed and check the box for Replace all child permissions with inheritable permissions from this object.

You'll get a warning that explicitly defined permissions will be removed. Click Yes to continue.

If you get any errors, just click Continue.

I'm amazed at how absolutely complicated and labyrinthine this is. Absolutely ridiculous, especially in a GUI. Sorry to put down Windows, but this can all be done in Linux with a very simple CLI command with modifiers and done. To make it apply to everything within, just add the recursive modifier.  Have this problem now with Windows 8.1, and it keeps not taking, but when I had the same issue in Linux, I just used chmod with modifier options and all done. Sticks and everything. So sad for the OS that the majority of people use.  Hey Microsoft, any thoughts on making this all more user friendly and not so complicated that it doesn't stick and we all have to go through this headache?