Bug Reports

Hi everyone,I'm having an issue with the latest version of Lightroom CC on a MacBook M5 Pro running macOS Tahoe 26.5.1. (I was experiencing the same problem on 26.5 and decided to update hoping it would fix it, but unfortunately it didn't.)Since this morning, it's been impossible to to use Noise Reduction, even though my internet connection is working perfectly. I've already updated both Lightroom CC and macOS, cleared the cache, and optimized the catalog, but I keep getting this error screen whenever I try to use Noise Reduction.Has anyone experienced the same issue or knows how to fix it? Any help would be greatly appreciated. Thanks! 🙏 

[This bug report was originally posted on 1/26/2019 in the old feedback forum, but it never got transferred here. See the attached email message.]   In LR 14.3.1 / Windows 11, when LR is in  Window > Screen Mode > Full Screen, floating dialogs always appear hidden in back of the main LR window, and calling the toFront() function has no effect. This prevents my Any Crop and Any Filter plugins from being used in Full Screen mode. This doesn't occur in the other screen modes, nor does it occur on Mac OS 15.5.   This simple plugin demonstrates the bug:https://www.dropbox.com/s/6d1l3llo5dwzzuw/floatingfullscreenbug.lrdevplugin.zip?dl=0 Simply invoke Library > Plug-in Extras > Floating Dialog in the various Screen Modes. The command executes this simple code: LrDialogs.presentFloatingDialog (_PLUGIN, { title = "Floating Fullscreen Bug", contents = f:push_button {title = "Push Me"}, onShow = showErrors (function (t) LrTasks.startAsyncTask (s

On macOS Tahoe, Lightroom Classic overshoots when navigating with arrow keys on MacBook Pro models with ProMotion enabled. Setting the display refresh rate to 60 Hz immediately eliminates the issue. Reproduced on both M1 Max and M5 Max with fresh macOS and Lightroom installations. Does not occur on an M4 MacBook Air (60 Hz display).

I start with an edited version (lightroom adjustments only) of a photo in lightroom. I make a copy of it and then click reset on the new copy. This copy is essentially no modifications at this point. I then edit that copy in photoshop. When I am done editing in PS, I save it. I then open that PS-modified version in lightroom and paste ALL settings I have copied from the original to this new TIFF version. I expect the changes to work but it looks wrong. I notice the REMOVED tool item masks are strange. It looks like the REMOVE masks in the version that I pasted to are 90 degrees rotated - clockwise. Basically, copy/paste of masks does not work from a raw file to a tiff version. It’s like PS messed up the orientation indicator or something and LR got confused?

Lightroom Classic 15.0.1, Windows 25H2 26200.7171, Nvidia GeForce RTX 3060 (32.0.15.7602)   I took a photo of a bunch of fish swimming around behind a glass window. I wanted to use both reflection removal and AI Denoise. According to this page, I perform the AI Denoise first.   Here is the photo I used: https://www.dropbox.com/scl/fi/2zqjndbvb4i2mcwqqrgku/PMC_3135.NEF?rlkey=gq1w1mwdiu86oab9avto3wj9i&st=bi4tyj72&dl=0   Here is a screen capture of the unedited version of this photo, you can see reflections as well as noise       Here are the steps I followed:   1. AI Denoise, slider at 50, works as expected, noise is reduced.  2. Distraction Removal: Reflection, slider at 100. Reflection is not removed. Here is a screen capture after both steps, the noise reduction remains effective, but the reflection is not removed.     Also, please note that if I perform the steps in the opposite order (Remove Reflections first, the reflections are removed) but when I then add on the AI Deno

