Skip to main content
MPeter1975
MPeter1975
Participant
March 27, 2023
질문

Lightroom Classic can't batch rename photos on a special drive

  • March 27, 2023
  • 1 답변
  • 1142 조회

Hi!

 

I know that what I try to do is not officially supported, but I still can't understand what the problem is and if I could workaround somehow.

System: Windows 10 Pro, 21H2, build 19044.2728 (but i'm sure nothing to do with Windows)

 

Problem:

When I select photos from drive P and try to mass rename them I get the Problem with Renaming Files error window with Some photos will not be renamed because they are missing or not writable. No matter if I try with one or many photos, all are listed to have the problem above.

The funny things:

  • I can open any photo with the Show in Explorer menu
  • I can rename any photo by modifying the file's name in Metadata group's File Name field
  • During the above operations Windows' audit log show successfull credential check, file handle request, file open, file close, etc.
  • During mass rename neither failed nor successful audit log events are logged
  • Mass rename works outside of drive P

 

Tech background:

I used to use a network folder for my original RAW files. The shared folder was mapped as drive P to my desktop. Although this worked fined it was a little slow sometimes because of huge number of raw files and only 1 Gpbs network connection to my NAS.

 

I bought a new SSD and installed it as drive E and created a photo folder on it and copy all images into it. I permanently mapped E:\photo as drive P with regedit. 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices
Key: P: 
Value: \??\E:\Photo

This makes P drive available right during boot time and works as a real drive without any problems except for Lightroom Classic.

 

  •  

 

Judging by the logs I'm pretty sure that the registry magic to fake drive P is the cause of the problem. What I don't understand why single rename works while mass rename does not.

 

Any help, suggestion appreciated.

 

Thanks,

Peter

이 주제는 답변이 닫혔습니다.

1 답변

johnrellis
johnrellis
Legend
March 27, 2023

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

 

I think it would be simpler if you changed your catalog to refer to the new locations of the photos at E:\Photo.  To do that:

 

1. In LR's Folders panel, find the section for the P drive.

 

2. Right-click a top-level folder in that section and do Show Parent Folder.  Repeat that until P: is showing as the top-level folder in that section.

 

3. Right-click P: and do Update Folder Location; select E:\Photo as the new location.

 

This is what it looks like (with a Y drive instead of P):

 

MPeter1975
MPeter1975작성자
Participant
March 28, 2023

Thank you for your answer.

 

I will not change the location, because I still syncronize my local folder to my NAS share which is mounted as drive P on my laptops. I also syncronize the catalog files (without previews) across my computers and use the same catalog on every computer (not at the same time), so I need to have the same folder location (drive P) everywhere.

 

I just wanted to give a speed boost on my desktop computer with the original raws, storing them on a fast SSD primarily. Smart previews also do not seem to be an ultimate solution because I use Photoshop and Premiere working on the same contents.

 

I still would love to hear any ideas why the mass rename does not work while I can rename individual files without any problems.

johnrellis
johnrellis
Legend
March 28, 2023

Some more thoughts:

 

1. Try using the "subst" command at the command line rather than changing the registry.  Though various posts claim editing the registry is a way to make the effect of "subst" permanent across reboots, perhaps "subst" is doing something more that those posts are unaware of.  Probably not, but worth a quick test.

 

2. There have been a couple of other reports about LR not liking "subst" drives:

https://community.adobe.com/t5/lightroom-classic-discussions/lightroom-classic-8-2-1-photos-have-read-only-access/m-p/10461224 

 

Whether this is a bug in LR or a Windows weirdness, I don't think Adobe is likely to ever change LR to accommodate "subst" drives better (based on over a decade of observing what kinds of problems they address).  But I might be wrong, and you spit into the wind and file a formal bug report:

https://community.adobe.com/t5/lightroom-classic/ct-p/ct-lightroom-classic?page=1&sort=latest_replies&filter=all&lang=all&tabid=bugs

 

To have a hope of Adobe paying attention, the bug report would need to have a precise set of steps for replicating the problem with a brand new catalog with (say) just 3 photos imported, all located on the local disk.   If Adobe can't quickly reproduce a problem, they'll never file an internal bug report (unless many people report it).

 

Even if they eventually fix the issue, it will be many months at a very minimum.

 

3. On the other computers, change the root folder of the photos to P:\Photos (by creating a top-level folder) and updating the LR catalog to use the new location as described above.

 

On the computer with the SSD, make a very small partition on the SSD or another local disk and assign it drive letter P. Use the "mklink" command to make a symbolic link or a junction (two different beasts) from P:\Photos to E:\Photos.

약관 및 조건Accessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices