We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
I get this error when removing rejected files from the disk within Lightroom Classic CC (latest version 9.1).
Here's what I've done so far and my tests:
So far, I haven't noticed any errors in my catalog, and when I tell LR to run the Integrity Check, it passes (no problems). I even asked LR to find any missing files, and it doesn't find any missing files, and when verifying all previews/DNGs, that also passes without issue. So basically no signs of corruption of any sort.
Any idea on this?
I've seen that this has been a problem in the past, but never found a solution as to why. I mainly don't want to get down the road and realize that all of my LR catalog backups (which Id o on a daily basis) are corrupt and I've lost everything in terms of edits. I have started exporting edits to XMP files just as a backup, but it's an extra step.
Possibly a poorly implimented plug-in. One suspect would be Logitech Options
Yes that was it. I don't know why this is enabled by default unless it only affects users of Logitech devices.
It is installed when you install the Logitech support software for the mouse or keyboard
I uninstalled Logitech Options, and the error did not happen again
I have been receiving this same message when trying to export my finished images. I tried many of the fixes listed in these threads. However, in my case, it turned out to be the catalog that had a problem. I was able to export the images by creating a NEW CATALOG, then importing the images from the original catalog into it, to then export it. Hopefully my sharing this will help someone else. Here are the steps.
File > New Catalog > (name it) Create > the new catalog will then open...
File > Import From Another Catalog > (find original catalog) Double Click to open or click Choose > (check box) Import.
Once the images have completed the import, you may export as you normally would.
I figured it out after a while. It was related to an add-in called "LogiTools" or "LogiOptions" or something like that, which is related to Logitech devices (kyeobards and mice). Anyways, disabling the "Logitech Options" add-in was the cause of the problem. Don't know why, but after disabling it (after reading another person's recommendation) the issue went away.