Can't rename file or folder in Windows 10
Question
Answers
All replies
-
The marked answers here seem all inadequate to the issue in the title as I experiment it on my W10 PC. So, this issue is not solved for my W10 PC.
Experimenting apparently the same issue on a clean W10 x64 install, I also note that, after creating a new folder, the process refused the folder name I wanted to give (so the new folder remained called "New folder"). I note that the folder's properties window shows as Attributes "Read-Only (Only applies to files in folder)", the corresponding box being fully dark (not grey or white).
In fact, not doing a lot of further checks, most folders on the W10 HDD of this PC have this attribute set at Read Only (this PC is a simple PC, just W10 on it just installed & MS Office, nothing else), which appears absurd to me.
This read only "false" attribute introduced in W10 is another bug that affects all my machines with W10 on them. It is not fixed. However, it is also quite "old".
I wonder if there is a link between this "false" "read only" attribute and this refusal to rename the folder.
I renamed the folder easily using an old "DOS" command as suggested & it worked (in command mode, go on the specific drive where you need to do this and type "ren 'old' 'new'" where 'old' is 'New folder' and 'new' is '<whatever new name you want to give>'.
I have no clue why the command mode worked and file explorer did not work.
I am used to buggy programming but some basic testing & quality checks seem seriously missing @Microsoft.
As noted by others in this forum, such issues makes Windows 10 barely workable, so I suspect MS will come with fixes. It is Sunday, I can loose time at home, but what in professional life? Impossible, I would have to roll back to W7 immediately.
These serious issues are not new. So, it comes to me as a surprise that they have not been fixed much earlier.
I may investigate the possibility to use another file explorer as the one mentioned below. However, the proposed solution below does not respond to the issue in the title of this thread as I experience it.
I downloaded Xplorer2 from http://zabkat.com/x2down.htm . It shows exactly the same problem, which is somewhat reassuring. I confirm it was NOT a solution for the issue mentioned in the title for me, so I cannot advise others to go down that route.
On my PC, it gave ALSO (as MS File Explorer) when creating a new folder this astonishing error message attached below (astonishing because the text of this error message does not look relevant at first sight).
Also, there is another fix mentioned below that is to delete in the regisry the following keys:
{2112AB0A-C86A-4ffe-A368-0DE96E47012E}
{491E922F-5643-4af4-A7EB-4E7A138D8174}
{7b0db17d-9cd2-4a93-9733-46cc89022e7c}
{A302545D-DEFF-464b-ABE8-61C8648D939B}
{A990AE9F-A03B-4e80-94BC-9912D7504104}Going to that extreme is perhaps fine for other people mastering the Windows 10 OS environment. I am a simple Advanced user.
I could easily technically do it (delete these keys in the registry with all due precautions) but I would not know why I am doing it and what could be other knock on effects, etc.
I would have to research first to which folders these keys belong. So it would take me more time (I am just a prudent amateur). Not knowing, I would not advice others with same level of expertise to go that route unless this is done only for experimenting (no risk of consequences of potentially degrading the registry).
I am not sure it would fix exactly the exact same issue as the one I have (the one in the title of this threat) in the specific setup in which I operate (note that I have a theme with one fixed picture; I mention this as this characteristic was mentioned by others - I have no clue if this is relevant).
I can only support other forum members views that this bug requires
1) MS more urgent attention from W10 support team,
2) a reason why it happened giving some confidence it is really fixed,
3) a precise KB relating to the fix.
Too much time lost to my taste.
Good luck.
- Edited by acontrario Sunday, July 24, 2016 4:08 PM