Then I apply AI denoise, in LR Classic 15.3 it does it in the background which I really like, however once I apply it to let’s say 100 pictures, and start editing the ones that already editable, it is stopping at the last few images. It is toally random where it is stopping but all the AI denoise remains in a stuck position and I can’t edit those photos unless I restart LR Classic. Sometimes these are images that already have some AI denoise on them, I just don’t bother to select the ones that doesn’t have it, so I paste the settings to all. And usually it is stuck it one point of the process.It only goes through the process if I don’t start editing any other photos, just wait for the whole process to finish. Lightroom Classic version 15.3Mac OS Sequoia 15.7.5Maxed out M1 Max MacBook Pro with Apple Studio Display 5K.

The red-x Reject badges persist on thumbnails in the filmstrip even when all the Select and Reject checkboxes in Assisted Culling are unchecked.  To reproduce on LR 15.4.1 / Mac OS 26.4.1: 1. Download and open the attached catalog. 2. In the Assisted Culling panel, uncheck all the checkboxes. Observe that the red-x badges still appear on the filmstrip thumbnails:  I haven’t discovered any way to make them disappear, including by deleting the Helper.lrdata file.

Lightroom Classiv v15.3 (on Mac OS Tahoe) has a problem importing photo files that have a pipe symbol - a | symbol - in the XMP field dc:subject.Lightroom apparently has a problem interpreting the pipe symbol, and then hangs, seemingly indefinitely until the import is cancelled, while showing a high level of CPU usage. This hanging seems to take place at the end of the import process for this photo.The pipe symbol is used by Lightroom to separate levels in the keyword hierarchy within the Hierarchical Subject XMP field.  Having pipe symbols also within the keywords doesn’t seem to be a problem with the Hierarchical Subject field - at least it doesn’t interfere with importing.  Also the pipe symbols in the Weighted Flat Subject field don’t seem to cause a problem with imports.Attached is a sample file that hangs when being imported into Lightroom.  Of course, a problem file causes a batch import of photos to fail, with some number of files correctly importing until Lightroom does to pro

The update to the Generative Remove AI model in Lightroom Classic 14.5 has ruined it, as it now changes elements outside the painted mask, making it more or less unusable in many situations.

Synchronize Folder > Scan For Metadata Updates can cause frequent spurious metadata conflicts for TIFFs that are stored on NAS.  Over the years many people have reported spurious metadata conflicts that Adobe hasn't been able to track down, and many of those reports involve photos stored on NAS.  Here's a recent report:https://feedback.photoshop.com/photoshop_family/topics/before_after_comparison_of_metadata_conflicts...While the particular use case here may not be that common, it may provide a reproducible test case that points to the bug (likely a race condition) underlying all those other persistent reports.Here are the steps that consistently produce the spurious conflicts in my configuration:1. Connect to a network volume on a 2013 iMac running MacOS 10.14.6. The volume is mounted with SMB 3.0.2.  2. Place 4 1800 x 1200 TIFFs (about 13 MB each) in a folder on the network volume.3. Import them with Add into a LR 9.0 catalog running on a 2019 Macbook Pro

I am so SAD!  I have bought a new Macbook M4 Max However, Lightroom CC lastest version, cant EXPORT slideshows as videos! the progress bar is stopped at nearly 10% position. No matter if I wait several hours it won't move any progress = I Cant export slideshow as Video   I always used this function, for a few years, day by days   I uninstalled the LR and tried reinstalling it, but it still failed. Does anybody have the same issue?I wonder if it is a problem related to M4 chips. Please kindly help and fix please!

EnvironmentAdobe Lightroom Classic 15.3 Lightroom SDK macOS 26.5.1 Standalone reproducer plugin attachedSummaryA floating dialog opened via `presentFloatingDialog()` does not reopen on the second screen. When the dialog is closed while positioned on a second monitor and then reopened, it always appears on the primary screen instead. Steps to Reproduce1. Connect a second monitor.2. Install the attached reproducer plugin via File > Plug-in Manager > Add.3. Run via Library > Plug-in Extras > Run Second Screen Dialog Bug Repro.4. Choose "Test Floating Dialog".5. Drag the dialog to the second screen.6. Click "Close and Reopen".A complete standalone reproducer plugin is attached. Expected ResultThe dialog reopens on the second screen at the position where it was last closed. Actual ResultThe dialog reopens on the primary screen. The position on the primary screen mirrors the saved coordinates — for example, a dialog closed at the top-left of the second screen reopens at the top-l

