Bug Reports

After updating from 15.5.1 to 15.6, the dialogue boxes are FAR brighter.  The medium grey has been replaced with much brighter elements.  I ended up rolling back to 15.5.1 because of this!when will Adobe follow Mac’s dark mode?  And at least not make things BRIGHTER!this interface won’t let me attach images?

Lightroom Classic synchronization has been stalled for an extended period, initially under version 15.5 and continuing under 15.6.Approximately 1,400 photographs remain pending. Lightroom Classic displays the status "Uploading" with "Image" in the sync details.Steps to reproduce Open Lightroom Classic with synchronization enabled. Observe that existing photograph uploads remain stalled. Import a new JPEG from local Mac storage, independently of NAS storage. Create a new collection and enable synchronization. Add the JPEG to that collection. Verify that the collection appears in Lightroom Web and Lightroom Mobile. Observe that the photograph itself never uploads. Expected resultBoth the collection and its photograph should synchronize successfully.Actual resultThe collection synchronizes, but the photograph remains queued. Existing uploads also remain stalled.Previously, restarting Lightroom Classic advanced synchronization by approximately four photographs before stalling a

Lightroom Classic Version15.4.1macOSTahoe 26.5.2HardwareMacBook Pro (Apple Silicon)DescriptionExport as Catalog consistently fails when the destination is an external exFAT SSD.After several minutes Lightroom displays:“An unknown error occurred while exporting the catalog.”The partially created export folder is then deleted.The identical export succeeds immediately when the destination is the internal APFS SSD.ReproductionOpen any Lightroom catalog. Choose File → Export as Catalog. Select an external exFAT SSD. Export with or without negatives. Wait. Lightroom reports “Unknown error occurred while exporting the catalog.”ExpectedCatalog exports successfully.ActualGeneric error.Export folder deleted.Reproduces onSamsung T9 (exFAT) SanDisk Extreme SSD (exFAT)Does NOT reproduce when destination isInternal APFS SSD.The same catalog (approximately 415 GB including negatives) exports successfully to the internal APFS SSD in a few seconds. The resulting exported folder can then be copied to th

Camera profiles that contain two DNG 1.6/1.7 profile features load and can be selected, but the features have no effect on the rendered image:RGBTables (tag 52543 / 0xCD3F) ProfileGainTableMap2 (tag 52544 / 0xCD40)This applies to external DCP profiles and to profiles embedded in DNG files, in Lightroom Classic and in Camera Raw in Photoshop. The DNG SDK 1.7.1 parses both tags in camera profiles, and its reference rendering applies them to the same files.Test 1 – RGBTables (SDR)Two DCPs for the Nikon Z 7, identical except for the RGBTables payload: one with an identity table, one with a defined chroma change. Each is a group (ProfileGroupName) with an SDR member and an HDR member (ProfileDynamicRange). Installed in %APPDATA%\Adobe\CameraRaw\CameraProfiles, Lightroom restarted. Applied to the same raw file with identical neutral settings (white balance As Shot, all sliders 0, sharpening and noise reduction 0, linear tone curve), HDR editing off. Exported as 16-bit TIFF, ProPhoto RGB. Res

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. 

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. 

I recently got a 5D IV and just noticed that capture times on video files shows 5 hours ahead in Lightroom (photos are fine). This causes videos taken late in the day to be imported into the folder for the next day. I'm running the latest Lightroom (6.10) and 5D Firmware (1.04). I checked my old 5D Mark III videos and they are fine. I suspect Lightroom ins't picking up the timezone info and is using UTC time.  Is this a bug?

My basic issue is that Library previews do not update reliably in Lightroom Classic after work is done on a TIFF file in Photoshop, whether the “edit (original) in Photoshop” command is used, or the file is simply opened from the Finder and edited. It started a few months ago. It’s intermittent: sometimes previews update immediately, perhaps half the time, though it seems to be getting worse. Sometimes I can force Previews to update using one of several methods gleaned from this forum or other research (see below), sometimes nothing will work except re-saving the file in PS, then reimporting it to LR, OR making an (un-needed) adjustment in the Develop module to trigger preview update in Library. The excellent Lightroom Queen web site suggested I try a bug report as they couldn't come up with a solution for me. After several weeks troubleshooting I’ve learned that making an adjustment to a parameter in Develop, even a very small one, seems to trigger the preview to appear correctly

I noticed after updating my new v10 converted catalog that LrC was acting slow in the Library module, so I disengaged the usual culprit for this, the "Automatically write changes into XMP" setting. Then to my dismay, I noticed that it proceeded to mark the majority of the photos in the current grid view as needing a metadata update, even though the catalog metadata was fully saved to XMP prior to the upgrade, as far as I was aware.   Then I paged down, and the pattern repeated: Lightroom scanned all the now-visible photos and found that almost all of them also needed to be updated on disk.   And I did it again. And again.   Eventually I wrote a script to send "Page Down" events to the program periodically to ensure that Lightroom looked at every photo in the catalog, then let it run overnight with the library filter set to "Metadata Status = Up to date", so that it would give me the list of photos that need no metadata update. The next morning, I scrolled the grid back u

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.

