Lightroom Classic

Depuis la mise à jour Lightroom Classic 15 et la conversion obligatoire de mon ancien catalogue, Lightroom Classic affiche en permanence « Synchronisation de 123 043 photos ». Le compteur ne change pas, même après plusieurs heures.Le catalogue contient 168 764 photos, dont 67 198 sont indiquées comme synchronisées. La synchronisation a parfois une activité CPU/disque/réseau, puis retombe à zéro sans progression visible.J’ai déjà : réparé Creative Cloud Desktop en recréant OPM.db, puis suspendu la synchronisation, quitté Lightroom Classic, sauvegardé le catalogue et renommé le dossier Lcc transfert 24.10.25 Sync.lrdata afin qu’il soit reconstruit.Mes originaux sont sur un disque externe G:, avec une sauvegarde E:. Je ne veux pas supprimer/recréer le catalogue, ni risquer les photos ou les collections synchronisées. Merci de vérifier côté serveur l’état de la file Lightroom Cloud et de m’indiquer la procédure de diagnostic ou de réinitialisation serveur appropriée.

In library, I hit R to open crop tool in Develop. But this opens crop overlay, with the Zoom tool, not the crop tool. Hitting R again (closes crop ), then R again, will open crop overlay with the crop tool.The in the Right-hand panel the Crop section is greyed out too.

 Hi everyone,First, ChatGPT helped writing this post since i have been talking with it about this question yesterday the whole day. now the question below:I'm having a really weird problem with Lightroom Classic and I'm running out of things to try.When I switch Lightroom Classic to Chinese, most of the UI becomes garbled/unreadable. The really strange part is that the top menu bar displays Chinese normally, while most of the rest of the Lightroom interface is messed up.Even stranger: Photoshop on the same PC displays Chinese perfectly.So I'm starting to think this might be something specific to Lightroom's UI/text rendering rather than a general Windows Chinese-font problem.SystemWindows 11 Build: 10.0.26200.8875 Lightroom Classic 15.5 Windows display language: English (United States) Display scaling: 150% Lightroom scaling: Auto Chinese fonts: Microsoft YaHei installedThings I've already triedI've gone pretty far down the troubleshooting rabbit hole:Uninstalled and reinstalled Lightr

AI Denoise consistently fails to complete on my machine. This is 100% reproducible and has persisted across multiple Lightroom Classic and Intel driver versions, including the current pairing of both.System:Lightroom Classic 15.4.1 [202606201310-b9f148a4], Camera Raw 18.4 Windows 11 Home 26200 Intel Core Ultra laptop, 16 logical cores, 32 GB RAM Intel Arc 140T integrated GPU (16 GB shared), driver 32.0.101.8860 WHQL (current, verified in Device Manager) Files: Fujifilm RAF (X-Trans)Symptom:Click Denoise. The background progress indicator (top-left) immediately shows roughly 10% progress, then never advances — waited well over an hour. The photo becomes locked: "AI processing is in progress for this photo. Editing is temporarily unavailable." Task Manager shows the Arc 140T near 100% compute utilisation for the entire time, so the GPU is actively executing something — it just never finishes. Exiting Lightroom during this state leaves orphaned Lightroom processes that must be killed in T

Summary:The Map module fails to render any map content. On launch, the world map appears very briefly, then the entire module goes grey and stays grey indefinitely. No persistent error is shown, though a fugitive message reading "Unable to connect to Adobe servers. The Map module is not working." occasionally flashes on screen for a fraction of a second before disappearing. This matches other open reports of the same bug (e.g. the "(Europe) Map Module not showing a Map" thread, open since LR 14.2 in early 2025 and still unresolved as of 15.5).Environment:Lightroom Classic version: 15.5 [202607291506-b8869fa7] OS: Windows 11 Home, version 11.0.26200 GPU: NVIDIA GeForce RTX 4070 Ti SUPER (driver 32.0.16.1088) GPU acceleration: Off (User Preference: Off, GPUDeviceEnabled: false) Displays: two monitors, both 3840×2160, system running at 200% (192 DPI) scaling Language: EnglishSteps to reproduce:Open Lightroom Classic with a catalog containing photos that have GPS coordinates embedded in th

Hi everyone. I am posting in this forum as Lightroom is what I’ve used, and I cannot find a support email address to ask Adobe directly.I subscribe to a 1TB/month cloud storage, as well as to the Creative Cloud monthly applications package. I am cancelling both services as I haven’t used them much in years. However, there are warnings upon cancelling that photos may be lost if I cancel. I’d like to not lose any of my photos, as I may want to pick my editing back up at a later time. Does anyone know the following:If I cancel my services, if I re-subscribe later, will all my photos be there again in my photo library, or would I be starting from scratch with an empty library and need to re-import everything? If the photos would still be there - will any edits I’ve made still show up, or no? Also… my mind boggles with the locations of all of my photos - when I first started they all lived on hard drives nicely organized, but once services started switching to cloud I became very confused w

