Lightroom Classic

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

After starting LR, clicking the GPS badge of a photo centers the map on the last-displayed location rather than the coordinates of the clicked photo. To reproduce on LR 15.5 / Mac OS 26.4.1: 1. Open the attached catalog. 2. Go to Map view. 3. In the filmstrip, click on the GPS badge of "miami.jpg". Observe the map centers on Miami (correct). 4. Go to Library. 5. Restart LR. 6. Click on the GPS badge of "san francisco.jpg". Observe that the module switches to Map view and the map centers on Miami rather than San Francisco (incorrect). 7. Go to Library. 8. Click on the GPS badge of "san francisco.jpg" and observe the map moves to San Francisco (correct).  

Steps to Reproduce: 1. Select an Ai mask2. Move any of the Refinements sliders from form the current value to another one and back to the current value but NEVER releasing the slider.Actual Result: A step is recorded in history but nothing changed from step 1 and step 2, the value chosen in UI is the same.Expected Result: Moving AI masks "Feather" or "Edge" sliders DOES NOT record an history step when the UI value is the same as before.Addendum: There is floating point difference in the values when moving a slider back and forth to the same value but it should not matter.Feather at 30 Feather moved from 30 to 30 again 

Lightroom bug - hit a folder limit and unable to select the newly imported folder.452497 photographs across many drives in one catalog.The S drive has 214341 photos. It's the largest drive and so had many more folders than the previous drives.S:\Master Photos\ contains ~1633 folders. I know that's a lot but that is how her filing system was started. Those are the sequential numbers from 2220 - 3853 but there may be a sub folder or two or deleted folder in there so that's why the number is ~ approximate.Folders are labeled "sequential number"-"date" so 3853-20150316Adding one more folder caused Lightroom 4 to not allow the last folder to be clicked on and not show any images. The T:\ drive (offline, collapsed and below the S:\ drive) was collapsed and the label was overlaid on top of the "Collections" section label. Updated to latest version of Lightroom 5 via her new cloud account, had it rebuild the catalog and the same problem occurred.Created a sub folder S:\Master Photos\2012 and m

EnvironmentMac mini M4 24 GB unified memory macOS Tahoe 26.5.2 Lightroom Classic 15.5 Apple Silicon / arm64 Lightroom Classic catalog with images using AI masks, Remove and Lens BlurProblemLightroom Classic produces random blue horizontal lines/artifacts on images after AI processing.The artifacts are variable and may appear only several seconds after selecting the image in Develop. They can also be present in exported JPEG files.The problem appears to be strongly related to Lens Blur.Reproducible behaviorI can reproduce the problem with the following sequence:Open an image containing AI masks and/or Remove edits. Apply Lens Blur. Lightroom starts AI processing in the background. After some time, random blue horizontal artifacts appear in the image. The artifacts can also appear in exported JPEG files.The behavior is not simply a display-only problem because the artifacts can be present in the exported JPEG.Important observationsWith Graphics Processor disabled:Lens Blur ON → blue arti

Apple ProRaw images taken in Apple's camera app on my iPhone 14 Pro generally work well in LrC these days, which is great. In LrC I often use the "Apple ProRaw" profile.   When I perform a panorama merge of these images, however, LrC reports that the resulting .dng file is using the profile "Apple Embedded Color Profile" but shows an exclamation mark: "Profile missing." See attached screenshots.   I wonder if this is an inadvertent result of LrC's rule that only Apple ProRaw files have the option of the LrC ProRaw profile, and that the merged file is not recognized by LrC as a ProRaw file. Can this please be improved, or is there a workaround?   Thanks, Wallace

Hola;Es mi primer post, he estado indagando por la comunidad, y no he acabado de encontrar la solución.Uso LRC en un MacBook Pro y en varias ventanas de ajuste tengo problemas de redimensionar (salen cortadas). Me di cuenta en la de ajustes de mascara (adjunto captura), pero repasando algunas otras secciones como Ojos Rojos, Recorte… también tengo el mismo problema (adjunto capturas)He probado en modo pantalla completa y nada, se queda igual.Alguien sabe como solucionarlo? Es muy molesto no poder trabajar bien.Muchas gracias.  

The new Lightroom version has a major bug in the map module!When you try to position a photo somewhere on the map Lightroom 6.8 assigns a wrong position (near the spot).

Description of IssueI believe that at times, Lightroom Classic 15.5 produces phantom pins on the map, that is, pins that appear to be locations of photos, but either the count of images is wrong, or the pin itself doesn’t work (when you hover over the pin, nothing happens), or both. I understand that a major malfunction of the Map module was fixed in 15.5, but this seems like a different problem.Lightroom Classic Version Number (Help>System Info…) Lightroom Classic 15.5OS Version NumberWindows 11 25H2 (26200.9168)Camera Model (sometimes necessary)Nikon Z6 IIStep-by-step Reproduction Instructions (in precise terms, please)Step 1: Select a lot of images and display the map (in my case, all photos in New York State). Zoom in. Notice the cluster of pins right in the center of this screen capture (I have drawn a red box around them). Step 2: press the plus sign to zoom in more. Let’s focus on the bottom of this cluster of pins. Notice the area indicated by the arrow, there are three pins

