Lightroom Classic

Have been having a lot of crashes with LRc 15.4.1 for a week or so. Currently the situation is so bad, that moving from library to dev the app crashes every time. I’ve been sending a lot of crash reports. I’ve also tested multiple files from different cameras over past 20 years, the issue stays.I’ve also tested downgrading LRc, issue doesn’t go away. I also tested the other Lightroom, Photoshop, Bridge and Bridge (beta) - all crashing equally the same, when changing to dev/edit or in case of bridge an ps, just opening any raw file. This suggests that the problem is somewhere in Adobe shared runtime stack that is used by all of the apps. I also repaired Creative Cloud installation, no help. Files can be opened just fine in any other capable app. I created new catalogs to see if it was catalog corruption, but it is not. I have gone through all the usual Windows error checkings, sfc, dism, chkdsk, even the memory check. no problems there. All my other apps and even games work fine. Window

Lightroom Classic 15.4.1 on Windows: 1–2 second UI stalls when selecting photos — WPR trace points to MFC/Win32 window-handle processing Hello,  I am investigating a persistent Lightroom Classic performance problem on Windows. Selecting a different image can freeze the entire Lightroom interface for approximately 1–2 seconds.  This does not appear to be caused by RAW decoding, storage performance, the catalog, previews, GPU acceleration, plug-ins, or monitor refresh technology. Windows Performance Recorder traces consistently point to Lightroom’s main UI thread spending substantial CPU time in MFC and Win32 window-handle processing.  ## System configuration  - Lightroom Classic 15.4.1    Build: 202606201310-b9f148a4  - Camera Raw 18.4  - Windows 11 Business, build 26200.8737  - AMD Ryzen 9 5950X, 16 cores / 32 threads  - 32 GB RAM  - NVIDIA GeForce RTX 2080 Ti, 11 GB VRAM  - NVIDIA driver 591.86  - Catalog stored on an NVMe SSD  - 12 MP RAW files stored on another NVMe SSD  - Approxima

Sometimes, maybe. 1 in 10 when I edit in another program, LR does not properly make a copy with Lightroom edits. It will sometimes even make the copy of a version prior to some final edits I made. It’s almost always. a much brighter version of what it should have done. You can look at the copy and original and they are not the same.

This post applies to Lightroom Classic and the Lightroom Ecosystem products. Camera Raw feedback can be found here.   Generative Remove makes it easier to remove unwanted objects and distractions with a simple gesture, even on complex backgrounds. For more accurate results, be sure to include the object's shadow in your selection and/or expand its size.    Detect Objects uses AI to find the objects underneath a brushed area. The masked areas will now appear larger than the Early Access version of this feature. You can also circle objects for quicker selection now.    We have also updated the spot selection experience to make it easier to manage variations, switch the fill type, refine the selection area, or re-generate as needed.    Batch updating is also now supported for Generative Remove spots.    Try out the latest updates and share your feedback with us here. Please also include the following details in your post:  App versi

Installed this and my tethered camera setup no longer works.  It appears to work as before, but no images are transferred.  Canon R1, Windows 11.  Anyone else having tethering issues?