Lightroom Classic 15.5.1 and prior versions. Using MacOS, but I doubt that matters for this bug.When using the Dust removal tool (in the Distraction Removal panel), if you rapidly add dust removal spots, the “Removing New Dust Spot...” dialog will stick and not disappear even after LR has finished adding the spot.Steps to reproduce:Enable Dust removal. Start rapidly clicking multiple spots, without giving each time to complete. The busy dialog will popup, timeout, but fail to dismiss automatically. Manually press Cancel to dismiss it yourself.

In Lightroom Classic, after I created a new catalog, the file originally displayed the correct LrC logo. However, the logo has now disappeared and is no longer showing on the file icon. Tried all neassary process but not working.

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.

自動補正を全体にかけハイライトやコントラス、彩度などの項目ごとの設定を同期するとチェックしていない項目がリセットされて0となってしまいます。   11.3.1のみこの状態となっており11.3では問題なく同期できました。

When a video is exported from Lightroom Classic that does not have the size 1920x1080 pixels, it is scaled down. Videos that are in portrait format (1080x1920 pixels) are scaled to 960x540 pixels. A video with 1440x1080 pixels becomes 1280x720 pixels when exported. Do not scale videos during export.  

When a video is exported from Lightroom Classic, the “Capture Date” (CreateDate or DateTimeDigitized) is overwritten with the time of the export. However, the “Capture Date” must not be changed during export. It works when exporting photos.

Exporting a portrait video at Quality: Max (up to 4K) chooses a target resolution that is much less than 4K, with a lower frame rate than the source. To reproduce on LR 15.5.1 / Mac OS 26.6.2: 1. Open the attached catalog. 2. Select the video Portrait.mov and do File > Export. 3. In the Video section, select Quality: Max (up to 4K) and observe that the Source resolution is 2160 x 3840, 60 FPS (correct), but the target resolution is 1920 x 1080, 30 FPS (incorrect) -- it should be 3840 x 2160 (or similar horizontal 4K resolution), 60 FPS:  4. Do the export and observe that the resolution of the output is indeed 1920 x 1080, 30 FPS (incorrect), with the portrait video inserted as letterbox (black borders on the left and right).  The exported video should be 3840 x 2160, 60 FPS (or similar horizontal 4K resolution), with the video inserted as letterbox. 5. Select Landscape.mp4 and export it with Quality: Max, and observe the Source resolution is 3840 x 2160, 60 FPS and the Target resolu

In LrC, German version 15.5.1, Camera Raw 18.5.1, the tool tip for “Punktfarbe”, “Hue Range”, the lower triangle, says “Geringere Abfallkante”. I presume the tool tip in the English version is something like “lower edge”, “lower threshold” or “lower limit” or “lower ramp”. In any case, you would not translate “lower” into “geringer” in such a situation. You would use “Untere” instead, which matches “Obere” for the upper end. Geringer would translate to smaller or less in this context, in the sense of “not as high as something else”, which is arguabely not what you want to say. Note that my mother tonge is German and I am an electrical engineer. Feel free to contact me if you need further input or insight at <Email redacted by Mod> Kind regards, Markus

I am a photojournalist and recently switched from a PC to a MacBook (last week). My workflow has been rock-solid for many years, and my old archive copied over to the new Mac system without any issues.My Workflow: Preview & Culling: Photo Mechanic Editing: Photoshop 27.9.1 / Adobe Camera Raw Saving: Exported/saved as DNG files Archiving: Import DNGs into Lightroom Classic 15.5.1 The Issue: For my commercial side work, I regularly apply the "Adaptive: Color" profile to my Raw files. However, since switching to the Mac, when I import these newly edited DNGs into Lightroom Classic, LrC fails to apply or read the "Adaptive: Color" profile. The images import looking completely flat.What I've Tried: I read that updating the AI settings in Lightroom might resolve this, but it did not work. Manually reapplying the Adaptive Color profile inside Lightroom does fix the image, but this is way too time-consuming and defeats the purpose of my workflow. Note: Older images processed this

When I try to import picture files, I get a popup for assisted culling that locks the application. I need to go to task manager to shut down the application.   I turned off assisted culling under catalog settings, but this does not correct the issue. Is anybody else experiencing this issue. I cannot import new files!  

LRC 15.3Windows 11 Step to reproduceConfigure auto import. Don’t rename and don’t apply any preset. Keep is simple  Auto import settings  Copy a photo in the auto import folder. The photo is imported automaticly Launch a normal import with the "don’t import suspected duplicates" box checked Point to the initial folder were the photo was (not the auto-import one) The photo that is already in the catalog is not greyed. You can reimport it and create a duplicate even if you ask to avoid duplicates. Kind regards

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().

I have many video files imported into LrC that I want to modify the filename.  The video files were taken with the iPhone 17 Pro.  My usual method to edit the filename is to edit the filename entry in the metadata panel.  When I use the method I get an error message that the filename cannot be edited.  If I use the alternate method of using the F2 key, I get the same error message.  I have submitted another bug report about not being able to import video files into LrC 15.5.  That bug report has been “Acknowledged”.  In that case reverting to v15.4 allows imports. Unfortunately reverting to v15.4 does not fix this issue.