Bug Reports

Hello, my raw files are getting color distorted in Lightroom.I tested different card reader, different apps and different PCs.This issue is showing on exactly one PC, not any other in the household.I will try updating graphics drivers tomorrow, Lightroom was up-to-date in the time of the incident.Image shows distorted even when exported.Attaching examples of affected images.Thank you for your tips. 

I am an editor for another photographer who sent me an LrC catalog with Smart Previews. An important detail: he uses MacOS and I use Windows 10. He has recreated the catalog multiple times, but the same error keeps happening: an exclamation mark appears on the image with the message 'Lightroom has encountered problems reading this photo'. I've already moved the files from my C:// SSD to another SSD, but the issue persists. I am running the latest version of the software. Here is my system information:Versão do Lightroom Classic: 15.4.1 [ 202606201310-b9f148a4 ]Licenciar: Creative CloudConfiguração de idioma: ptSistema operacional: Windows 10 - Business EditionVersão: 10.0.19045Arquitetura do aplicativo: x64Arquitetura do sistema: x64Contagem de processadores lógicos: 8Velocidade do processador: 3,6GHzVersão do SqLite: 3.36.0Versão do Adobe GSDK: 1.4.0.213Uso da CPU: 1,0%Fonte de alimentação: ConectadoMemória interna: 32683,8 MBMemória GPU dedicada usada pelo Lightroom: 38,7MB / 5966,0M

Expected Result:Lightroom Classic should successfully export a batch of raw images using full GPU hardware acceleration.!--tgqphd||[]-->!--tgqphd||[]-->Actual Result:!--tgqphd||[]-->The system immediately crashes into a Windows 11 Blue Screen of Death (BSOD) with BugCheck code: 0x00020001 (HYPERVISOR_ERROR)!--tgqphd||[]-->.!--tgqphd||[]-->!--tgqphd||[]-->Steps to Reproduce!--tgqphd||[]-->Open Lightroom Classic.!--tgqphd||[]-->!--tgqphd||[]--> Go to Preferences > Performance and ensure "Use Graphics Processor" is fully enabled (including for Export).!--tgqphd||[]-->!--tgqphd||[]--> Select a batch of raw images and begin a heavy export.!--tgqphd||[]-->!--tgqphd||[]--> The system immediately crashes into a BSOD mid-export.!--tgqphd||[]-->!--tgqphd||[]-->!--tgqphd||[]--> !--tgqphd||[]-->Workaround Found:!--tgqphd||[]-->Turning off GPU hardware acceleration specifically for Exports!--tgqphd||[]--> inside the Performance preferences

This bug causes DATA LOSS.Description of Issue After viewing duplicates using the new LR15.4 Find and manage duplicate photos feature, and marking some photos (either Original or Duplicate) as Rejected, the use of the “delete rejected photos” function (e.g., through the keystroke cmd-Delete) will cause all photos to be deleted from disk and from the catalog, not just those marked for rejection. Lightroom Classic Version Number (Help>System Info…) Lightroom Classic version: 15.4 [ 202606101834-493069d4 ] OS Version Number ​​​​​​​MacOS 26.5.1 (25F80) Step-by-step Reproduction Instructions ​​​​​​​add a photo, and a duplicate of that photo, to a LR catalog. switch to Duplicates view; the two photos should appear in a stack. mark one of the two photos Rejected. cmd-Delete to delete rejected photos confirm. The Expected Result ​​​​​​​only the Rejected photos disappear from disk and the catalog. The Actual Result ​​​​​​​all the photos - even those not marked Rejected, disappear fr

I’m trying to open the Lightroom desktop app on a 2021 Macbook Pro. It looks as if the app starts to open, but then crashes immediately. I’ve tried restarting my laptop, uninstalling and reinstalling lightroom, and signing out/signing back into the Adobe Creative Cloud app. I’m still able to access other Adobe products on the laptop, it’s just Lightroom itself that’s unable to open. I can’t provide any screenshots, since the app itself won’t open.  It’s not Lightroom Classic, but the new Lightroom app. 

My LrC 15.3 catalog (approx. 75000 photos, wherof 30000 photos are virtual copies) was completely indexed for Assisted Culling.After updating to 15.4 LrC started to rebuild the index.After maybe 2 hours (indexing about 3000 photos) an additional 100GB ofvirtual memory (the system has 64GB memory) are used up and the system becomes unusable. It then requires to reboot the system, otherwise starting LrC takes about half an hour, but even then the catalog selection dialog is non-responsive.I could reproduce this behavor at least 4 times.When the Assisted Culling indexing process is paused, LrC seems to run normal.====Lightroom Classic-Version: 15.4 [ 202606101834-493069d4 ]Lizenz: Creative CloudSpracheinstellung: deBetriebssystem: Windows 11 - Business EditionVersion: 11.0.26200Anwendungsarchitektur: x64Systemarchitektur: x64Anzahl logischer Prozessoren: 16Prozessorgeschwindigkeit: 2,3GHzSQLite-Version: 3.36.0Adobe GSDK-Version: 1.4.0.213CPU-Auslastung: 11,0%Stromquelle: AkkuIntegrierter

