Lightroom Classic

Once a photo is loaded from my library, after hitting develop, pictures have color splotches on them that makes editing them impossible. This seems to have started on or about 7/20/26.Original:In Develop mode without starting any editing (note: I have restarted my computer since the issue started): 

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,

·  Title: LrC 15.4.1 UI Issue:  Closing Remove Tool leaves gray panel area; fails to redraw Edit/Basic panels. ·  Product: Adobe Lightroom Classic v15.4.1 Release (Camera Raw 18.4) ·  OS: macOS 25.6.2 ·  Description: In the Develop module, using Solo Mode with the right panel visible, activating and then closing the Remove (spot removal) tool completely breaks the right panel interface. The panels vanish into a blank, dark empty column. Global panel keys (F8, Shift+Tab) and top menu toggles fail to restore it.  Workaround: Clicking the Edit icon (sliders) manually, or toggling Crop (R) or Masking (M) or Red Eye Removal icons on and off forces Lightroom to redraw the UI, successfully bringing the Basic and edit panels back.   Exiting the develop module to the Library module, (G or E) and then re-entering the Develop module (D) will also bring back the Basic and edit panels. ·  Camera model:  N/A ·  Steps to Reproduce:Open Lightroom Classic 15.4.1 in Develop module with Solo Mode active.

Hey,I’m stacking in PS from LRC, saving works fine, flagging, color label works fine. During the same session, these files disappear from LRC. They’re on the disk. I can’t import them, the import module won’t “see” them.

EnvironmentAdobe Lightroom Classic 15.4 Lightroom SDK Windows 11 Standalone reproducer plugin attachedSummaryA floating dialog opened via presentFloatingDialog() does not consistently receive keyboard input.The same floating dialog implementation exhibits two different behaviors depending on the SDK calls executed immediately before the dialog is created.In one case, keyboard input is routed to the floating dialog immediately after opening.In the other case, keyboard input remains with Lightroom, allowing Lightroom keyboard shortcuts to continue working while the floating dialog is visible.A complete standalone reproducer plugin is attached. Steps to ReproduceInstall the attached reproducer plugin via File > Plug-in Manager > Add. Run via File > Plug-in Extras > Floating Dialog Keyboard Input Reproduction. Choose one of the two test configurations: Plugin dialog receives keyboard input Lightroom receives keyboard input Press the Tab key.A complete standalone reproducer pl

라이트룸에서 생성형 업스케일를 사용하면 파일은 어디에 있나요! 내보내기를 해도 해상도가 업스케일 하기전의 해상도입니다.  여러번 업스케일을 시도해도 크레딧만 소모하고 이미지해상도가 그대로입니다. 

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

When I try to start lightroom classic I get the error message ?:0: attempt to index field'_nglController'  I cannot get it to start in any other way. Greg Hoglund 

Product: Adobe Lightroom ClassicUI language: Polish (Polski) — issue also affects English source copyOS: Windows 11Lightroom version:[paste from Help → System Info → Copy]Steps to reproduce:1. Library → select any photo → File → Export (Ctrl+Shift+E)2. File Settings → Image Format: JPEG3. Enable “Limit File Size To” → set to 5000 K4. Click ExportActual result:A dialog appears. In Polish UI the title is “Aktualizacja limitu rozmiaru pliku” and the message reads:“Jeśli obraz nie może osiągnąć limitu, zostanie on eksportowany do minimalnego możliwego rozmiaru pliku.”The English source text (approximate) is:“If the image cannot reach the limit, it will be exported to the minimum possible file size.”Problem:Both wordings are misleading. “Minimum possible file size” strongly suggests Lightroom will crush JPEG quality to the smallest file (e.g. tens of KB). That is alarming and contradicts what users expect from a paid subscription.What the message should describe is the opposite scenario: wh