In LRC, I have many hierarchical keyword structures, amongst which are locations, i.e. Country/State/City and in some cases location or street name.  Since version 15.4.1, LRC deletes upper level location keywords (Country and State, or when there's a fourth level then it deletes the city too) after a photo has been synced to the cloud. The keywords still exist in the cloud. I have checked other hierarchical trees and the keywords are all syncing correctly. If I reenter the locations the save metadata to file, the keywords once again disappear.I'm running LRC 15.4.1 on a Windows 11 Pro computer with Admin rights. Lightroom, catalog and photos are all on (separate) local nvme ssds. Plenty of space, plenty of speed. 

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

I cannot create a file on the external disc like saving my pictures year 2024. I tried to pick and slide 2024 file to the external disc, nothing happen.

 Lightroom Classic Bug ReportTitleLightroom Classic reports "The file appears to be unsupported or damaged" for valid Lightroom-generated HDR DNG files. Product Adobe Lightroom Classic 15.4.1 macOS 15.7.x (Apple Silicon) SummaryLightroom Classic reports that certain HDR DNG files are unsupported or damaged.However: Adobe Camera Raw opens and edits the files without any problems. Adobe Photoshop opens the files without any problems. Adobe DNG SDK Validator validates the files successfully. Lightroom Classic itself reports the files as invalid ("Validate DNG"). The same behaviour occurs in a brand-new Lightroom catalog and also with backup copies of the same files.Steps to Reproduce Open Lightroom Classic 15.4.1. Import or open the affected HDR DNG. Lightroom reports: The file appears to be unsupported or damaged.The file also cannot be imported into a brand-new catalog.Expected ResultThe HDR DNG should open normally, since: it is a Lightroom-generated HDR DNG, it validates

EnvironmentLightroom Classic 15.4.1 macOS 26.5.2 Wacom Intuos PT S CTH-490 Wacom Driver 6.4.9Steps to reproduceOpen Develop module. Select Masking → Brush. Paint using a pressure-sensitive Wacom pen. Vary pen pressure.Expected resultBrush size/pressure responds to pen pressure as in Lightroom Classic 15.3.1.Actual resultPen pressure is ignored. The brush behaves as if a mouse is used.Additional informationDowngrading to Lightroom Classic 15.3.1 immediately restores pen pressure functionality using the same hardware, driver and operating system.No changes were made to the Wacom driver, hardware or macOS. Only the Lightroom Classic version changed.Control test: The same Wacom tablet and pen work correctly in Photoshop on the same Mac. Pen pressure affects brush size as expected. The issue only occurs in Lightroom Classic 15.4.1.

Lightroom Classic Version 12.1  OS Name: Microsoft Windows 11 Home Version 10.0.22621 Build 22621   Importing a .MOV file from a NAS drive into lightroom .MOV file originally taken on an i-phone 12 720x960 0.7 MP Imported video is rotated by 180 - so upside down .MOV file originally taken on an i-phone 12 960x720 0.7 MP Video is imported correctly

LR 15.2 introduced inconsistent names for the Backspace and Delete keys in the French in-program shortcut help. WindowsLibrary Help:Map Help:“Supprimer” is French for the Delete key. But on Windows, the Backspace key is called “Retour arrière”. MacLibrary HelpMap Help: On Mac, the Delete key is called “Supprimer”. So the two instances of “Arrière” should be replaced by “Supprimer”. 

Sync Settings with Upright Transforms checked doesn’t always check Copy automatically, as was intended by the undocumented change in LR 15.0.  To reproduce on LR 15.3 / Mac OS 26.2 (see the attached screen recording): 1. Save the attached file Upright-Transforms.lrtemplate (created in LR 14) to the Copy Paste Subsets subfolder of the Lightroom settings folder.  Restart LR. 2. Select two photos and do Sync Settings. Click Check None and click Synchronize. 3. Do Sync Settings again, select the subset Upright Transforms, and observe that Crop is checked (correct).  Click Synchronize. 4. Do Sync Settings again.Observe that the subset Upright Transforms is selected (correct) but that Crop is unchecked (incorrect). When you click Synchronize, the Crop is copied, even though it is unchecked.

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.

This is core to my workflow, an absolutely necessary feature I use every single time I’m editing photos. In the Develop Module, under let’s say the “Basic” adjustments panel, one should be able to adjust values (such as Exposure, Contrast, Highlights, Shadows, Whites, Blacks, etc.) while hovering the mouse cursor over a section of the photo (in the Loupe View) and see RGB values changing under the histogram.In the latest version, the RGB values are no longer displayed under the histogram while those values are being adjusted. For example, I click the number next to the ‘Highlights’ slider and move my cursor over to a white part of the image. When I press the up arrow on my keyboard to increase the value of that number, the RGB values under the histogram *should* be displayed and also increasing. Instead, they are not displayed at all.I have downgraded to the previous version and the program’s behavior returns to expected. This is a brand new computer, fresh win 11, AMD Ryzen 7 7700X; 3

What an awful release. Don't get me wrong, I'm glad to see new developments, but this Lightroom update is an absolute disaster. After culling just 5-10 images, the AI Assist culling tool completely hogs all my RAM, causing my Mac to freeze and throw memory errors. It’s a total nightmare.Culling images via the library module is practically impossible right now - everything just locks up. Even with previews pre-generated and trying to run AI Assist culling, the performance is still abysmal. On top of that, it frequently fails to even generate a Denoise. What is going on, Adobe?! This is absolutely unacceptable!P.S. The RAM management is completely broken and goes beyond any acceptable limits!  

Recipe:  When the secondary window is in grid view, it doesn’t always respond to the keyboard shortcuts “f”, Escape, or Shift+g.  To reproduce on LR 15.3 / Mac OS 26.4.1, follow these precise steps (see the attached screen recording): 1. In LR, go to Grid view, close the secondary display window if it’s open, and do Window > Screen Mode > Normal 2. Restart LR. 3. Do the menu command Window > Secondary Display > Grid to open the secondary window in Grid view. 4. Select a thumbnail in the secondary window and type “f”. Observe that nothing happens (incorrect). 5. Do the menu command Window > Screen Mode > Full Screen Preview (the command invoked by the shortcut “f”) and observe that the image is displayed in full screen. 6. Type Escape to exit full screen preview and observe nothing happens (incorrect). Typing “g” and Shift+g also have no effect (incorrect).   7. Type Cmd + Tab and then Tab to switch to an app other than LR. LR is now no longer in full screen mode. 8. C

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 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!

Letters in texts added in books in Book module are rotated in LrC 15.3. The rotation seems to happen per line as displayed (not per carriage return). Switching back to 15.2.1 put the letters correctly again, and upgrading to 15.3 rotates the letters.Attached two screenshots of the same page in a book in 15.2.1 and 15.3.15.2.115.3The letters are also rotated for a new book created in 15.3.

System: Mac M1 Air 16gb/512gb OS: Sonoma 14.3.1 LRC Version: 13.1 Release ---------------   Three Issues: 1) I have a preset folder with six custom presets.  When doing multiple exports using the batch export feature, LRC often doesn't launch the same number of processes as there are presets selected.  I select 6 presets and it will only do 4 sometimes, 5 others.  Sometimes it does all 6.  I have to examine the export folder, see which ones it missed, and go back and re-export the ones it didn't do.  Annoying.   Potential Fix:  If LRC can't do all of the processes because of system limitations (I don't know why on a Mac M1 that would be the case), at least inform the user which ones are being done and which are not.  Perhaps a loop to do sets consecutively with proper UI notification would be a good approach.   2) When doing multiple exports, a dialog comes up for each process, "Preparing to export".   "number of processes - 1