Rename: TC cannot change the letter case of file/dir if need elevation

[Slavic]

This problem may have a long story, but it happens not often in practice and so may be forgotten.
If we want to rename a file or folder which requires admin (elevated) rights, after input a new name usually TC shows a warning message; we can choose "As Administrator" option, sometimes need to confirm this in UAC dialog, and the object will be renamed. However, if we use rename operation to change only the letter case of the object, TC refuses to perform this operation and keeps the old name. Explorer, on the other side, does this correctly.

How to reproduce:
For simplicity, we can use the C:\Program Files (x86) dir, which doesn't allow to create or rename anything without admin rights.
1. Create a new folder C:\Program Files (x86)\MyFolder in TC. Choose As Administrator, and it will be created.
2. Try to rename it in place (Shift+F6) to myfolder. TC will keep the original name.
3. Open the Explorer locally (right click on parent "..", choose first line in context menu). Then use F2 or Rename in context menu on MyFolder, input myfolder. Explorer will show the dialog informing about administrator rights, choose Continue. Renamed successfully!

Possible reason: TC attempts to rename an object (it fails because of lack of rights) and then checks the result using case-insensitive comparison. It counts that MyFolder and myfolder are the same, so no need to ask admin rights and rename. But if comparison shows the difference (e.g. MyFolder -> myfodder), it asks for admin rights and works as expected. If rename does not require admin rights, changing the letter case works correctly.

[petermad]

Confirmed.

Workaround: rename to something else like myfolder1 first and then to myfolder

[ghisler(Author)]

checks the result using case-insensitive comparison

That's exactly what I do, because some file systems like FAT32 do not support case sensitive renaming. Therefore I will not change this behaviour, sorry.

[Slavic]

That's exactly what I do, because some file systems like FAT32 do not support case sensitive renaming. Therefore I will not change this behaviour, sorry.

Sorry, but if this a fundamental design decision (whether users agree or not), then the current ability of case-sensitive renaming without elevation should be counted as a bug