Unbelievable !!! After 6 hours, after looking nearly every where.Tom give me the RIGHT solution Is it good to write them? What can happen if I do it wrong.
Robin2010 suggest that I should write these keys if I don't have don't know how to or if I should. I tried all the above suggestions: in cmd partdisk it says no on volume detail, I still did theĪttr clear readonly, it did not work.I did clear to both disk and volume.did not work.I change the letter of the volume, restart and then assign new letter.did not work, looked in the key registries but did not found the Policies folder under CurentControlSet Would like to deactivate that protection so I can do some changes but I don't find the option to undo it. On the ExFat I put my personal pictures and to protect them from delete or move actions by mistake i chose in Proprieties of the Volume ExFat to be readonly. I made 2 partitions, one NTFS and one exFat. Hello, I have an external HDD LAcie 500GB. Come on MS u got the resources to dig into this further and for once REMOVE this stupid error out of windows!
Is anyone at MS looking into this ? I mean a freggin error years back and to see it still active today makes you think no one really cares about this. I boot up linux for a week in a row and no errors, clearly its not a hardware error as it would show similar errors in different os'es and similarity in hardware of us users in here having this issue? Now imįorced to start command, and do all the diskpart commands, both for the drive and then for the volume.
What not and it started in vista.moved over to windows 7 and what we can expect from next MS release is that this issue will still be here? If i wanted to run command prompt os i would use bsd or some other unix distro, but i dont want that. This is so SILLY! its been what many years since vista came, then win7 and STILL this issue is a PROBLEM! Im starting to get seriously sick to do this EVERY TIME i start my computer, its insane! I had this issue before.many times.many re-installs.many
Annoying, but at least it's a simple workaround until a patch is released. Now the drive is no longer write-protected.
I went into Disk Management and changed the driver letter to G: then restarted, and Well, I had to restart the server for the first time since the last time I posted, and it did exactly the same thing where disk E (the RAID) said it was write protected again. Happen next time I have to restart, but at least its working for now. Restarted and drive still was write protected, but I changed drive letter back and now I can write to the disk again. Tried changing drive letter, but that didn't work, either. I did the "attrĭisk/volume clear readonly" anyway, but that didn't work. I tried doing the diskpart on both drive and volume, and both details listed "readonly" setting as no. I tried other fixes, such as reformatting the drive or resetting the RAID settings, but those only work until I have to restart it again. C drive is fine, but drive E (jmicron RAID 1, dual 2TB drives) comes up as write-protected every time I reboot. Just want to report that I'm having similar issues - we got a new Server 2008 r2 set up with File Services and Hyper V roles enabled. A reboot sometimes fixed it temporarily) I'll post a message if the problem returns. (Usually I had this problem after booting from power off state. It's been a week already since I had this problem so I hope this was the solution. While looking further on the internet, I've read somewhere this issue has something to do with a corrupted MBR of that hdd. This disk is actually a different disk so a new physical disk. Currently it says no on both disk and volume - It says "This medium is write-protected" when trying to delete or create a file on the disk. The ReadOnly attribute is set to no and clearing it does not solve it at all for me! Anyone other suggestions? Can you give some more info ? - ReadOnly attribute on both DISK as well as VOLUME - you say "disk gets write protected" - tell us where you see this, or how you know - are you using external storage ? - is this "disk" a partition on the same physical disk, or is it actually a different disk Please volunteer as much info as possible thanks, Edwin.
My second disk gets write protected, even when I have all rights.