Description of Issue: The eye icon on the Remove panel stays greyed out.Lightroom Classic Version Number: 15.4 (June 2026)OS Version Number: Windows 11 25H2 (up to date)Camera Model: Canon R6 mk2Step-by-step Reproduction Instructions: In the develop module use the remove/heal/clone on some part of the image.The Expected Result: The eye icon should become active so you can hide the edits.The Actual Result: The eye icon stays greyed out.Image below shows the result:  

I have updated the LR to version 15.3, and since that update I cannot sync the edits across multiple photos with auto sync on while using Smart Previews to edit. Some things, like applying a preset works but adjusting exposure, shadows etc do not propagate through the rest of the images… If I do edit while on library module it will work. This works fine with the source files connected and when LR isn’t using smart previews… also lightroom is slower to apply presets etc than the previous versionHow do you fix this?

W tłumaczniu na język poski znalazłem nastepujące błęd: Pokaż wskaźniki przycinania powinno być Pokaż wskaźniki prześwietleń i niedoświetleńPokaż opcję Obcięcie, gdy mysz jest nad wskaźnikiem powinno być Pokaż ostrzeżenia, gdy mysz jest nad wskaźnikiemUkryj obcięcie światła powinno być Ukryj ostrzeżenia o prześwietleniachUkryj obcięcie cienia powinno być Ukryj ostrzeżenia o niedoświetleniachPokaż obcięcie światła powinno być Pokaż ostrzeżenia o prześwietleniachPokaż obcięcie cienia powinno być Pokaż ostrzeżenia o niedoświetleniachPokaż obcięcie powinno być Pokaż prześwietlenia i niedoświetlenia   Profil Adaptacyjna powinno być Adaptacyjny

As the title says, While using the Remove tool, the cycle new spot fill type (or Shift + T) shortcut is not working with lightroom classic, my version is Lightroom Classic 15.3.1. Is anyone else experiencing this? I have tried resetting the preferences or holding (Shift + Alt) upon launching the program but to no avail. Any help is appreciated, thank you!

Using the Copy Settings Subset option of modifed doesn't recognise the cropping if the image angle or aspect ratio haven't been modified. Please delete this post or merge with my later post here: https://community.adobe.com/t5/lightroom-classic-discussions/copy-settings-gt-subset-modified-ignores-crop/m-p/15501384

When applying the Color Profile “Adobe Standard” to an image in Lightroom Classic and then exporting as DNG. Then later importing the DNG back into Lightroom Classic, the Color Profile is set to “Adobe Color” instead of “Adobe Standard”.When opening in Photoshop, ACR shows “Adobe Standard” correctly. Lightroom Classic Version Number 15.3.1 Mac OS 26.5.1  Reproduction Instructions:Either use a random image, set the Color Profile to “Adobe Standard” and export as DNG. Then import the DNG back into Lightroom Classic and see it applies the “Adobe Color” profile.Alternatively, import the attached DNG file and see that the Color Profile is set to “Adobe Color”. Open it in Photoshop and see that the Color Profile is set to “Adobe Standard”.Expected Result: Lightroom Classic also applies the correct Color Profile: “Adobe Standard”.The Actual Result: Lightroom Classic applies the “Adobe Color” profile.Lightroom Classic:  ACR:  

