Problem with write protected folders on a harddrive in Windows 7'en

[mattiashawee]

Hi all.

I think this is my first post here, and i realy hope somone can help me with a realy anoying problem i have. It's not the first time i have had this problem and i can guess it's not the last either.

Now to my problem, .. last day i reinstalled Windows 7'en, .. i have a ssd disc i putted Windows on "C:" and i also got a "older" harddrive as "D:" in this case (with all program / games) and stuff.

My problem is what all my folders on my "D:" is write protected, and even IF i remove it and check again it's still there, .. HOW can this be.

I remember i have had this problem before and i manage to fix it then, but now .. with ALL folders write protected i fell screwed.

I know it has to do with the NTFS permissions and stuff (ownership) and all that but, 1 folder i can handle but .. now its seems to be my whole D: harddrive.

I have Googled about the issue and tried out the Windows cmd apps to change right's / attributes without any good success at all, soo now i write here to see if it's somone who can tell me what to do.

/M

 

[ex_bubblehead]

The write protect flag does NOT apply to folders. That flag on a folder simply indicates that there are one or more special flags applied to one or more files inside that folder. You cannot clear it. This is how it has been since Windows 7 was originally released. Forget it and move on.

 

[mattiashawee]

Hi and thx for ur answer, .. ok i didnt know that accouly. But how should i know if a folder is writeprotected ?. Why im asking is cose i installed Microsoft FSX and wanted to use it with an addons making clouds looks nicer, but the program seems to complain about it couldent write textures to FSX. And after that i saw the folder was writeprotected and i tried to remove it without success..:/

 

[mattiashawee]

I made an experiment also, and format a new hd to test on, .. made a folder and bam.. writeprotected without a file in it. Im realy confused right now.. :/

 

[ex_bubblehead]

As I said, it's NOT an issue that you need to concern yourself with. This is working as intended. The folder is NOT write protected.