Skip to main content
Participant
July 1, 2026
Question

Problems with LrC not recognizing current catalogue.

  • July 1, 2026
  • 2 replies
  • 0 views

For the second time in a month, LrC when opening says it can’t find the catalogue. Today that happened and I had just used the catalogue yesterday. Today I am trying to use the most recent back up. Last month when it happened, I had to reconnect all my images. This was time consuming. 

Am I doing something wrong or different. Have not had these problems in the six or so years using the app. 

    2 replies

    JohanElzenga
    Community Expert
    Community Expert
    July 2, 2026

    If you had to reconnect the images, then something more and different happened. If Lightroom just can’t locate the current catalog for some reason, then there is no reason why you would have to reconnect the images once you found it and Lightroom opened it.

     

    Where is your catalog located? On the internal drive or on an external drive? And what is your OS? WIndows? Mac? This kind of information is vital in understanding what could have gone wrong. For example: on Windows, if the catalog is on an external drive, you could get this problem if Windows changed the drive letter. And if the images are also on that drive, or another external drive, then drive letter change can explain why you had to reconnect them.

    -- Johan W. Elzenga
    gary_sc
    Community Expert
    Community Expert
    July 1, 2026

    Hi, ​@jamesd57009737

    First question: can you locate your catalog file? (The suffix should be .lrdata)

    Second qustion: have you tried double-clicking it?

    Why it gets dropped, I have no clue, too many possible small reasons (what I mean by that is that are bunches of reasons, none glaring that are easy to spot).

    Let us know and good luck

    JohanElzenga
    Community Expert
    Community Expert
    July 2, 2026

    The suffix is .lrcat, not .lrdata!

    -- Johan W. Elzenga
    gary_sc
    Community Expert
    Community Expert
    July 2, 2026

    @JohanElzenga, dang, thank you for the correction.