Catalogs get corrupted constantly

[Hooches]

Hi there!

I´m having problems with Lightroom Classic since the last weeks. After importing new pictures some of them are greyed out (see picture) in the develop & library module. I can open the files without any problems with Luminar AI for example.

I can solve the issue by creating a new catalogue and import all of the pictures into that new catalogue and i can edit them without any problems. But after a few imports (sometimes even the next import) i have the same problem again and have to create a new cataloue again which is quite annoying.

I´m working on a M1 Macbook Pro. Checked the SSD with the Disk drive utility and it didn´t show any errors. Already tried reinstalling Lightroom and used different SD cards. I plug the SD-Card directly into the Card-Reader of the Macbook.

Do you have any ideas how to solve this problem?

[moved from bugs to discussions according to the community rules - Mod.]

[Bill Sprague]

Try resetting your preferences.  That can fix things when Classic is acting in odd ways.  

https://helpx.adobe.com/lightroom-classic/help/setting-preferences-lightroom.html

Or....

https://www.lightroomqueen.com/how-do-i-reset-lightrooms-preferences/

[Hooches]

Thanks, will try that!

[F. McLion]

They don't even show a name.

Are these ARWs as well?

What happens if you right-click on them and try "Im Explorer anzeigen"? Does it link to a photo?

[Hooches]

Can´t try at the moment since i´ve just set up a new one. As soon as the problem comes back I will test it. If I remember correctly it didn´t show any information (Metadata etc.) at all and it would just show the info from the last picture that was selected.

[dj_paige]

@Hooches, you should not mark your own answer that says "Thanks, I will try that" as the correct answer. There is nothing in "Thanks I will try that" which is an answer, much less correct. If other people's answer is correct, you can mark one of those answers as correct.

[Hooches]

It wasn´t me who marked it as the correct answer, it was @Bill Sprague.