Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
5

P: v14.5 Lightroom has encountered problems reading this photo | Round circle ‘!’ warning on Images

Engaged ,
Aug 21, 2025 Aug 21, 2025

OS: Windows 11
LrC VERSION: 14.5

A couple of days ago I upgrade to v14.5.
As for every update, I regurlay empty cache, optimise catalog, remove all previews and generate new standard ones (also, I wanted to test how was was the new option to use GPU for generating previews).
Never had a problem with this workflow.
After previews generation process was completed (1h 30m for 29.000 files, 23.000 jpegs and 6.000 raws) I got an error: for 21 RAWs the preview could not be generated. Looking in the catalog at those files, I realised they have an exclamation mark on a dark circle: this is not the missing photo mark. If I click on the exclamation mark, I see error "Lightroom has encountered problems reading this photo, you are not allowed to edit this image. "

Yet, I can still enter develop module and edit the photos without any problem: the editing history is there, I can zoom in at 100% (generating the 1:1 preview), I can change sliders, export... Everything... (PS: I do not use smart previews).

 

The 21 problematic photos are in different folders and have different dates.
The files can be opened by any other program, including Fast raw Viewer.

For a couple of problematic photos, I tried deleting the photos from file explorer, and the square light missing photo question mark replaced the round dark question mark.
I restored the files from three sources:
1- the original file
2- a backup from a second HD
3- a backup from Amazon Photos


In all three cases above the black round exclamation mark came back: this should prove that it's not a problem of corrupted files, I instead believe it's an issue in LrC.

a.png

Bug Investigating
TOPICS
Windows
1.1K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Aug 29, 2025 Aug 29, 2025

Hi @Giovanni Stoto, @iTomDean, and @shayb68441784,

 

Thank you again for the detailed testing and examples. I’ve logged this issue with the product team so engineering can investigate further. I wasn’t able to reproduce the problem on my end, but I’ve attached all the details you’ve shared so far to the bug report.

 

To help the team isolate the root cause, could you please collect and share logs from your system after reproducing the issue? Here’s how:

 

Steps to Collect Logs

  • Close Lightroom

...
Translate
59 Comments
Engaged ,
Aug 26, 2025 Aug 26, 2025

Do we have news?

Translate
Report
Explorer ,
Aug 26, 2025 Aug 26, 2025

Bonjour,

 

Dans LrC 14.5.x pour certaines images (rarement toutefois), après avoir ajouté un masquage, sur la vignette de l'image (dans le module bibliothèque, ou dans le ruban du module développement), il apparait un point d'exclamation dans un cercle noir (!). 

 

Lorsqu'on clique sur ce point d'exclamation, un message indique que Lighroom a rencontré des problèmes lors de la lecture de cette photo et qu'elle ne pourra pas être modifiée. OR, elle est modifiable dans le module de développement.

 

J'ai supprimé la photo de Lightroom puis je l'ai importée de nouveau après avoir changé son nom : au départ pas de (!). Dès que j'ajoute un masquage, le (!) réapparait.

 

Les photos pour lesquelles j'ai constaté cette anomalie sont au format .psd.

L'ajout de masquage sur une photo au format .psd ne produit pas systématiquement cette anomalie.?

 

Que faire ?

 

Cordialement

Translate
Report
LEGEND ,
Aug 26, 2025 Aug 26, 2025

If you share one of these .psds here, we can see if the issue occurs on other LR installations and file a bug report if necessary. Upload it to Wetransfer, Dropbox, Google Drive or similar free service and post the sharing link here.  Also, include a screenshot of the Develop window, including the masking panel, showing the mask that's causing the problem.

Translate
Report
Engaged ,
Aug 26, 2025 Aug 26, 2025

News?

Translate
Report
Engaged ,
Aug 26, 2025 Aug 26, 2025

Any news?

Translate
Report
Engaged ,
Aug 26, 2025 Aug 26, 2025

What about news?

Translate
Report
Engaged ,
Aug 26, 2025 Aug 26, 2025

Do we have news?

Translate
Report
Engaged ,
Aug 26, 2025 Aug 26, 2025

Any news here?

Translate
Report
Engaged ,
Aug 26, 2025 Aug 26, 2025

@CMass news?

Translate
Report
Engaged ,
Aug 26, 2025 Aug 26, 2025

@CMass any news?

Translate
Report
Engaged ,
Aug 26, 2025 Aug 26, 2025

@CMass so we have news?

Translate
Report
Engaged ,
Aug 26, 2025 Aug 26, 2025

@Bob321 we are paying a monthly fee for updates that always bring problems, we deserve a feedback when submitting a bug!!!!!

Translate
Report
Engaged ,
Aug 26, 2025 Aug 26, 2025

@Bob321 and @WHO?!? 

Can you please submit yourselves a bug in the Bug session? And in your post reference this one?

This is ridiculous that no one here from Adobe is proving any feedback when it's obvious it's a bug.

@CMass has initially provided a useless comment proving that Adobe doesn't even read properly what people write: very unprofessional. And now she has disappeared because probably she doesn't know what to say.

I have been asking to move this post from discussion under bug, to no avail.

If only I could leave Lightroom! But after 15 years and thousands of picture, it's almost impossible...

Translate
Report
Explorer ,
Aug 27, 2025 Aug 27, 2025

Hello,

I performed the test on my side: I imported the picture on my laptop and processed the picture on the same way as on my main computer. There was no issue on the laptop untilI modify the first mask created.

Then I performed the same operation on my main computer but in another catalog than the one I'm used to work with. Same thing: after having created two mask, if I modify the first one with the pencil to erase a part, the issue occurs: (!) is the displayed on the thumbnail.