Versione di Lightroom Classic: 15.5 aggiornamento di agosto 2026Sistema: MacOs Tahoe ultima versioneFile: Nikon raw convertito in DNGComportamento: sistematico, sempre riproducibileDescrizione: nell’immagine c’è una persona che voglio rimuovere. Dal modulo Sviluppo seleziono “Rimuovi” e spunto “Usa IA Generativa”. Clicco su “Persone”, attendo che LrC trovi l’area con la persona da rimuovere e premo “Rimuovi”.Da questo momento non sarà più possibile salvare i metadati, nel senso che LrC visualizzerà sempre “Metadati non salvati”. La situazione si risolve cancellando la rimozione. Nota: quando premo CMD+S sul file, per salvare il file, comunque qualche modifica viene apportata poiché il finder del mac aggiorna la “Data di modifica”.

Compare view often incorrectly labels a photo as having an embedded preview. To reproduce on LR 15.5 / Mac OS 26.4.1 (see the attached screen recording): 1. Download and open the attached catalog. Observe that Catalog Settings > Standard Preview Size is 2880. 2. Right-click folder "test-pics" and do Synchronize Folder, selecting Show Import Dialog Before Importing. Set the import option File Handling > Build Previews to Embedded & Sidecar. Observe in Grid view that X.ARW is marked with the embedded-preview badge (correct). 3. Do Library > Previews > Build 1:1 Previews, selecting Build All. Observe that neither photo has the embedded-preview badge (correct). 4. With X.ARW selected, go to Compare view. Observe that it says Embedded Preview at the bottom of X.ARW (incorrect). 5. Go to Grid view. 6. Select X.jpg and go to Compare view. Observe that X.jpg is labeled with Embedded Preview (incorrect). 7. Go to Grid view and restart LR. 8. Select X.ARW and go to Compare view.

Yes, this exact question has been raised many times in the past and those posts have all been closed as “answered” without any resolution.  This is still an issue.I open LrC, import and make edits.  LrC sits idle with computer running for at least an hour.  Try to close LrC and it spends several minutes  "Writing Metadata Changes into XMP" before the app exits.  What is LrC doing while idle after the last edit was made that it now needs to do when I’m trying to shut down the computer?  This is unacceptably poor performance but vaguely understandable as edits were in fact made.  Why are the XMP writes not happening during idle time rather than forced immediately at exit?The same delay occurs without making edits.  Open LrC, make no edits and immediately try to open another catalog.  LrC shows the "Writing Metadata Changes into XMP" message for several minutes before finally restarting with the other catalog.  This is after LrC spent several minutes  "Writing Metadata Changes into XMP" p

Just starting today the Map module is leaving behind markers for a photo or photos that have been moved. It also continues to show markers for photos that have been opened but are no longer in the directory being worked in. If I leave LRC and come back in, all is well but I've never had to do this before. It is more of an annoyance than a major issue, but it does clutter up my screen while moving things. I am in the process of locating old photos that have inaccurate or no geotagging and this behavior is slowing me down. I’m running 15.3 on a MacBook Air. Has anyone else seen this or have a suggestion of how to fix this behavior? 

LR 15.5 made numerous inconsistent and incorrect changes to how the Delete and Backspace keys are  translated in Help > Library Module Shortcuts and Map Module Shortcuts. Prior to 15.5, LR followed the principle of using the names of the keys as they appeared on the most commonly used keyboards for that language. For example, on Spanish (ES) keyboards, the Delete key is labeled Supr, and LR's Help used Supr for the Mac shortcuts for Library > Remove From Library, Map > Delete GPS Coordinates, and Map > Delete All Location Metadata. This convention makes sense -- Help uses the names of the keys that are displayed on the user's keyboard. But in 15.5, the displayed names of the Delete key (Mac) were changed in all 15 non-English languages, for some but not all of the commands assigned Delete.  Similarly, the displayed names of the Backspace key (Win) were changed in 6 languages, for some but not all of the commands assigned Backspace. For example, in Spanish, the name for the

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”. 

 EnvironmentAdobe Lightroom Classic 15.4 (also observed in earlier versions) Lightroom SDK Windows 11 Standalone reproducer plugin attachedSummaryA floating dialog opened via presentFloatingDialog() becomes the active window, but no control initially receives keyboard focus.As a result, standard keyboard interaction is unavailable immediately after the dialog opens. Pressing Enter, Esc, Space, or Shift+Tab has no effect. Keyboard navigation only begins after pressing Tab once (or after clicking any control with the mouse).The same reproducer behaves differently on macOS, where the first control immediately participates in keyboard navigation.Steps to ReproduceInstall the attached reproducer plugin via File > Plug-in Manager > Add. Run File > Plug-in Extras > Floating Dialog Keyboard Focus Reproduction Without using the mouse, press the following keys in order: Enter Esc Space Shift+Tab Finally, press Tab.A complete standalone reproducer plugin is attached. Expected Resu

When multiple videos are selected, Edit Capture Time incorrectly shows the message for a single photo selected, rather than a message that indicates the capture times of the other videos will be adjusted by the same amount as the first: When multiple photos and at least one video is selected, the message incorrectly states that videos will not be adjusted: But in these cases, the problem is just with the message being displayed. Clicking Change All correctly adjusts the capture times of the other videos by the same amount as the most-selected photo/video. Tested on LR 15.4.1 / Mac OS 26.4.1.

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

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

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