Lightroom Classic version: 15.3.1Operating System: macOS 26.5.1Computer: MacBook Pro M1 Max, 64 GB RAMCameras affected: Canon R5 Mark II Canon R6 Mark II Description:AI Denoise suddenly stopped working during an editing session. It had been working earlier the same day and then began failing on every RAW file.The issue affects RAW files from both Canon cameras and occurs across different folders and catalogs.When I select Photo → Enhance → Denoise → Enhance, Lightroom either displays:"An unexpected error occurred while processing."or no Enhanced DNG is created.Troubleshooting already completed: Restarted Mac. Reinstalled Lightroom Classic. Cleared Camera Raw cache. Verified over 600 GB of free disk space. Tested multiple RAW files from different folders. Tested files from two different cameras. Catalog and RAW files are on an external drive. Lightroom edits, exports, and all other functions work normally. AI Denoise is the only feature that consistently fails. This ap

Description of Issue:Merge to HDR stalls (application unresponsive, beachball) when merging exposure-bracketed images on 15.4.1. Another user in an original 15.3 thread reported this resolved after updating to macOS Tahoe 26.5. I am on macOS Tahoe 26.5.2, a newer build, with a fresh OS install, fresh Creative Cloud install, and a brand-new catalog, and the stall still occurs on 15.4.1. This rules out the macOS-update fix reported by others for the 15.3 version of this issue.Lightroom Classic Version Number: 15.4.1 (Help > System Info)OS Version Number: macOS Tahoe 26.5.2Camera Model: Sony a7r V & DJI Mavic 4 ProComputer Version: Mac Studio M3 UltraStep-by-step Reproduction Instructions:Fresh macOS install, fresh CC/LrC install, no plugins, brand-new catalog. Select a set of exposure-bracketed RAW images. Photo > Photo Merge > HDR (or Ctrl+H or Ctrl+Shift+H). Merge stalls partway through; have to quit to reset the merge process.Expected Result: HDR Merge completes and produ

I moved a folder from one hard drive to another and Lightroom is throwing me in a loop. I’m at a loss, I don’t know what to do here! This makes zero sense I’m going in circles.   

As the title says the folder where my Lightroom catalog is stored only shows the folder 0 to 9 and A to F. In these folders there are seperate folders (like 0A2A). Is there a way I can rebuild/restore my catalog?  It is not showing any .lrcat / .lrdata files.

I am currently on LRC 14.4 and CR 17.4.  I have learned to work with the changes in the Denoise that got rid of the middleman DAT file and keeps the file naming of the original file.  I have learned to batch edit with pasting dev settings including denoise.  It has been ok. But now Adobe doesn't like that I'm running so far behind.    After having this version stable for several months, I am hesitant to upgrade.   Can anyone who has upgraded to the latest version give me any advice?  I only have a 1T harddrive, that I try to clean out by moving files to external SSDs as much as possible.  I am honestly scared to upgrade after seeing so many performance issues, etc from other posts.  I have 13th gen Intel(R), 32 DB RAM, and 8G Nvidia GeForce RTX 4060 Laptop GPU - ASUS TUF Gaming laptop Thoughts?  I can’t really afford a new laptop, so I am hoping to not have to do that again.  Right now, with 14.4, a single denoise takes about 4-8 seconds.

I use DJI drones, and their RAW format is DNG. Lightroom Classic is quite happy to accept these and successfully does an HDR merge on them. The output is once more DNG (or allegedly is).I use Topaz Photo to pre-process my images before doing most of my processing on Lightroom Classic. Topaz quite happily accepts DNG files straight from the drone. However, if I pass it a DNG that HDR Merge has generated, Topaz rejects the image as being an unsupported format.So it looks as if LRC is generating DNG files that do not quite meet Adobe’s own DNG specification in some way that neither Topaz or I understand.I use Windows 11 and the very latest LRC.  

