Inconsistent name change of "My documents" on the XP/2003 desktop

[Fla$her]

If one rename the "My documents" folder after cm_OpenDesktop, the same name will remain in the list, although the new name will be displayed in name editing mode or in the panel header after opening.
The name change itself after cm_RenameOnly or cm_RenameSingleFile affects only the registry key:
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\CLSID\{450D8FBA-AD25-11D0-98A8-0800361B1103}\(Default)

If there is no way to edit the name in the list, then I guess it's more correct to not allow these commands to be applied/used for it.

[ghisler(Author)]

Sorry, I just show what Windows returns when enumerating the the items in that folder.

Moderator message from: ghisler(Author) » 2025-05-05, 12:25 UTC

Moved to will not be changed

[Fla$her]

2ghisler(Author)
Please do not rush to refuse the proposed solution. Read what I wrote below.
You can prevent the change in the same way as you do for cm_OpenControls, for example.

[ghisler(Author)]

Sorry, I will not do this workaround. I check whether the item has the "can rename" flag set, and only allow rename when it has.
You can test this by pressing Shift+F6 on various items on the Desktop (will not allow to rename many things with Shift+F6).

[Fla$her]

I check whether the item has the "can rename" flag set, and only allow rename when it has.

But such a limited approach leads to flaws and bugs. It's bad.

[ghisler(Author)]

How should I know that a changed name isn't reflected in the list when the item reports that it can be renamed?

[Fla$her]

You can add a folder to exclusions.

You can also compare the text/title of the edited field (22 for WM_USER+50) with the current item name when editing is confirmed. If the item name has not changed, then restore the editable one.

[Fla$her]

2ghisler(Author)
Were you not satisfied with the answer to your question?

[ghisler(Author)]

I wasn't. Just because Windows fails to show the new name now doesn't mean that Microsoft wouldn't fix it one day.

[Fla$her]

The topic is related only to XP/2003, where Microsoft will not fix anything anymore.
If this hasn't been fixed even on Win 11, then why expect a miracle from Microsoft after decades?
And why should we care what might happen in the future, if it is logical to make exceptional fixes for outdated versions that we use?
Let me remind: Windows 10 support ends on October 14, 2025.