Dollars to donuts it
was , in fact, errors on the card, as touched upon by
bob1033 and
Seto Prasetyo, even though the OP said he checked it for errors and it came back clean.
Regarding that little switch on the side : problems can and do occur with this of course, but it's worthy to note that people have had the exact same problem as the OP occur with card readers that have a little slot for plugging microSD cards in directly, no adapter needed ( like the one from
SIIG®, Inc. for example ).
As for "fcuk it" - type suggestions like chucking the card, buying a new one, etc… what can I say, they're not solutions unless you absolutely cannot be bothered to deal with little problems yourself no matter how simple the cure.
Seriously, BY FAR, the most likely reason is errors on the card, and these are correctable. I deal with this all the time, have for years. The problem is consistency, or lack thereof rather. Take two different computers, with two different versions of Windows, and with two different kinds of card readers—that's 8 possible combinations that can be setup—you might get 3 of those 8 setup combinations asking you right off the bat, when you plug the card in, whether you would like to scan the card for errors and fix them, meaning those 3 setups detected something was off about the card, and the other 5 setups will say nothing, just read the card contents and show them to you ( then when you try to do anything you find out you can't rename, can't delete, etc.).
But this issue of (correctable) errors on cards is definitely the most common reason for this problem. Because it is, my suggestion is to remove the card, and reboot the computer. Give it 5 minutes for it to finish booting completely and for everything to finish loading. Then plug the card in… chances pretty good it will detect the issue at that point and ask you if you want to scan/fix, like I said above.
Other workarounds that were suggested, like sharing permissions, do have their place, because they can help in certain circumstances, but logic should tell you that if it worked many times in the past without requiring special advanced settings, it should now as well, and it should tell you that there's a new factor that presented itself. That new factor
could be that for some reason, those share permissions were corrupted, changed in some way… but there is WAY more chance that's it's some logical and easily correctable OS-related problems on the card. Bad master file tables, indexes, security descriptors, what have you… the card will isolate itself from further damage until they're fixed. That's why, until they are, you won't be able to delete, or rename, etc.—you're attempting to write to the very areas that have become corrupted. The OS won't let you, but the OS can easily deal with these issues… as long as it can be made to
see them, lol.
for if it work good for you but not me because that hack tool that protect SD card it in the SD card that why it don't work that make only three solution left it.....(1) HECK THE HACK TOOL!!!! With eye to eye (2) buy a new phone(3)tell the police to let them case all those hacker. NOTED: the hacker are the only one who know the ways and they can fix your phone by use solution (1) it HACK VS HACK!!!!! ,but you should beware them that may not fix it they may only make it worse and stolen your money.
Facebook
Twitter
Instagram