Lightroom classic Assertion Failed

Forum|Forum|8 years ago
November 4, 2017
7 replies
9753 views

Anybody else have this? any fix? thanks Ramona

This topic has been closed for replies.

Correct answer Pyrrhic24

A workaround I found was to find an old lightroom catalogue (.lrcat) file and open that, it then should open lightroom. Not perfect but seemed to work for me.

C

Cynthia243649952jel

Participant

I tried all the previous suggestions as well. The only thing that worked was opening an older .lrcat file. I think the file was corrupted somehow. Luckily, I back up Lightroom every time I use it so I was able to recover most of my files.

L

LocketGirl

Inspiring

I had this while I was trying to attempt to open edited DNG files I was working on in Bridge in Lightroom Classic and it was super annoying: the official Adobe workaround didn't work, changing the names didn't work, updating my computer didn't work nor did restarting it. What did work was deleting the one DNG file that Lightroom kept trying to make a corrupted folder for (which is why it wasn't working in the first place.) I deleted the one persnickety edit (knowing I have the original RAW file elsewhere) and FINALLY Lightroom opened! Hope this ACTUALLY helps anyone with this problem because the "correct" doesn't work for half the people here.

anitao36423279

Participating Frequently

I had this issue starting this morning, but I'm not sure if it was an Adobe update or Windows update that messed me up. I checked my registry and my Pictures folder, removed and reinstalled, both saving preferences and not. I tried creating a new catalog. No help with any of that. Finally I tried turning off Ransomware Protection. Can start LR. Turn it back on, cannot start LR. Turned it off for now. This makes me pretty nervous as ransomeware is truly nasty. I guess I'll end up turning it of when I want to use LR and on again when I finish.

benvenisti

Participating Frequently

What worked for me was renaming the offending catalog extension to .lrca-. Seems like that file got corrupted. No big deal because it was old, everything was exported, the client wanted a change and I was able to do it in PhotoShop. Give that a try

P

PJ_Traveler

Participating Frequently

Same problem,

windows 10 update seems to have corrupted LR, because all of the LRcat backups fail with the assertion fail. I have the Pictures folder, and it is reference in the registry correctly. I suspect that lightroom is pointing at the wrong place, but can't find it or fix it.

P

Pyrrhic24Correct answer

Participant

A workaround I found was to find an old lightroom catalogue (.lrcat) file and open that, it then should open lightroom. Not perfect but seemed to work for me.

D

dlehne

Participating Frequently

Thanks so much for the suggestion. Sad to say it didn't work for me. Opening the catalog resulted in the exact same pop-up.

My guess is that different underlying problems cause this uninformative pop-up to be displayed. That would mean that no single workaround is going to work for all of them. That said, your response was a heck of a lot better than anything I've heard through any channel from the software's makers. So far it's just been silence. Not even crickets.

Again, thanks for taking the time to post the suggestion.