Bug Reports

Lightroom Classic fails to open after update to rev 16

Current update as of Nov 9, 2026Ipad Air 5 (M1) The remove masks are now backwards. I should be editing the right side of the sky. It wasn't like this this morning when I was editing (nor ever, of course).

Lightroom 10.0 — Sync Issues After editing photos in Lightroom, my changes weren't reflected in Shared Photos or Lightroom Web, even though synchronization showed as complete.Restarting Lightroom finally triggered the sync.As a professional designer, I realize this is a relatively minor bug, but it reflects a broader frustration with Adobe's creative applications. Recurring bugs and reliability issues are becoming increasingly frustrating.Compared to tools like Figma, which remain remarkably stable even as new features are introduced, Adobe's applications often feel unnecessarily unstable. As creative professionals, we depend on tools we can trust to work consistently, and reliability is becoming a real concern for me.Adobe really needs to prioritize stability and reliability over constantly adding new features.

In Lightroom Classic version 16.0, when using the Generative AI tool to remove dust spots, only the first click shades the area in red. Version 15.4 shades areas for all clicks. You can loose tracks of which dust stops have been clicked if only the first click is shaded.

Not really a bug, but with the latest new release of LR, the current/selected photo isn't sufficiently highlighted on the bottom thumbnail strip, to distinguish it from other thumbnails. Looking at the bottom row of thumbails, the current/selected photo should have a border around the thumbnail or a different background color than the other thumbnails. Currently its background color is barely distinguishable from the surrounding/other thumbnail background color

The option to use LrC-style panels in LR Desktop feels like it was implemented in a rush without sufficient  UX/QC testing. I've already discovered two rather critical issues with it:Not all panels have "hold to hide" buttons. Curves and Color Grading are both missing them. Furthermore, some other panels' buttons aren't mapped correctly (e.g. the Basic panel's "hold to hide" button also affects the Curves panel) Keyboard shortcuts aren't remapped, so the Cmd/Ctrl + [1-9] shortcuts now open panels out of order, and only if they exist with the same name (e.g. Cmd + 1 is useless now)

Inconsistent drag-and-drop behaviour with local files on macOS.In the Browse tab, dragging and dropping files from a CFexpress Type A card to a folder on my local hard drive causes Lightroom to COPY the files. The original files remain on the card.  In the Favorites tab, performing the same action causes Lightroom to MOVE the files. The original files are removed from the card.In the previous versions, Lightroom always copied the files, regardless of whether the folders and files were viewed in the Favorites tab or the Browse tab. This is the preferred method.Holding down Option, Command, or Control while dragging and dropping the files does not change this behaviour. Unfortunately, only using the Browse tab is not a long-term option.This behavior is really confusing and frustrating because it messes up my files on the card / camera. Thanks in advance for any help or suggestions how to solve the issue.

I have tended to manage the initial import of photos to LR via a local drive. Then selecting which to upload to the cloud. I always leave some time before clearing away old photos I don’t wish to keep, but before doing so I review the folders to ensure I have uploaded my “keepers” to the cloud. The filter options has worked well unto this new version, however it now does not appear to filter the presented images in the folder. 

Device/app: iPad Pro (M5), Lightroom for iOS 11.6.21, Fujifilm X-T50 RAW (.RAF)Workflow:1. Export the unmodified RAW original from Apple Photos.2. Edit in Lightroom.3. Export as JPEG, Metadata: All Metadata, Save to Device.Expected: The edited photo lands in Apple Photos next to the same shoot's photos imported directly from the camera's SD card, at the correct capture time and time zone.Actual:- The capture time inside Lightroom is correct (21:08:11).- The exported JPEG contains the correct DateTimeOriginal (2026:10:23 21:08:11), but with OffsetTimeOriginal -07:00. The XMP create date also carries -07:00.- Apple Photos shows the time zone as GMT-07:00. The SD-card photos from the same shoot show Chicago (-05:00 in October).- Result: Photos displays 9:08 PM but sorts the photo about two hours late, among photos taken around 11 PM.Also observed: with iOS 12-hour time on, the capture date was replaced by the export date. Turning on 24-Hour Time fixed that, which matches other reports in

