Skip to main content
Participant
January 14, 2026
Question

Lightrom has encountered problems reading this photo

  • January 14, 2026
  • 2 replies
  • 177 views

I recently merged a work project catalog into my master catalog. Now that I went to look at those photos in my master catalog, I get an error message saying there was a problem reading this photo and I can't make adjustments. This error message only shows on the photos I have edited and used the automatic denoise. I'm afraid I've done something irreversible with these photos. I also upgraded lightroom classic just before the migration so the project catalog was updated when importing the photos.

2 replies

Anshul_Saini
Community Manager
Community Manager
January 14, 2026
 
Thanks for the detailed description. Let’s clarify a few things so we can point you in the right direction.
•Are you seeing the same issue described in this thread?
If so, please let me know, and I can merge your post there, so you’ll automatically receive updates as the issue progresses.
 
If this is not the same issue, please share:
•A screenshot of the exact error message shown in Lightroom
•The Lightroom Classic version you upgraded from and to just before the catalog merge
 
To help narrow this down further, please also test:
1. Does the photo become editable again if you remove the edits or temporarily remove the XMP sidecar (if present)?
2. If yes:
•Copy & paste settings excluding Details / Denoise
•Then reapply Denoise again and check whether the issue disappears
 
Looking forward to your update.
 
Best regards,
Anshul Saini
Participant
January 14, 2026

This appears to be the same issue except restarting Lightroom does not fix the problem for me. Also I have not been able recreate or find any other photos or folders with this problem. 

The photo is locked and I can't create a virtual copy of it or make any changes to the edit. There's no XMP sidecar present. I upgraded from Lightroom Classic 13.4 (not 100% sure) to 15.1

dj_paige
Legend
January 14, 2026

At least two other people with this issue in LrC 15.1 say that reverting back to 15.0 or 15.0.1 fixes the problem. Its worth a try.

dj_paige
Legend
January 14, 2026