Bug Reports

This has been happening for probably a week or two. I have it by default apply content credentials to every jpg I export - can’t hurt, right?In every single export lately, a random number of them ‘fail to apply’ and hence do not export at all. I have to keep going to the export dialog, click ‘skip’, and it will export a few more and fail to export a random number. Currently I have done this 8 times to a set of 148, and am down to one single file that it just doesn’t seem to want to apply them to ever. I assume this is a bug and I should give up on credentials until this is fixed.  Mac Mini M4 Pro, OS 26.5.2 

Version: Lightroom Classic 15.5.0.8OS: Windows 11 Pro (build 10.0.26100)GPU: NVIDIA RTX 3090, driver 32.0.16.1088 (22/07/2026)RAM: 32 GBRepro: Run Assisted Culling / auto-stack-by-similarity on a large batch of photos. Crashes reproducibly — 5 identical crashes since 2026-08-09.Crash signature: Windows Application Error log shows Lightroom.exe faulting in ntdll.dll, exception code 0xc0000374 (STATUS_HEAP_CORRUPTION), consistently at the same fault offset (0x112165) across all occurrences.Context: App log shows the last command before each crash was ag.library.stacking.generateAutoStacksBySimilarity. Lightroom's process memory usage reached 13.5–14.6 GB (41–45% of system RAM) just before crashing, suggesting a memory-handling bug in this feature on larger culling batches. 

Auto updated to LrC 15.5 on my MacBook Pro M3 Max last night. Came home from shooting a concert and the import dialogue would appear to function normally, but after hitting the actual button to import, nothing happened. It went back to the grid view, briefly the import status bar appeared in the top left then just as quickly disappeared. I tried different ways of doing it, enabling full disk access (already was set), copy vs convert to dng, even created a whole new catalog and did a hard reset on my computer. Same issue every time. Decided to downgrade to 15.4.1 through the creative cloud as I was able to recently import and edit on that version. Opened Lightroom back up and viola, everything worked just fine. Gonna stick on this version and disable automatic updates until I hear adobe fixes this.

I updated to LrC 15.5 a few hours ago.  Since then LrC has problems with video files.  The first problem I noticed was that when I tried to synchronize a folder that had two new video files.  After a couple of minutes I got the error message “An unknown error occurred while reading the video file. (2)”.  I had just completed those files with DaVinci Resolve so I went back and produced the same files again to check if DR had made an error.  When I tried again with the new files but got the same errors.  I was able to play both videos without any issue using VLC Media Player, so they seem to be OK.  I then shutdown LrC and did a backup including optimizing the catalog, and then restarted it to see if that made any difference, but same error.  Then I started looking at other videos that were already in LrC and found that when browsing them in the Library module, most of them pop up a message “There was an error working with the video”.  They will not play in LrC but work fine with VLC Med

Lightroom Classic version 15.4Mac OS 26, Version 26.5.1Mac Studio M4 MaxPrior to the latest upgrade to Lightroom Classic I was backing up my catalog to my Synology drive. I now get the unable to write to drive error, check permissions and available space on the drives. I can backup the file locally on my MAC and then copy that over to the Synology drive. So it does not seem as though permissions is the issue. Have 16TB of storage on the Synology and 782 GB free on a 1 TB SSD on the Mac. Only started when after the latest upgrade to Lightroom Classic.

When I want to skip through hundreds or thousands of photos in Lightroom Classic (Version 15.0.1) in the film strip I mostly get this very annoying problem: after holding the arrow key to the right or left for a few seconds it doesn't stop anymore to speed through the images though I'm no more holding the arrow key. Sometimes it's going on for "just" a couple of hundred further photos and sometimes even through thousands of photos until the very last photo in the strip. I can't even stop it.This first started three months ago when I updated on a new MacBook. On my old Macbook this never happened in years. Does someone got an Idea to fix this bug?

When the Fetch Altitude For Coordinates button in the Location tagset of the Metadata panel is pushed while in the Map module, it correctly sets Altitude but it doesn't display it in the Metadata panel. This appears to be an old bug filed in 2019 that didn't get migrated from the old feedback forum: https://community.adobe.com/t5/lightroom-classic-discussions/map-module-altitude-of-the-points-si-0-in-the-gps-coordinates-of-the-photos/m-p/10313076#M136897    To reproduce on LR 13.2 / Mac OS 14.2.1:   1. In Library, select a photo that doesn't have any assigned GPS coordinates.   2. In Map, drag the photo to the map. Observe that it gets assigned GPS coordinates but not Altitude (correct).   3. Click the Fetch Altitude For Coordinates button. Observe that the Altitude field remains blank (incorrect).   4. Go to Library and observe that the Altitude field is filled in (correct).   5. Go back to Map and observe that the Altitude field is filled in (correc

The option Catalog Settings > Metadata > Include Develop Settings In Metadata is not working correctly -- develop settings are still getting included in the exported metadata and .acr files (which contain develop settings) are sometimes getting exported. The   Metadata Status field is also not working correctly. Tested with LR 15.5.1 / Mac OS 26.6.2: 1. Download and open this tiny catalog and select the single photo:https://www.dropbox.com/scl/fi/f32l8iyi85gldfbd1xiew/ccbug.2026-09-01.zip?rlkey=hkwadikr9tkhdxcha1dgparms&dl=0 2. In the Metadata > EXIF AND IPTC panel, observe that Metadata Status is Up To Date. 3. In Catalog Settings, observe that both Metadata > Include Develop Settings and > Automatically Write Changes Into Sidecar are unchecked. 4. Export the photo to Desktop with Image Format: JPEG, using these settings:  5. Using Exiftool, observe that the develop settings are incorrectly included in the XMP section of the exported photo:[XMP] Exposure 2012 : -3.0

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

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

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

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?

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.

Select a number of photos say about 200 on the film strip. auto sync on Hit auto to adjust the settings automatically. Can be done on library or develop module does not matter to the issueLightroom will adjust the settings automatically and you can go to different photos and the automatic settings would have been applied to all the photos.Now adjust one setting on one photo with auto sync on (eg. bring the vibrance or saturation down back to 0 or a different amount….in this case vibrance to -5)Browse the rest of the photos … The rest of the photos should now have auto adjustments applied + the vibrace slider to where you adjusted it manually. However when I do this other than some photos that are in immediate to left and right of the photo that was active while I did the vibrance adjustment the rest of the photos has the auto adjustments back down to 0 and the only vibrace is at -5. This seems to affect tone and vibrance saturation.. not presence (probably because auto does not affect

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

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!