P: Batch renaming has stopped working in LC 10.3

Hi. I just updated my LRC to v12.1 but prior to that, I've been trying to clean up a real mess from moving images and catalogs from over 2 decades of photography from old Dell laptop to new Win 10 desktop PC with lots more storage, RAM, etc. The problem I started with was that after merging old catalog from laptop and newer catalog from desktop into one fresh catalog, not only are many of my photos duplicated, they are also stamped with a very long string of date and time data that I'm trying to strip out. No easy task. So in my efforts, my workflow to untangle this is to go through every folder in LRC and identify images that are related (could be 2 photos of same subject or hundreds), selecting them all (in Library module), and using the Metadata panel on the right, doing a batch rename (using mostly custom text + sequence # (starting with 1)). I have spent 4 whole days combing the internet to find a better, faster way to do this. No luck. What I'm noticing is that in LRC, my files show the rename is successful. However, when I go to my Windows Explorer, those same images reflect no change (old long string of date/time still exists). I did some digging and looked at folder properties (C:/users/myname/Pictures), and the whole folder is set to READ ONLY! What the...??? I unchecked this box, including all subfolders, and then did a Synchronization on the Pictures folder in LRC (right click on the parent folder, Pictures, in LRC folders panel on left) for good measure. Tried again, and IT WORKS this time. I just tested this out by renaming one photo in LRC, and then hit F5 (refresh) on Windows Explorer showing the image in the folder it exists, and the renaming was reflected correctly. Yay! I then tested it with all 20 images in the same folder, renamed them with a unique text plus a number sequence (start with 1), and then hit refresh (F5), and it updated over on Windows. Now I'm going to try with 100 or so images.

TL;DR: CHECK THE PROPERTIES on folders where the images are stored and ensure that they are NOT SET TO READ ONLY.  Hope this helps.

Hello!

On version 11.0, Windows 10, and I still have that problem.

Something which has worked for me - export as Catalog, and then rename - seemed to work ...

I am glad i'm not the only one having problems here - but what a completely appalling situation. This is creating so much stress for me ... just fix the bug already !!

So I have found a way around this glitch and not sure why it works.

I import all my files, either edit and work on them or do this next step then edit them.

Simply Export as original or .dng or .tif or or .jpg in super high res. Then Re-Import those files and then you can batch re-name as usual, seems to be working for me.

Same here, cannot batch rename, but only happens in folders with more than 100 images (so far).
Thanks

I am having the exact same issue and it is literally making my life very very difficult right now.

Good afternoon. I have the following problem:

I work with weddings and import files from different cameras. After syncing the files (adjusting the cameras time) I rename them all before starting to edit.
Example: João-and-Maria

After finishing editing, I rename again because sometimes I have to delete some photos during this process. Then I rename again.

But to avoid any problems, I change everyone's name. Example: Marriage-João-and-Maria

It turns out that in a catalog I'm editing, when renaming again, only about 70% of the files changed to the correct name. The rest got the old one.
And the strangest thing: it happened randomly. Files in the same folder are named differently even if they are sequential.

Example: The first 10 files, the 3rd and the 9th got the old name. And confusion continues throughout the catalog.

If I manually rename these files that haven't changed, one by one, they change. But the idea is to do it in batch (since there are 1000 files approximately).

What could be happening? Has anyone been through something like that?

Having the same issue rn. Just removed and re-imported all of the images and it's working again.