Opened Lightroom Classic 15.5.  Upgraded Library version as requested.  I imported some photos into Lightroom Classic.  After a while, looking through the collection, it automatically closed down.  I had this happen several times.  I ran log collection and uploaded the logs.The log reference is Adobelogs_20260811_075703_590-win-GS.zxp.I could not find a way to log in directly to support on this issue.My system setup CPU: AMD Ryzen 5 5600X 6-Core Processor (3.70 GHz)RAM: 64 GB DDR4GPU: NVIDIA GeForce RTX 3050 (6 GB)System type: 64-bit, x64-based processorOS:  Windows 11 Home Version 25H2  Build 26200.8875 I would like to know how to solve this issue.

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

I used to edit photos in the FIT option. and Zoom when I required to edit a specific area. I was not an issue till now. But happened to be like shifting the color/exposure when I trying to zoom. This affects the final export as well I am seeing different output that I see in the fit  options. I tried by changing the GPU off and On but resulting same. 

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 the June 2026 update I have been plagued with giant squares developing on the sky portions of my photos when applying the denoise feature. I primarily edit on my mac that is operating macOS Tahoe  and understand that this has been a reported issue but I’ve gone as far as buying a new camera to find a solution for this since it does not seem to be a priority to be fixed and I can not find a way to fix this on my end. I shoot with Canon products and edit with canon raw images and this problem has been super frustrating. This is an issue on both lightroom platforms too.

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.

LRC: 13.5.1Windows 11Lightroom has been really slow for me, and I was sure that facial recognition was turned off, but today I was scanning some photos that had group pictures, and LRC is still recognizing faces when I’ve explicitly turned it off. Note that it was turned off before this screen capture and has been turned off as long as I can remember, but LRC is clearly still doing it. How can I stop this? I don’t want LRC to recognize faces. I don’t want it, don’t need it, and it’s taking computer resources and slowing down my work. Thanks  NB: I am not upgrading to the newest version because it is incompatible with my Fuji GFX100 due to LRC’s native tethering causing issues. Thanks

Hi all.  I'm SUPER frustrated right now, and feel like I've been chasing my tail.  And I think that there just isn't a solution for my problem, that it is a bug in the software, but I'm really hoping that is not the case.So, when I export my RAW files as jpegs, my noise reduction settings are completely ignored, and the images turn out extremely grainy with a lot of noise.Just to clarify... I understand high ISO, I am NOT applying any sharpening or sharpening output settings, and my images look great (with NR) in both the library and develop modules.It is only when I EXPORT that they become a grainy mess.So, after spending hours researching what could be wrong, I discovered that if I export the image with ANY kind of resizing, the NR DOES apply.  It is only if I try to export it in its original size that it the NR settings are not applied.Trouble is, I really want to export all my images in their ORIGINAL size.  I do not want to make them smaller in any way, as I am

Description of Issue:Lightroom Classic freezes the photo preview after using AI Denoise combined with Sync across a batch of high-ISO photos. Once the bug triggers, no slider adjustment updates the preview anymore - only the histogram reflects changes, not the actual image.Lightroom Classic Version Number:15.5OS Version Number:macOS 26.5.2Camera Model:Sony A1 II / A7R V / A7S IIIStep-by-step Reproduction Instructions:Import a batch of high-ISO photos, some already partially edited. Select one photo and apply AI Denoise at approximately 30%. Select all high-ISO photos in the batch and Sync settings from the denoised photo. Navigate to the first photo in the batch (one that had edits applied prior to the denoise sync). Attempt to change any slider on that photo.The Expected Result:The photo preview updates in real time to reflect the new slider values, as in any normal edit.The Actual Result:The photo preview is frozen and does not update regardless of slider changes. The histogram does

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

SummaryImporting photos in Add mode (files already local on a fast NVMe volume, no copy/convert) is extremely slow. CPU utilization spikes for 1–2 seconds, then the application goes idle for 5–10+ seconds, repeating in a cycle. During the idle gaps the Lightroom window intermittently reports Not Responding. Per-second process tracing shows the import pipeline is running with a median of 2 active threads while the rest of the machine is idle. All external causes (storage, antivirus, network, background analysis features) have been measured and excluded — details below.Environment Item Value Lightroom Classic 15.5 [ 202607291506-b8869fa7 ], Camera Raw 18.5 [ 2673 ] OS Windows 11 Enterprise, build 11.0.26200 CPU AMD Ryzen Threadripper PRO 9975WX — 32 cores / 64 logical processors RAM 256 GB (Lightroom reports 261,500 MB available) GPU NVIDIA GeForce RTX (32 GB VRAM), driver current Storage

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.

I can't open any of my LRC catalogs.  I get message "AI storage error."  Tried to find the Data storage file.  Supposed to find it in "Help>system info>library.  Window shown after these steps shows no "library."No problem opening catalogs when I move my master HD to my laptop. Laptop is running LRC 15.4. Mac Mini is running Tahoe 26.3.1 Desktop is running LRC 15.5 release.  Should I re-download software on desktop mini?