I applied Denoise to 115 files by selecting the files, select Autosync, the clicking the check box on Denoise.  After all files complete Denoise, I again selected the same 115 photos, select Autosync, then uncheck denoise.  The process starts and a status bar appears labeled “Removing Denoise on 115 photos”.  The status bar progresses but after a short time stops.  Checked the photos and find the first 21 have had denoise removed.  Did “Optimize Catalog...” and then restart.  Tried to denoise the remaining 94 photos. Same result as before but this time it denoised another 21 photos before hanging up.  Restart, the did the same process to remove denoise on the remaining 73.  This time it removed denoise from 18 before hanging up. LrC is unable to remove Denoise from the entire set of selected photos.   LrC 15.3, Win11 

black and white outline on my pictures in lightroom classic after update  v15.3 ->  Filmstrip 

Since I updated to MacOS 14.6, printing from Lr Classic to my Epson SCP800 has beeen a nightmare. The printer driver seems to have become completely unreliable.    1. When I select a profile in Lr, the printer driver has color matching set to Epson Color Controls, and not (as it should) to Color Sync. Sometimes the driver opens with Color Sync correctly set, but then changing any other setting (eg, paper type) causes it to revert to Epson Color Controls.   2. When I make changes to the print settings (eg, changing paper type) and save a preset, the change is not present in the preset. This problem does NOT seem to occur when using the print driver from Apple Preview.   I have -- reinstalled the Epson drivers -- deleted and readded my printer -- deleted my Lr preferences (but I'm confused about this because moving the com.adobe.LightroomClassicCC7.plist file out of ~/Library/Preferences doesn't seem to change anything in my Lr setup, even if I restart my machine

After updating to LHR classic 14.1.1 LHR stops shwoing metadat in the lybrary module as well as in the developement module (loupe info). Closing LHR and deleting the files: ...Helper.Lrdata, ....Previews.Lrdata as well as ....Sync.Lrdata helps, as they are created each time new when starting LHR.  But after working for about 10min all the metadata disapears again.  I have installed LRH fresh and reset all settings. Nothings seems to help. I have a attached a screenshot but I wonder if that helps - there is just that spinning wheel.     Any suggestions?    P.S. I have a large catalog with about 200.000 photos in it but have had no issues so far. Big Windows PC with plenty of power. 

If a plugin calls catalog:updateAISettings() immediately after photo:applyDevelopPreset(), the application of the preset is ignored. This bug was introduced in LR 15.3, likely with the background processing of AI commands. To reproduce on LR 15.3 / Mac OS 26.4.1: 1. Import the attached preset “_Update Bug.xmp”. 2. Put the attached file “updateaisettings-bug.txt” into the LR Scripts folder. 3. Go to Develop with a test photo. 4. Do Scripts > updateaisettings-bug. Observe that Exposure is not changed (incorrect -- it should change to 4). 5. Apply the preset “_Update Bug”. Observe that Exposure changes to 4 (correct). A workaround is to call LrTasks.sleep (0.1) before calling catalog:updateAISettings().

Hello,I recently posted on Intel's forum regarding problem with heavy gpu tasks on my laptop.They asked me to post here to see if people on Adobe's side have any idea on how to fix this, and to cooperate. My laptop is an Asus Zenbook (UX3405CA) : - I9 285H - Intel Arc 140T 16Go updated with the latest available driver (32.0.101.8331) - The problem is still there with older drivers - Windows 11 pro up to date - Lightroom classic version 15.1 - Tried with older versions of Lightroom - The BIOS has been updated- Cleanded drivers with DDU in recovry mode then reinstalled through intel utility tool - Recleaned them with DDU in recovery mode then reinstalled through MyAsusThe problem persists.I get a LiveEventKernel with the code 141 in the event viewer every time the problem arises.I have attached some relevant files, but can't add the dump because the format is not accepted.I need your help to fix this problem permanently.Thank you

I re-edit a photo from Lr Classic in Photoshop. It is in my target collection which is my sync collection. Lightroom Classic says the sync is done. The new version is visible in Lightroom on the web (Chrome). The thumbnail in Lr Mobile is correct. When I open the image in Lightroom Mobile it reverts back to the old previously edited version. Thanks