Copy link to clipboard
Copied
Hello,
I'm experiencing a frustrating issue: the Denoise window won't open after the "Loading Enhance Data" screen. After that, the loading screen doesn't appear again when I try to relaunch Denoise, unless I restart Lightroom.
I've tried adjusting the GPU settings and optimizing the catalog, but nothing has worked so far.
I'm using Windows 11 with an i7 6850k, a GeForce GTX 1080, and 16GB of RAM.
Thank you very much for your help!
Copy link to clipboard
Copied
Just updated to LC14, was working before the update on the same .dng files - not anymore!
Copy link to clipboard
Copied
I have experienced exactly the same issue with the latest LC update on a similar platform.
The "Loading Enhance Data" loading progress window appears but then nothing... the preview window fails to appear. I thought there might be something wrong with the .dng file as denoise / enhance worked with another file from the same camera (Pixel 7). So also tried exporting the .dng file as a .dng file to another location but this failed also with the progress bar not moving - effectively hanging.
What has worked is starting Bridge and opening the file with Camera Raw. The denoise option is available and the preview dialog loads as expected including generation of a new, enhanced .dng file - as was previously the case in the last version of Lightroom
Copy link to clipboard
Copied
I do not see this problem using LrC 14.0 on Windows 10.
Have you tried to reset your preference file?
This procedure works for both Lightroom Classic and Lightroom Desktop.
If you are using Lightroom Desktop, it can change your local storage location. Please review this setting after resetting preferences.
Reset Procedure:
1. Close Lightroom.
2. Hold down [Alt/Opt]+[Shift] while restarting Lightroom.
3. Overwrite the Preferences when prompted by the dialog.
4. Close Lightroom.
5. Restart Lightroom.
Copy link to clipboard
Copied
Thanks for your feedback and the reset procedure.
The problem was in Windows 11 which was the case for the first poster.
The issue resolved itself a day after my earlier post and following a LrC update to 14.0.1 so perhaps the update reset conditions?