Regarding the new Archive Photo locally function in Lihgtroom Desktop, I experience that unedited photos are tagged as edited after being moved to the local storage. The Reset Edit function is greyed out/disabled (beacuase there are no edits). If I open the photo in develop, I can verify there are no edits applied. The only workaround I have found, is to reset the develop settings in Lightroom Classic (which is kind of cumbersome and unwanted). Does anyone else experience this, and is it a workaround I haven't thought of? I shoot raw. To my big surprise, I also see that even after applying some edits to the local photo, I am unable to reset the edits if I right click it (it's grey/disabled). Is it a bug?   [Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules.]

hello everybody, im done with my nerves. yesterday i downloaded lightroom again but my problem is or was that it crashed after starting and froze with a error. after many many tries with troublehooting and help from the discord server we didnt came far. After doing the CC adobe software to delete everyhing my lightroom wonnt start now at all... pls help me somebody.

Nach dem letzen Update kann LR keine Dateien (Hasselblad 3F) Dateien mehr öffnen die mit der Phocus App von Hasselblad erstellt wurden. Bis zum letzten Update ging es einwandfrei .

I use the search to find a month of photos eg. July 2026. This is on an iPad running latest software. Sort order doesn’t work on any of the options and no idea what it is sorting on as a default -definitely not capture date. When selecting sort by star rating (or any other option) it will appear to shuffle the photos into a different order, but not by star rating (or the option selected). And I tried to add a filter on stars after just editing a four star photo while already in July 2026 filter -added =4 star -doesn’t find any photos.

Hello,I am experiencing a persistent and reproducible problem when trying to export or convert photos from my Lightroom cloud library, and I would appreciate your help investigating it.Summary of the issueWhen I select a large batch of photos (several hundred to several thousand) and run "Export Originals," the process regularly stalls partway through — sometimes after only a few dozen images, sometimes after several hundred. The progress indicator simply stops advancing, with no error message and no further disk or network activity after a short time.The problem is specific to JPEG-sourced images. RAW files export without any issues, both with and without GPU acceleration enabled. It is not limited to a handful of individual files — it recurs across entire series of JPEGs (in my case, digitized scans from negatives and slides, all processed the same way), which rules out isolated file corruption as the cause.I have also tried "Render to DNG" as a workaround, since DNG output does not

Using Lightroom version 9.5 on Windows 11, when in the Edit view, with multiple RAW files selected from Local storage, selecting from the menu “File::Edit In Photoshop::Open As Layers In Photoshop” throws this error:unexpected error performing command: AgCommand.performCommandID could not perform command: ag.file.editinPsAsLayers (Command was disabled)This only happens in Edit view and only from the menu. I can right click on the selected RAW files in the filmstrip and select “Edit In Photoshop::Open As Layers In Photoshop” and it performs as expected with no error.Other views don’t throw that error; for instance, if I’m in the Photos view to browse photos, the menu item  (from the File menu) works without error. If I’m in the grid view it works without error as well. It only fails when in the Edit view and selecting from the menu “File::Edit In Photoshop::Open As Layers In Photoshop”.I uninstalled Lightroom and reinstalled it. Problem persists.The installed Photoshop version is 27.9.1

Lightroom Version 7.0 Operating System - macOS 14 Sonoma I was excited to learn that LR had the ability to work on local drives. I have used Bridge for the last several years after getting frustrated with Classic's performance. I like what I see in the new LR and am giving it a try. I have run into a problem that I am not able to delete any photos in LR that reside in folders on my Synology NAS drive. After asking if I want to move the photo to the trash I get a response saying "This file cannot be moved to the trash. Please try deleting directly from the disk." I have the gone into my Synology settings and I cannot find anything there that would cause this response. I have no issues deleting photos when in Bridge.  I have administer rights on the NAS drive as well as read/write privileges.  Photos residing on the internal SSD or attached drives delete just fine.  I also can copy files into NAS folders, Move photos from one folder to another on the NAS.  I hav

When creating mask using luminance range, changing range is lagging (choppy performance) with GPU acceleration turned on. On CPU only it’s very smooth.Please see attached video. You can also see CPU and GPU usage on it, and GPU is barely used (which makes sense, it’s just displaying simple 2D image with some colors).Attaching dxdiag file. Drivers are newest, nothing else works in the background, games run crazy fast, the image is medium size JPG, not even heavy RAW.GPU: 4070Ti. 

