Production workflow · Lightroom Classic workflow
Lightroom Classic: original path points to the wrong volume
How do I fix an old drive path in Lightroom Classic before recovery?
Short answer
First fix the link, not the files: right-click the folder with the question mark in Lightroom Classic's Folders panel, choose Find Missing Folder and select the folder on the renamed drive. The catalog then updates every photo inside it. Only if the originals exist on no connected drive does a read-only recovery scan make sense.
The situation
Lightroom Classic expects a drive name, letter or folder that no longer matches the mounted storage.
The catalog stores each photo with the folder it lives in, so a drive that reports a new letter or name takes a whole folder tree offline in one go. Repairing the reference at folder level fixes hundreds of photos at once.
01 / Diagnose
Work out what actually disappeared
Photo archives usually live on external drives that come and go, and Windows hands out letters in the order devices are plugged in, so a card reader connected first can displace the archive. On macOS a renamed volume has the same effect. Migrating the archive to a larger disk creates a new path as well, and the catalog keeps pointing at the old one.
Absolute paths can break even while the file remains intact elsewhere. For Lightroom Classic, this matters because Lightroom Classic can keep references or helper media without containing a complete independent original
Check the last known path, trash and backups without writing to the original device.
02 / Protect the source
Preserve the best recovery chance
- 1
Connect the archive drive by itself and note the letter or volume name it receives, so the catalog has a stable target to work with.
- 2
Compare the folder path in the catalog with the path on the drive, checking that the subfolder names below the top level still match.
- 3
Reconnect at the highest folder that is marked as missing, so the catalog reassigns every subfolder and photo underneath in a single step.
- 4
Give the drive a permanent letter or keep its name unchanged, and reserve a read-only scan for photos that no connected drive holds.
Do not reconnect photo by photo and do not import the folder again from its new location. A second import creates duplicate entries without the develop settings, and the old entries stay behind as missing files nobody can edit.
03 / Choose the method
Match the tool to the source
For stable, readable exFAT, NTFS and FAT16/FAT32 or uncompressed IMG, DD, RAW and BIN images.
Unconfirmed exports are marked .UNVERIFIED.
Reconnecting only works while the files are present on a mounted disk. File Recovery Hero reads exFAT, NTFS and FAT16/FAT32 archive drives and uncompressed images read-only; a drive that no longer mounts, or an encrypted one, is beyond it.
04 / Verify
Check the recovered content, not just its name
The catalog is correct again when no folder carries a question mark after a restart, a sample photo opens in the develop module with its edits intact, and the folder panel shows the new drive with the expected photo counts.
Keep the source until two verified copies exist. One working preview is not enough.
Sources and technical references
FAQ
Questions about this recovery case
Can Lightroom Classic workflow be recovered in this situation?+
The catalog stores each photo with the folder it lives in, so a drive that reports a new letter or name takes a whole folder tree offline in one go. Repairing the reference at folder level fixes hundreds of photos at once. The result still depends on what remains readable on the source.
What should I avoid before scanning?+
Do not reconnect photo by photo and do not import the folder again from its new location.
Does scanning write to my memory card?+
Your memory card is only read. Nothing is saved to it.