Further, if I drop all the mask by deleting the last operations in the history, the (!) still remains.

I'm going to share the picture and screenshots of Develop panel.

Regards

 

Translate
Report
Adobe Employee ,
Aug 27, 2025 Aug 27, 2025

Hi @Giovanni Stoto,

 

Thank you for sharing the very detailed investigation, and thanks as well to @Bob321 and @WHO?!? for confirming similar behavior.

 

Would you all please update to the latest version of Lightroom Classic 14.5.1, which was released today, and let us know how it goes?

If the issue persists in v14.5.1, please copy & paste your system info from the Lightroom Classic Help menu > System info and share a few affected images via DM so I can pass them on to the product team for investigation.

 

Thanks again for your patience.

 

Best,
Anshul Saini

Translate
Report
Contributor ,
Aug 27, 2025 Aug 27, 2025

Yes, can confirm I have the same problem with 14.5. And I'm seeing comment from others who also are seeing it (see atttached). It's not just you. 

Translate
Report
Engaged ,
Aug 27, 2025 Aug 27, 2025

Thanks

Unfortunately 14.5.1 does nopt solve

Translate
Report
Engaged ,
Aug 27, 2025 Aug 27, 2025

@Anshul_Saini 

14.5.1 does not solve the problem:

GiovanniStoto_0-1756312195600.png

GiovanniStoto_1-1756312277834.png

GiovanniStoto_2-1756312325027.png

GiovanniStoto_3-1756312353075.png


I have also ytried converting the image in DNG and copy/paste develop setings from raw to dng, and the problem appeared also on dng.

Since the problem was not there before (confirmed by others whom have downgrade and problema disappeared) I do not think kit is related to hw/sw components but here attached the system info.

Even if I share the affected images, they would be useless without the edits that generate the warning.

Translate
Report
Adobe Employee ,
Aug 28, 2025 Aug 28, 2025

Thanks for sharing the sample files via DM, @Giovanni Stoto. I tested it on my end, but wasn’t able to reproduce the issue, so I’ve forwarded the files and details to the product team for further investigation.


In the meantime, could you help confirm a couple of things:
 • If you take new RAW files and apply the same edits (either copy/paste from the problematic photo or recreate them manually), do you see the same error in 14.5.1?
 • If you repeat the same workflow in 14.4 and then upgrade to 14.5.1, does the error appear after upgrading?


This will help the team narrow down whether the issue is with existing edits migrating between versions or if it also affects newly created edits in 14.5.1.


Thanks again for your detailed investigation and for sticking with this while we dig deeper.

 

Best,

Anshul Saini

Translate
Report
Engaged ,
Aug 28, 2025 Aug 28, 2025

Yes to both.

The dng I sent was an export of a raw with !, when exported from raw to dng and imported, no problem, then I copied dev settings from raw and pasted to dng and ! appeared.

 

Going back to 14.4 the ! disappears and reappears on the same files after upgrade.

 

As I wrote I noticed that if I remove the brush from the mask, the ! disappears.

 

Later I will try to copy dev settings from a raw with ! and paste it in a DIFFERENT raw, to verify if it's just the developments or the combination with a specific file.

Translate
Report
Engaged ,
Aug 28, 2025 Aug 28, 2025

In the same folder I sent via DM I added three screen recordings: A, B and C.
I have been playing with some combinations, and my resultsb are:
- I confiorm that for the photos the missue is with a brush in a mask: by removing the brush the ! disappears.

- If I copy dev settings from a RAW/DNG with ! into a RAW/DNG without !, the ! appears: so it's not the dev settings + RAW combination, but it's just the dev settings to be the problem

Translate
Report
New Here ,
Aug 28, 2025 Aug 28, 2025

14.5.1 has the same bug

 

Translate
Report
Adobe Employee ,
Aug 29, 2025 Aug 29, 2025

Hi @Giovanni Stoto, @iTomDean, and @shayb68441784,

 

Thank you again for the detailed testing and examples. I’ve logged this issue with the product team so engineering can investigate further. I wasn’t able to reproduce the problem on my end, but I’ve attached all the details you’ve shared so far to the bug report.

 

To help the team isolate the root cause, could you please collect and share logs from your system after reproducing the issue? Here’s how:

 

Steps to Collect Logs

  • Close Lightroom Classic if currently opened.

  • Launch Lightroom Classic again.

  • Reproduce the issue.

  • Close Lightroom Classic immediately after closing the issue/ error modal appears.

On Windows

  • Lightroom log: %appdata%\Adobe\Lightroom\

  • Camera Raw logs: C:\Users\<username>\AppData\Roaming\Adobe\CameraRaw\

On macOS

  • Lightroom log: ~/Library/Application Support/Adobe/Lightroom/

  • Camera Raw logs: ~/Library/Application Support/Adobe/Camera Raw/Logs/

Note: Log files will have names like:

Adobe Photoshop Lightroom Classic Log Latest v0.txt

Adobe Photoshop Lightroom Classic Log Latest v1.txt

lrc_console.log (be careful not to confuse with lrcc_console.log under Lightroom CC)

 

You can upload these logs via DM (or a secure link), and I’ll ensure they’re attached directly to the bug report for engineering.

 

Best,

Anshul Saini

Translate
Report
Adobe Employee ,
Aug 29, 2025 Aug 29, 2025

Updating Status

Status Investigating
Translate
Report
New Here ,
Aug 29, 2025 Aug 29, 2025

I am also seeing the same problem. Had to revert to a previous version so I could work with LR again. 
Adding to the problem described, the interface has slowed down immensly and many times the mask's overlay won't show even though it is set to "show always" and pressing the O shortcut won't do anything either.

Translate
Report