Folders renamed through Windows Explorer keep the original name
--------------------------------------------------
Rise to the top 3% as a developer or hire one of them at Toptal: https://topt.al/25cXVn
--------------------------------------------------
Music by Eric Matyas
https://www.soundimage.org
Track title: Darkness Approaches Looping
--
Chapters
00:00 Folders Renamed Through Windows Explorer Keep The Original Name
00:52 Accepted Answer Score 29
01:32 Thank you
--
Full question
https://superuser.com/questions/1148080/...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#windows #windows10 #tortoisesvn #windows10v1607
#avk47
Rise to the top 3% as a developer or hire one of them at Toptal: https://topt.al/25cXVn
--------------------------------------------------
Music by Eric Matyas
https://www.soundimage.org
Track title: Darkness Approaches Looping
--
Chapters
00:00 Folders Renamed Through Windows Explorer Keep The Original Name
00:52 Accepted Answer Score 29
01:32 Thank you
--
Full question
https://superuser.com/questions/1148080/...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#windows #windows10 #tortoisesvn #windows10v1607
#avk47
ACCEPTED ANSWER
Score 29
I eventually searched for all desktop.ini
files in my directory tree and removed them all. The issue got fixed instantly:
- Folders finally showed their actual name
- New renames actually happened at file system level
Such files contained entries like this:
[.ShellClassInfo]
LocalizedResourceName=This is the new name
... that seems to be a feature rather than a bug:
LocalizedResourceName
Specifies a resource module and the string ID to use as the name of the folder to display when viewed using the File Explorer or the Shell.
I don't have the faintest idea of how Windows ever came to the conclusion that I wanted to translate the folder rather than renaming it.