I solved it.
Running Diskpart in CMD did remove the read-only restriction, except it doesn't say it does. If I inspect any folder in the volume, it will say it's write-protected, but it's not so I guess it's fine now...
Running Diskpart in CMD did remove the read-only restriction, except it doesn't say it does. If I inspect any folder in the volume, it will say it's write-protected, but it's not so I guess it's fine now...
I can't remove write-protection on my Internal HDD.
It's not a permissions issue.
I have full access to my computer, control is not be the problem.
Whenever I try to remove write-protection on any of my folders, it just stays on as soon as I click the OK button or apply button. The box will untick, and I will close the window, but nothing changes, even if I see the folder claim that it's setting the attribute for all folders underneath the selected one.
I've also tried adding StorageDevicePolicies -> WriteProtect into Regedit, but that seems like something I'd do if the problem was an external drive, not an internal one. Regardless, it didn't work.
UPDATE:
I've tried running Diskparts "> Attribute Volume Clear Readonly" command now as well, and it says that it succeeded...
But it didn't, the read-only is still enabled. Diskpart even says read-only is not enabled on it, yet it still is! God why?! This is so fun.
A little bit at a loss here.
It's not a permissions issue.
I have full access to my computer, control is not be the problem.
Whenever I try to remove write-protection on any of my folders, it just stays on as soon as I click the OK button or apply button. The box will untick, and I will close the window, but nothing changes, even if I see the folder claim that it's setting the attribute for all folders underneath the selected one.
I've also tried adding StorageDevicePolicies -> WriteProtect into Regedit, but that seems like something I'd do if the problem was an external drive, not an internal one. Regardless, it didn't work.
UPDATE:
I've tried running Diskparts "> Attribute Volume Clear Readonly" command now as well, and it says that it succeeded...
But it didn't, the read-only is still enabled. Diskpart even says read-only is not enabled on it, yet it still is! God why?! This is so fun.
A little bit at a loss here.