Problem: LrC 15.4.1 - Receive “Lightroom has encountered an issue updating AI edits” & “unable to backup catalog error” after migrating catalog from Windows 10 to Windows 11.  =============== Background: Problems started when I moved LrC catalog/workflow from a windows 10 machine to a windows 11 machine. Backed up entire C drive from W10 PC to external hard drive (included the then-used LrC catalog). Signed out of all adobe apps on old machine before doing a “fresh”/”clean” install of Windows 11 to C drive. Kept all jpg/raw originals on F Drive, which on second catalog import attempt, had no issues on Windows 11.  Migration Attempt 1 (Failed, Abandoned): After Windows 11 install, and LrC install, tried to open old catalog from Windows 10 and could not get it to boot properly. Tried to copy the Catalog from old Windows 10 C drive (external) to new Windows 11 C drive (internal) --- Alt+Open LrC and selecting the copied old catalog led to: missing files, missing edit info, and AI Edit

When I start Denoise, instead of pop-u showing the progress the entire right side panel is grade out and a test says : An AI process is running on the photo. Editing is temporarily disabled.” Ok, There is a problem: A popup is the standard established way of visually indicate a process i progress. The ways this new bizarre way indicates the process is confusing. Sometimes the images flickers, making an optical indication I am Done , I click on something, but there is no response to anything because the process is in progress. Please stop the foolishness.  An example, a 45min running “dead process” on a 24 Mpix file: Even a sniping tool of Windows often hangs when Lightroom runs. The top apre aof the image shows a black background panel, which than disappears. and we cannot even make screens hot, because the entire windows hangs than hopelessly.  An example:Forever hanging, never finishing. A 20Mpix, small by present times. 

Lightroom Classic’s secondary display selection keeps switching from my preferred monitor to another connected monitor. This interrupts my editing workflow and forces me to manually reconfigure the setting.I use a three-monitor setup. Lightroom Classic runs on my left monitor, which is Windows display #1. My preferred secondary display is Windows display #2, the middle monitor. I use that screen to review crop changes and overall edits while working in the Develop module on monitor #1. However, Lightroom Classic randomly changes the secondary display to Windows display #3, and I have to go back into Preferences and set it again.This has been happening for years, and it occurs multiple times within an hour of editing. The repeated reconfiguration breaks my focus, and my current workaround is insufficient. I’m asking Adobe to confirm whether this is reproducible on their side.Steps to reproduce Open Lightroom Classic. Use a three-monitor setup. Set the secondary display to Windows di

When I paste settings threw Auto Sync. The AI processing will start. After while if it is multiple pictures like 30+ it will get stuck on Information "AI processing is in progress for this photo. Editing is temporarily unavailable." Even though the progress has already ended. So no proces is running. Obviously the photo can not be edited so I need to restart lightroom. Can you add some function to stop the proces on the photo itself? Otherwise I can not do anything with it. 

MEU LIGHTROOM NÃO CONSEGUE MAIS ACESSAR SUAS INFORMAÇÕES EM NUVEM, VOU FAZER O UPLAOD DELAS DEPOIS DA EDIÇÃO E ELAS NÃO BAIXAM NO TAMANHO SOLICITADO POR ESTE ERRO

SummaryLightroom Classic’s built-in catalog backup takes approximately 14–16 minutes to create a 39.1 GiB ZIP containing 39.7 GiB of nearly incompressible .lrcat-data.I tested the same catalog with two local internal storage destinations: WD_BLACK SN850 1TB, PCIe 4.0 NVMe NAND SSD Intel Optane SSD 900P 280GB, PCIe 3.0 NVMe 3D XPoint Changing the destination from the SN850 to the Optane 900P reduced the duration by only 105 seconds, or 11.24%. The completed ZIP remained approximately 39.1 GiB.The main issue is that almost the entire backup consists of .lrcat-data that provides very little compression benefit.Actual resultsWD_BLACK SN850 destination Source catalog: D:\Lightroom\Lightroom Catalog.lrcat Backup destination: same physical WD_BLACK SN850 Completed ZIP: 39.112012 GiB Backup folder creation to ZIP last write: 15 minutes 34 seconds Intel Optane 900P destination Source catalog: same catalog on the WD_BLACK SN850 Backup destination: separate Intel Optane SSD 900P Compl