Skip to main content
Known Participant
April 22, 2025
Question

Lightroom Classic 14.2 losing "New Remove Spot" edits after quitting

  • April 22, 2025
  • 3 replies
  • 1068 views

I think this is actually a bug but will report it here and the moderators can decide if it is a bug.

 

Lightroom Classic 14.2 on Mac mini with Apple M2 Pro, 32GB, Sonama 14.7.1.  This is a with a fairly new catalog with not many images.

 

If I start with a new image with lots to be cleaned up:

I use the new Remove tool and spend 20 minutes cleaning up the image:

I quit Lightroom and restart and my edits are gone but I have a message "Some Remove settings need to be updated":

I click "Update All" and wait around 4 minutes for the updates to complete. They finish but the image is not what it was before I quite.  i.e. the updates don't work properly and I have to clean up the image some more.

 

1) Lightroom should NOT lose the edits just by quitting

2) If it is going to lose the edits, refreshing them should put it back the way it was before it lost the edits.

 

3 replies

atj777Author
Known Participant
April 22, 2025

This is what I am trying now... 

 

I created a newer catalog by Exporting as Catalog from All Photographs (currently only 2215 photographs as to opposed to my original catalog which has over 300k).  

 

I will start using this Newer catalog and see if the problem recurs.

atj777Author
Known Participant
April 23, 2025

So even with creating a brand new catalog with a brand new lrcat-data file, the problem recurred.

GoldingD
Legend
April 22, 2025

In your screenshots, I do not see any AI edits (in this case generative remove would be the AI in question) So my furst hunch in MACOSand LrC v14 is probably not correct, that being something wrong with access to the lrcat-data file. Perhaps another member can squish that thought down to not the issue.

atj777Author
Known Participant
April 22, 2025

The New Remove tool is AI based and the data are definitely stored in the lrcat-data file. The previous Heal tool was also AI based.

 

In fact, if you look at the last of my screen shots it clearly says "Update AI Settings" as the last step in the History after I clicked on "Update All"

JohanElzenga
Community Expert
Community Expert
April 22, 2025

There is AI and there is Generative AI. The remove tool is indeed AI based, even if you do not check the option to use Generative AI. The .lrcat-data file could be the problem. There are reports that this file sometimes gets corrupted, or that Lightroom can't write to it because of permission problems. You could try moving it out of the catalog folder, so Lightroom builds a new one. That will mean you'll have to update AI settings one more time, but then the problem should be over.

 

-- Johan W. Elzenga
JohanElzenga
Community Expert
Community Expert
April 22, 2025

I noticed the right panel shows the remove tool panel in all screenshots. Did you close the tool panel (go back to general edits) before you quit Lightroom? Maybe not closing the panel will not write the edits into the catalog properly and so this triggers the update requirement.

 

-- Johan W. Elzenga
atj777Author
Known Participant
April 22, 2025
quote

I noticed the right panel shows the remove tool panel in all screenshots. Did you close the tool panel (go back to general edits) before you quit Lightroom? Maybe not closing the panel will not write the edits into the catalog properly and so this triggers the update requirement.

I don't believe that is the cause. Earlier today I worked on three images straight after each other before I quit and lost the edits on all three images. There's no way to move from one image to the next without closing the tool panel.

 

This only started happening after ugrading to 14.2 and doesn't happen every time but happens often enough to be extremely frustrating.

JohanElzenga
Community Expert
Community Expert
April 22, 2025

Strange. I haven't seen never seen it and I have not seen any other reports either. As Lightroom Classic 14.2 has been out for quite some time, it seems unlikely that this is a general bug in version 14.2 rather than something on your computer.

 

-- Johan W. Elzenga