TitleGhost keywords remain in Lightroom Desktop/Web after removing them from all photosProductAdobe Lightroom (Cloud Desktop)Version9.4.1PlatformmacOSDescriptionAfter removing a keyword from all photos, the keyword remains visible in the keyword list even though it is no longer assigned to any photo.The keyword returns 0 photos when selected, but it is still present in the keyword list. The same ghost keywords are visible in Lightroom Web, so the issue appears to be synchronized through the cloud rather than being caused by a local database.Steps to reproduceSelect an existing keyword. Filter the library by that keyword. Select all matching photos. Remove the keyword from all selected photos in a single operation. Wait until cloud synchronization is complete. Select another keyword or reopen Lightroom.Expected resultIf no photos contain the keyword anymore, the keyword should disappear from the keyword list (or be removable permanently).Actual resultThe keyword remains visible in the k

It is not yet clear whether the data entry issue in the "Masks" section has been fixed, as a new problem has already appeared. It causes even more inconvenience, because it cannot be solved by switching from photo to photo and back.It is impossible to manually enter values in the "Exposure" field. Both on the main panel in general settings and in the "Masks" section. Using the mouse cursor or the up/down arrows on the keyboard, everything works correctly. But doing it manually is impossible. For example, when you need to enter exact values, such as +0.05 and the like. And this wouldn't be a big problem and could be done with the slider using the mouse, BUT there is an important catch. In the "Masks" section, when moving the slider with the mouse, it jumps only and immediately by 4 points, not by 1, as required for fine-tuning. For example, its values can only be 4, 8, 12 (and not 1, 2, 3), and so on. When I want to enter +0.06, an error message appears and the value increases straight

Can any one please help with this fullscreen issue that I am having?DescriptionI have identified what appears to be the cause of a Full Screen UI problem in Lightroom Desktop 9.6 on macOS.When switching between normal windowed mode and Full Screen mode, Lightroom's top toolbar/header changes height.This is the horizontal toolbar running across the top of the Lightroom window. It contains the Photos button/navigation control, Search All Photos, Notifications bell, Share, Help and Cloud status.In Full Screen mode, this toolbar becomes noticeably taller than it is in normal windowed mode.The content below the toolbar does not appear to be correctly repositioned to account for the increased toolbar height.As a result, the top of the photograph is cut off, and the top of the Histogram is also clipped - no try much but it is an annoyance!Steps to reproduceOpen Lightroom Desktop 9.6 on macOS. Open a photograph in the Edit view. Observe the height of the top toolbar in normal windowed mode. Sw

DescriptionUnder Preferences > Cache > Storage location for originals, there are supposed to be the buttons “Reset” and “Browse...” to change the specified path. However, if the current path is too long, these buttons go out of the window. See the screenshots below. This can be worked around by scrolling horizontally to see the buttons, but I highly doubt this is intentional. I’m not even sure it’s possible unless you have something like a Magic Mouse or MX Master. In any case, I thought I had trapped myself permanently with this bug while reproducing it to write this report until I accidentally scrolled sideways. Expected ResultThe buttons to change the storage location are always visible. Actual ResultThe buttons go outside the window where they cannot be seen nor pressed without horizontal scrolling. Steps to ReproduceGo to Preferences > Cache Change the “storage location for originals” to somewhere with a long path (i.e. many characters). ScreenshotsDefault path chosen. “B

Self explanatory. See attached video. 16" M5 Max MacBook Pro 128GB/8TB w/ macOS 27.

Since updating to LR 9.6 (Windows 11 10.0.22631) presets that have been applied with a reduced amount (e.g. 50 instead of 100) will reset to 100 when moving to the next photo or applying further settings to the same photo.Previously, when I applied a preset I could reduce the amount with the slider or by entering the amount. The amount was saved and the preset has been applied with the respective intensity. This could be easily used to adjust the mood of different photos to the same level.Now, when reducing the amount from 100 to e.g. 50 the adjustment only remains temporarily but resets to 100 when other settings are applied or I simply move to the next photo. Even the thumbnail in the list changes instantly back to a intensity amount of 100 of the applied preset.

The top crop border UI is misaligned with the grid. Auto-crop leaves a very small amount of unprocessed pixels in the corners (subtle at fit view, visible at 100%+ zoom). Not happening in 100% of cases, but occurs systematically and is easily reproducible.