P: First image of import is always corrupt

[csabato]

On every import, the first image is always corrupt. Removing the image from the library and then synchronizing the directory brings the image back into the library correctly. 

I just updated to the most recent version, and the issue persists. 

Windows 11 24h2 26100.6899

[johnrellis]

If you take one of the photos marked as corrupt into Develop, can you apply settings as normal?

Adobe fixed a bug in LR 14.5 where some photos were spuriously marked as "corrupt" ("!" in a black circle in the upper-right corner of the thumbnail), but users could still edit them in Develop. Perhaps Adobe didn't fix all aspects of that bug.

[dj_paige]

What do you see on your screen that indicates the photo is corrupt?

[csabato]

It's always the first photo. It does appear that I can actually edit the photo in develop. The photo appears low-res in library, but not in develop, and the exclamation point never goes away.

[dj_paige]

Ok, thanks, it doesn't really say "corrupted", and so using this word can lead us to head into wrong directions. I believe this exclamation point icon is what @johnrellis was referring to. You should be able to edit this photo in the Develop Module without problems.

[johnrellis]

There are a couple other reports of the spurious black-circle-! appearing in LR 15.0:

https://www.lightroomqueen.com/community/threads/random-corrupt-photos.53799/#post-1360626

in spite of Adobe reporting the problem from 14.5 was fixed

https://community.adobe.com/t5/lightroom-classic-bugs/p-v14-5-lightroom-has-encountered-problems-rea...

I'll keep an eye out and start consolidating them.

[csabato]

This was happening before I upgraded to 15, so it was not fixed for me in 14.

[johnrellis]

@csabato: "This was happening before I upgraded to 15, so it was not fixed for me in 14."

The bug was introduced in LR 14, but Adobe didn't report it fixed until 15.0.  Some confirmed that the fix worked for them, but clearly it's not working for some others.

[trevorp56149524]

Since the latest Classic update I'm having issues when exporting copies of image files from one folder to another. The first of the batch of images always has an exclamation mark(!) in a black circle top right and the preview is pixelated. (the subsequent image files in the batch copy across fine).

When I attempt to view the file by clicking on the preview I get a message stating "An unexpected end of file occurred" .

Has anyone else encountered this issue and know how to fix it or how to get Adobe to investigate this bug please?

Note: Ive had no problems doing this in any previous version of LR

[fannygarcia01]

@csabato I am having the same issue even after 15.0 update. And the same thing with mine, I am able to view and edit the photo under the development tab but cannot view it in library it says, "The file appears to be unsupported or damaged," and it appears blurry:

[dj_paige]

See this thread. Although Adobe claimed to have fixed this bug, it appears that it has not yet been fixed, as you are the third person using LrC 15.0 who have seen this happen. I would definitely comment in teh thread where Adobe claims it was fixed, and provide as many clear details as possible to indicate that it is not fixed. Do not simply say "It is not fixed", give details, as many as you can.

[KevinBrinckmann]

I am an editor for another photographer and I receive the catalog with Smart Previews. Last Saturday, we photographed an event together, and when he tried to send me the catalog, the following message appeared: 'Lightroom encountered problems reading this photo.'

I already tried storing it on the C: drive, moved it to the D: SSD, and nothing solved it. Is anyone else experiencing this?
LR Version: V15.0

[dj_paige]

There are two possible causes for the exclamation point icon in a black circle.

1. The file is corrupted and can't be used
2. The file is fine and a recent bug in LrC causes the exclamation point icon to appear.

Can you edit the file in LrC?

[KevinBrinckmann]

Yes, I can edit the files that appear in the "Develop" tab, but since it was a large event, I need to curate the photos before proceeding with the editing.

[ExUSA]

There is a 15.0.1 update that fixes some bugs, you might try that.

[KevinBrinckmann]

I installed version 15.0.1 after my report but still this error remained

[koleridav]

Having this bug as well, on 15.0.1 MacOS Tahoe. Happens about half of the time when importing images. I think I've only noticed it on JPEG images when pulling in from what my editors send me. Luckily removing from the library and syncing the folder pulls it in fine but annoying to have to do.

[rayc61580062]

Has there been a fix for this bug? I'm getting it with version 15 of the software and nothing I've tried has resolved it.

[WeGoFar]

I have the exact same issue.  It started happening at least a couple months ago.  I've tried copying the files to other local drives and importing them, importing direct from Google Drive, copying them using the command prompt prior to importing, importing using "Add" instead of "Copy", nothing seems to make a difference.  

My workaround is to right click, edit in photoshop.  In Photoshop, add a layer, delete the layer, exit.  This forces Photoshop to rewrite the file and it works fine from that point on.  I can open the original file in any other app and it's fine.  I've tried various JPG utilities and they all say the file is correct and valid.

So far, I've only noticed the problem with JPGs.  My drone and camera raw files always seem to import fine.

I'm on Windows 11 Pro 25H2 build 26200.7171, LrC 15.01 Release, Camera Raw 18.0, on an Intel core i7-9700  @ 3.00 GHz, with an NVidia GeForce RTX 3060 using Studio driver 581.57 using dual 4k displays.  I've had the problem long enough that I know it's been across more than one windows update and more than one NVidia driver update.