1
In Windows 7 I had moved My Documents
to My D:\ drive and called it "Docs". I have since added other folders (for my wife and kids) so have renamed it with my name "Ciaran"
In both Windows 7 and Windows 10, the display folder name was "Ciaran" but the path is D:\Docs
when I look in the address bar of Windows Explorer.
How do I change the folder path to Ciaran i.e. D:\Ciaran
?
Interestingly if I rename it to Ciaran1 the path becomes
This is incorrect - even when renaming the folder the path remains D:\Ciaran1
but reverts to D:\Docs
if I rename it back to Docs.D:\Docs
but the desktop.ini for the folder changes the LocalizedResourceName
to Ciaran1
Presumably it is some registry setting but not sure where to look and it could take a while to find it.
PowerShell:
PS D:\> ls
Directory: D:\
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 05/07/2019 17:18 Folder1
d-r--- 14/01/2020 23:42 Docs
d----- 13/12/2019 23:18 Folder2
d----- 08/10/2019 08:53 Folder3
da---- 25/10/2019 16:33 Folder4
D:\ desktop.ini
[.ShellClassInfo]
LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21770
IconResource=%SystemRoot%\system32\imageres.dll,-112
IconFile=%SystemRoot%\system32\shell32.dll
IconIndex=-235
desktop.ini
for D:\Docs
aka D:\Ciaran
[.ShellClassInfo]
LocalizedResourceName=Ciaran
IconResource=C:\Windows\System32\SHELL32.dll,4
IconFile=%SystemRoot%\system32\shell32.dll
IconIndex=-235
Please be aware that Windows 10v1809 had a terrible bug where redirected folders were deleted on upgrade. While Microsoft is unlikely to repeat that specific blunder, make doubly sure that you have a regular backup plan of important files. https://redmondmag.com/articles/2018/10/09/microsoft-lost-files-issue-windows-10.aspx
– Christopher Hostage – 2020-01-16T00:35:34.7871@ChristopherHostage The issue you speak of has zero to do with the OP's question and does not apply. The issue in that article is specific to the first public build version of the v1809 update only and it only affected a minute amount of users who took the v1809 update when it was first offered, which Microsoft pulled from the update servers within a short time after it became available (v1809 was delayed for weeks afterwards) and the v1809 build version that resulted with this bug is no longer publicly available (this is not what the OP is experiencing). – JW0914 – 2020-01-17T12:20:02.313