Lightroom Classic

SummaryOn a current-generation Intel Core Ultra laptop with Arc 140T integrated graphics, AI Denoise in Lightroom Classic 15.4.1 never completes. The GPU computes continuously at ~100% without ever finishing, the progress indicator never advances, and the photo remains locked ("AI processing is in progress for this photo. Editing is temporarily unavailable."). This is a regression: the same machine completed the same operation in 1–2 minutes on the LrC version current ~2 months ago. I originally raised this as a community question and was advised to file it as a formal bug report - this report consolidates all findings and test results from that thread: https://community.adobe.com/bug-reports-674/regression-ai-denoise-never-completes-on-intel-arc-140t-core-ultra-gpu-at-100-compute-progress-stuck-worked-in-1-2-min-on-earlier-lrc-versions-lrc-15-4-1-intel-32-0-101-8860-1635896EnvironmentLightroom Classic 15.4.1 [202606201310-b9f148a4], Camera Raw 18.4 Windows 11 Home, build 26200 Intel C

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.

On my laptop, when I highlight a folder>press file>export as catalog I get the dialog box but I cannot choose where I want it to be exported. After a bit lightroom says it must close and offers to report the issue. This function worked a week ago and works on my desktop. Please help I need this function.Bill

I am on Windows 11 Pro and I have the latest Creative Cloud with PS and LR Classic, Nvidia 2060S with the latest drivers. This error started appearing a couple of months ago. I start Lightroom, never mind if I open the catalogue or click the icon, and it takes 20 minutes to pop up. Task Manager shows it’s running, but it takes 20 minutes to show up.

In wake of a power outage, when I reopened LrC, ALL of my images had been moved to a new location. Some of which remained intact as thumbnails and others completely missing. Is there any way to revive the current catalog? If so, how? Matthew 

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

In 15.4.1 I have found that in Lens Blur the Blur option of Brush Refinement seems broken.  Using it does the same as the Focus option.  Anyone else noticed this?I am running the Mac version.

I’ve noticed the crop tool is sticky again. Lightroom Classic version: 15.5 [ 202607291506-b8869fa7 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 24Processor speed: 3.4GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.213CPU Utilisation: 1.0%Power Source: Plugged InBuilt-in memory: 65292.0 MBDedicated GPU memory used by Lightroom: 11351.4MB / 15995.0MB (70%)Real memory available to Lightroom: 65292.0 MBReal memory used by Lightroom: 12382.0 MB (18.9%)Virtual memory used by Lightroom: 24292.0 MBGDI objects count: 1276USER objects count: 4660Process handles count: 19316Memory cache size: 0.0MBInternal Camera Raw version: 18.5 [ 2673 ]Maximum thread count used by Camera Raw: 5Camera Raw SIMD optimization: SSE2,AVX,AVX2Camera Raw virtual memory: 1660MB / 32646MB (5%)Camera Raw real memory: 1926MB / 65292MB (2%)Cache1: NT- RAM:0.0MB, VRAM:0.0MB,

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

--- 2nd try to get it fixed ---Hint: Of course this wrong map-behavior works with other cities / locations, too.Select (e. g.) 'New York' library folder. Map Module: Open it and make photo GPS allocation tasks in New York.  Go back to the Library Module. Close LrC. Open LrC. Select some library folder different to the before used New York folder, e.g. Washington. In library folder Washington, GPS data already present: Click on a photo GPS coordinate icon. The Map Module opens. Expected Map Module behavior: The photo location in Washington is shown. Actual Map Module behavior: The New York map is shown.Lightroom Classic version: 15.5 [ 202607291506-b8869fa7 ]License: Creative CloudLanguage setting: enOperating system: Windows 11 - Home Premium EditionVersion: 11.0.26200Application architecture: x64System architecture: x64Logical processor count: 8Processor speed: 2,3GHzSqLite Version: 3.36.0Adobe GSDK Version: 1.4.0.213On a other PC with Windows 11 - Pro 25H2 it shows the same issue. Th

Sinds de laatste update van Adobe LrC 16.5 worden de foto's enkel uit de catalogus verwijderd. Ik krijg wel het scherm efkens te zien waar ik de keuze kan maken, maar dit verdwijnt onmiddellijk en de foto verdwijnt in LRC catalog maar blijft wel op de schijf staanWaar kan ik een aanpassing doen om dat schermpje langer in beeld te hebben om een ​​keuze te kunnen maken

Since going to the 15.5 release, the Masking tools are not working correctly.  As with the attached screenshot, though there is clearly a subject, the Subject mask cannot find it.  I tried with several other photos and got the same results (on equally obvious subjects).

After updating LRC v 15.5, I am unable to control or change camera settings on my camera when shooting tethered. The camera will not allow me to change apertures, shutter speed, ISO, focus points etc.When i disconnect tethering, it works fine.I am using Canon R5, Macbook Pro, Sequoia 15.7.1

since updating to 15.3, I’m finding that Lightroom Classic is quickly hitting a memory leak and freezing or crashing.  I’m processing RAW Canon CR-3 files, often adding AI object removal, and synchronising my edits across groups of photos (including masks, AI object removals & colour grading).  I find that I can only run for approximately 30 - 60 minutes before I start to encounter memory issues and either the app pauses (and doesn’t come back to life) or crashes altogether.  I keep getting error messages telling me that my system has run out of memoryThis has only been a problem since updating to LrC 15.3 a few days ago.system tech specs: MacBook Pro (16-inch, 2021)Apple M1 Max64gb ramMac OSX 26.4.1  

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!  

When opening LRC, I enter Library, select the folder where my photos are and click assisted cull from the bar at the top. It starts the cull, and less than a minute into the process it crashes LRC. I have tried to import and then cull, same thing happens. I have reset all preferences, it changes nothing. I have uninstalled and re-installed LRC, no difference. For this to happen in the middle of the busy season is unforgiveable. Adobe should be working around the clock to fix this issue, but I’m seeing nothing, not even a message to say they are working on it. Fuming doesn't cover how I'm feeling right now.

Any mask that I create in LRC the selection turns to B&W.  The only way I can revert back to color is to undo the mask.  if I leave the Mask Edit menu and go to Basic Edit menu, the selected objects are still B&W and all the sliders work as expected on the B&W object, i.e. if I change the Exposure slider the B&W object change brightness just as the rest of the image. This happens with both .nef & .dng files. Ken Anderson (aka keniliamna) 

Hardware:Mac Mini M4 Pro with 24 GB RAM and 16 GPU cores. The same issue also occurs on an M1 Pro. Lightroom Classic 15.2 macOS Tahoe 26.3 RAW ARW files from Sony A1, A9ii and A9i as well as compressed DNG converted files behave similarly. GPU acceleration is enabled in Preferences > PerformanceObserved behavior with AI Denoise Lightroom Classic Denoising a single image via the Detail panel is very fast: 5–7 seconds. When batch-processing even just 2 images, the first image processes quickly (normal speed), but the second image takes 38–40 seconds — about 5× slower. In larger batches (e.g., 100 images), the first image remains fast, but all subsequent images (the remaining 99) are consistently slow. Creating a preset that applies only Denoise and applying it to a single image results in the slow processing time (~40 seconds). Denoising one image quickly, then syncing that setting to another image, is also very slow.Workaround comparison: Manually scrolling through thumbnails and cli