Description:When working quickly in the Develop module — applying an adjustment, navigating to the next photo with arrow keys, then immediately applying another adjustment — the second adjustment is visually applied for a fraction of a second, then automatically reverted. Both the image and the slider value return to their prior state. This is not a display/refresh glitch — the slider value itself rolls back, indicating the catalog write is being overwritten.Steps to Reproduce:Open Develop module, select any photo. Apply an adjustment (e.g., Exposure +1.0). Press the Right Arrow key to move to the next photo. Immediately (within ~0.3–0.5s) apply another adjustment (e.g., Exposure +1.0) via slider or keyboard shortcut. Observe: the adjustment briefly appears, then both the image and the slider revert to the original (unedited) state.Expected Result:The adjustment applied in step 4 should persist, as it does when waiting ~1 second after switching photos before adjusting.Actual Result:The

Lightroom Classic Version: 15.4Camera Raw Version: 18.4Platform: macOS (Apple Silicon, MacBook Pro M1 Max)Issue:I accidentally started AI Assisted Image Selection on my entire catalog containing 262,118 photos.After starting the analysis, Lightroom began analyzing the complete catalog. CPU usage increased to between 200% and 400% and remains at that level continuously.The problem is that I can no longer stop the analysis process.Observed behavior:The Activity panel shows: Assisted Image Selection: Paused Duplicate Detection: Paused Face Detection: Paused Address Lookup: Paused All options in the Assisted Image Selection panel are disabled. The panel currently shows 0 selected and 0 rejected photos. Batch Actions is disabled (greyed out). Nevertheless, Lightroom still displays “Photos are being analyzed”. CPU usage remains between 200% and 400%.Troubleshooting already performed:Quit and restarted Lightroom Classic. Restarted macOS. Disabled Wi-Fi completely and restarted Lightroom.

15.4 - Mac version - Apple SiliconIf I hold down the left or right arrows keys while in Library Module and I hold a touch too long (only like 1 second) it will scroll uncontrollably in that direction and it’s hard to get it to stop. (my shoots are large and it can easily scroll many hundreds of photos before I can get it to stop) This is a new behavior and did not do this in recent versions. (I believe there was a time years ago that this happened.) It does not happen in Develop Mode.

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? 

So if I select 10-20-50-100 images, doesn’t matter, and I apply AI denoise to all of them, Lightroom Classic starts doing the AI denoise in the background. I can go to the develop module, start editing any other images, I can even use the previous button, etc. BUT the moment I copy settings from one image to another, the AI denoise in the background stops and it stays in that stuck position. I can’t edit any of those images until I restart Lightroom Classic. When I hit the copy settings button(on the keyboard), it finishes the denoising on the current image that it has been doing, but it does not continue on the next photo. Everything just stops.So basically if you apply AI denoise to images with copy and paste settings, then you can’t use the copy settings function until the denoise process finishes.Only workaround is to use sync settings for AI denoise and then you can work with copy settings and paste settings on another images in the meantime.Maxed out 16” M1 Max MacBook Pro 64gb R

In the Remove tool, there’s the healing and clone stamp tool which have to have a source. In previous versions if you hold down cmd on mac, and you drag the point, you can determine where the source should be exactly. And the original point where the healing takes place should show a preview of the source. In Lightroom Classic 15.4 when you hold down cmd and then drag the pointer of the heal or clone, you can not see the preview, only if you let go of the mouse. I attached a screenshot, it clearly shows that the healing doesn’t update the preview of the source.How it should work: It should display the preview of the source as it worked in previous versions.Software: Lightroom Classic 15.4Hardware: M1 Max MacBook Pro

라이트룸 클래식최신 버전 사용, 애플 맥북 m1max, 64gb, tahoe 사용중이며,카메라는 canon r3 사용중입니다. 테더링 촬영시 라이브 옵션을 사용할경우 카메라측에서 5~10번 정도 af와 셔터촬영을 했을경우,af를 잡지 못하고 셔터촬영이 되지 않습니다맥북상의 라이브화면에서만 af와 촬영이 가능합니다

Using an m1 Max, didn't have this issue prior to the latest update to version 9.4  Denoise introduces banding that continues on through to exported files.  Not an issue prior to the update.

Environments: Device 1: Mac Studio M1 Max (32GB RAM) OS 1: macOS 26.5.1 Device 2: MacBook Pro 16 M4 Pro Application: Lightroom Classic Description: The new Assisted Culling feature with faces is completely unusable. Navigating through images causes the entire application to hang repeatedly.Steps to Reproduce: Open Lightroom Classic. Ensure Standard Previews are completely generated and AI Culling has finished analyzing the entire folder. Verify no background tasks are running. Start navigating through the images using the new Assisted Culling feature for faces. Actual Behavior: After viewing a few images, the entire application freezes for 15-30 seconds. When it finally unfreezes, it rapidly skips forward by about 10 images. It works normally for a few more images before the severe freeze happens again.Troubleshooting Steps Taken: Confirmed Standard Previews are fully generated. Confirmed AI Culling has completely finished analyzing the folder. Confirmed absolutely no b

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.

This is my post from nine years ago:  It’s STILL an issue  after the full rewrite of the plugin.  How de we get this addressed?  Capture One and Canon’s EOS Utility get this right.  Lightroom Classic does not. I’m using an EOSr5 in an M3 MacBookPro running 26.5.1

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?

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

I encounter an issue with the latest update (V11) on shortcuts to assign a color label (6,7,8,9).Those shortcuts won't anymore assign a color label, it will now only remove the color label. The shortcut "Assign a color label and go to next photo" (Shift+6 to 9) still work well as previously.Please fix this adobe, my culling speed depend on it. Thanks in advance,

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!