March 10th, 2017, 04:06 PM
Get rid of read only
Inexplicably, entire folders full of files have become read only. After unchecking that box in the Properties, I get a message that I need Admin privs (and I am the Admin) but after Applying the change, the files are back to Read Only.
It seems that a lot of people are having the problem but I haven't found the cause or the solution.
What must be done?
Thanks - rev
March 10th, 2017, 04:14 PM
What folders are you talking about? I suspect you're trying to access old XP style folders. The naming convention changed in Vista and has continued all the way up through Win10. The legacy XP style folders are just junction points, not actual folders. Kind of like shortcuts.
March 10th, 2017, 04:51 PM
No, this machine was Win 7 Ult from the beginning and I've been working on the files for months without the slightest problem. Then, all of a sudden, files are read only. I have no idea how they became that way and I found dozens of posts by people having the same trouble on various Windows versions.
The usual procedure to remove that attribute doesn't work. It appears to work until you try to save the file again, then it's back to read only. I found a workaround which is to save the file to a different format, a .docx to a .doc, for example, and then work with the .doc. When finished, save it back to .docx and all will be well but there might be a large number of files involved so while that method does work, it's not ideal.
March 10th, 2017, 05:00 PM
Hmm, ok. You mean that the files are read-only, not the folder itself?
What did you try so far? A quick google brought this up:
Did you do any antivirus/antimalware scans?
March 10th, 2017, 08:40 PM
I believe the read only attribute applies only to files not folders but either way, I did nothing to cause this.
I have not tried the 46 things that didn't work for anyone else. Just Properties, remove attrib, as Admin - which doesn't work.
I also tried it with an elevated command prompt but I get 'parameter not correct' (the folder is not on the C:\ drive)
March 10th, 2017, 10:09 PM
What is the folder path if it's not the C:\ drive? Can you give us more to go on?
Did you take ownership of the files first?
March 10th, 2017, 10:21 PM
Take Ownership is working for me - thanks a lot!
March 11th, 2017, 12:38 PM
Today, Take Ownership no longer works!
March 11th, 2017, 02:06 PM
Bizarre. Did you do AV/Antimalware scans?
You still didn't give us much else to go on.
March 11th, 2017, 03:04 PM
>Bizarre. Did you do AV/Antimalware scans?
>You still didn't give us much else to go on.
I swear there's nothing to go on. I was working on those files the day before and without virus scanning or new installations of any kind, the whole folder (and others) suddenly became read only. I was only slightly reassured to learn that it's happening to a lot of people but all the obvious solutions don't work.
Take Ownership was rocking for me yesterday, except I couldn't find a batch method. No biggy, right click and take it from the Context menu. It didn't take me that long but today I'm back where I started and TO isn't working.
The only thing that is working for me is to save a .docx as a doc, delete the docx and resave the doc as a docx. The result is a read/write file in the latest format - but it's a drag, and I have a lot of files.
March 11th, 2017, 03:12 PM
You said it's not in C:\, so where are the files?
You said you got a 'parameter not correct' error for attrib, but you didn't post the command you ran.
March 11th, 2017, 03:25 PM
March 11th, 2017, 07:21 PM
Here's what I ran but after the error I didn't persevere because this method hadn't worked for other people experiencing the same problem.
ATTRIB -R D:\Creative Projects\Cross Examination\Docs /S /D
March 11th, 2017, 07:31 PM
If you have spaces in the path, you must put them in quotes. Also you ran the command for the folder, not the files in the folder.
Try this instead:
ATTRIB -R "D:\Creative Projects\Cross Examination\Docs\*.*" /S /D
That's what I meant by giving us something to go on. We can't help you with syntax errors if you don't tell us exactly what you did.
March 12th, 2017, 07:57 PM
I've already fixed them all by saving to a different format but I'll keep that command for tomorrow because I don't think I've seen the end of this and I never found out how it happened. Thanks.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)