Skip to main content
Known Participant
August 13, 2025
Released

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

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.

137 replies

Participating Frequently
September 7, 2025

So the plot thickens.
I am not currently using version 14.5.1 because it is much slower than previous versions, so I reverted to version 14.4. Even after that, the problem of the exclamation point persists. Guiding you step by step:

1- All looks well, and GPU is on auto

2 - I do a object selection mask, or sky mask, there is a moment where it is creating the mask and then no mask is created and the image gets the exclamation point

3 - I go to preferences and GPU is turned off.

Translate
johnrellis
Legend
September 7, 2025

@andre29143016m9nk: "If I go to preferences, even though the GPU use was set to AUTO, when the error occurs, it is now changed to OFF with no option to turn it on."

 

Please do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set.

 

Also, please post a full-resolution screenshot (not a phone pic) of Preferences > Performance.

Translate
johnrellis
Legend
September 7, 2025

@andre29143016m9nk: "even though Adobe Creative Cloud Desktop says I have Camera Raw 17.5 installed, when I go to LR about, it mentions 17.4"

 

LR Desktop and LR Classic have their own version of Camera Raw built-in and don't use the Photoshop plugin downloaded by the Creative Cloud app.  LR Classic's Help > System shows it this way:

 

Internal Camera Raw version: 17.5 [ 2318 ]

 

If your LR Classic's Help > System Info is showing Internal Camera Raw version: 17.4, then you don't have the latest version of LR Classic (14.5.1).  What does the first line of Help > System Info say?

Translate
Participating Frequently
September 7, 2025

strange, even though Adobe Creative Cloud Desktop says I have Camera Raw 17.5 installed, when I go to LR about, it mentions 17.4

Translate
Participating Frequently
September 7, 2025

I just found that even after reverting to version 14.4, I still get the exclamation point error when I try to make an AI mask, like select object. If I go to preferences, even though the GPU use was set to AUTO, when the error occurs, it is now changed to OFF with no option to turn it on.
So maybe it is related to camera raw 17.4?

Translate
Known Participant
September 5, 2025

No

Translate
jm68902488
Known Participant
September 5, 2025

Anshui has this bug issue been fixed in the 14.5.1 new release?

Translate
Known Participant
September 4, 2025

@AxelMatt yes but it was just to say that Adobe Is taking care they already have all the info and log.

Translate
Community Expert
September 4, 2025

@Giovanni Stoto  Sorry, but we don't have the appropriate informations. You've send this infos to @Anshul_Saini. Ok, but he's an Adobe employee, but other participants including I are normal user as you are. We don't have access to the infos that you've send to Adobe.

 

Translate
My System: Intel i7-8700K - 64GB RAM - NVidia Geforce RTX 3060 - Windows 11 Pro 26H2 -- LR-Classic 15 - Photoshop 27 - Nik Collection 9 - PureRAW 6 - Topaz Photo AI
jm68902488
Known Participant
September 4, 2025

Yes had the same issues with 14.5.  Rolled back to 14.4.  Any news if this was fixed in 14.51?

Translate