When I try to rename a file or folder in windows explorer nothing happens then I hear the dreaded failure ding.
I have no problem renaming files and folders on my external E drive just on the C drive.
What file and/or folder are you trying to rename. If it's System owned then it's protected and made hard to delete on purpose to prevent messing up the OS.
Maybe permissions?
There is also a tool unlocker.
Seems that the permissions prevent you to change things.
That is related to your account. R click on a file and read the permissions. Properties security.
If your not the administrator your account may be restricted.
Open the file through the program that created it and try to rename with Save as/
I have the same problem, and it is not a simple security problem. I am a member of admin group, and these are files I created. I have tried taking ownership recursively, changing read-only recursively, and giving authenticated users full control recursively. None of it works. In fact in a directory which has this problem, if I use explorer to create a new folder, it creates a folder named 'New Folder' and immediately dings and disallows renaming or deleting that folder.
I am, however, able to effortlessly do this with an external program.
I believe the source of this problem is that these files were copied in, a whole directory at a time, from an external machine. I think files that arrived this way have some special lock that I do not know how to reset. I.e., these are files from "untrusted source." Any ideas?
edit: I should add that on the machine these came from, there was no such problem, so it is unrelated to the path.
Thanks. --peter
Ok, I solved the problem.
Apparently it's a bug in explorer, or maybe a bit got flipped. I killed all running explorer processes, and restarted explorer, and the problem went away. That means it would also go away on reboot, presumably.
I didn't think I had previously had this problem, so I began to suspect explorer. Explorer is really a POS. It should at the very least not just "ding" without telling you why, not to mention many other shortcomings.
Did you kill "explore" or "explorer"? "Explore" is the Windows 7 interface, not the file manager.
I don't know what the process "explore" is, nor is there a process of that name on my win 7 machine. As far as I know, "explorer" in windows since at least xp is BOTH the file manager AND the desktop interface and window manager. ...A stupid design decision, imho, but that's how MS has chosen to do it. I also don't know what "Windows 7 interface" means. Maybe you mean the desktop UI, but I believe that's "explorer."
In any case, as I said, I killed all instances of "explorer," no more, no less.
--p.
Quote