Skip to main content
Inspiring
June 21, 2025
Question

V. 14.4 Denoise doesn't work (error)

  • June 21, 2025
  • 5 replies
  • 3351 views

- LrC Version 14.4 (build 202506051112-5918896a)
- Windows 11 Pro and OS version 23H2 on Intel Core i7-9750H
- Select new Denoise (or Raw Details) from Detail develop panel
- Expected result: denoised picture with access to slider and other options
- Actual result: error message "An internal message has occured: ?:0: attempt to index a nil value"

After clicking on OK the image seems fairly denoised, but the Detail panel options are unavailable with exclamation symbols on the right side. After restarting LrC, this denoise has been dropped. I tried this with all 10+ tested photos, taken with Canon R5MkII .CR3, 90D .CR3 & 70D .CR2, everytime with the same result. Optimizing the catalog didn't change the result. Using (PS 26.8 and) CR 17.4, the feature does work as expected. I include LrC System Info and screenshots.

 

5 replies

tonyhartphoto
Participating Frequently
July 8, 2025

Are we any closer to a proper fix for this issue? My gut instinct is this is some sort of corrupted catalog issue that Lightroom is not catching. I feel like a future update needs to address this and repair whatever is wrong with the catalog.

Moving all of my images to a new catalog isn't really practical. I appreciate that for those who use a multitude of smaller catalogs, creating a new catalog and importing files from the old catalog may be a reasonable workaround in the short term, but for those of us who use a single large catalog it is not realistic. 

Would appreciate if any Lightroom devs could chime in and offer an update. This is impacting my workflow significantly. For my last wedding edit I rolled back to the previous version, but this then caused all sorts of weirdness with AI remove work being forgotten - even after recalculating it kept forgetting and presenting the image as it was 'before removes' had been made.

tonyhartphoto
Participating Frequently
June 26, 2025

I have also been encountering this issue and was advised to post here by a helpful Adobe employee over on reddit. I am not willing to try moving my entire main catalog to a new, clean catalog (my main catalog is close to half a million images*) but I will make a test catalog with a few images and see if I still encounter the error. 

For reference I am running Mac OS 15.5 on a Mac Studio M1 Ultra (64GB RAM). My Lightroom Catalog file lives on my internal SSD and my working edits are on an external SSD. 

*I've been running Lightroom since the original version and have always used a single large catalog. It is one of the main reasons I use Lr so please don't advise me that a single large catalog is a bad idea! 

tonyhartphoto
Participating Frequently
June 26, 2025

I have tried making a test catalog with a small number of images and the problem doesn't present under those conditions. 

I am loathe to try moving my entire catalog over over 400k images to a new catalog though. Even with backups it feels very risky.

On updating to 14.4 I didn't get any notification about a catalog upgrade. Should I have? In the past I remember certain dialog boxes advising that a new version of Lr would involve upgrading the catalog. I didn't see that happen this time. 

Ian Lyons
Community Expert
Community Expert
June 26, 2025

Catalog upgrades only occur when moving from say LrC 12 to 13 or 13 to 14. The upgrade doesn't happen with dot releases (e.g. 14.1, 14.2, 14.3, 14.4, etc)

Per Berntsen
Community Expert
Community Expert
June 21, 2025

As suggested by @Ian Lyons , you need to update the GPU driver. A two-year-old driver is bound to create issues with the current version of LrC. Make sure to install the Studio driver, not the Game ready driver.

 

Your system info also indicates that you have an integrated GPU that seems to be active.

 

Adapter #2: Vendor : 8086
	Device : 3e9b
	Subsystem : 140a1025
	Revision : 0
	Video Memory : 80

 

An Internet search for  Vendor : 8086 Device : 3e9b identifies this as a UHD Graphics 630.

Adobe software does not work well with dual GPUs, so go to Control panel > Device manager >  Display adapters, right click the UHD Graphics 630 and choose Disable device.

 

Inspiring
June 22, 2025

Thank you both for your response.

I tried all of the following steps and checked the result after each step (incl. LrC and/or W11) restart):

- I used the NVIDIA app to update to the latest Studio Driver (32.0.15.7680). 

- While the Geforce was already manually selected (Customized), I disabled the Intel UHD Graphics 630 device.

- I made sure Windows Update was up-to-date: even optional updates were processed.

- Using PC HelpSoft Updater, I made sure all drivers were backupped and updated to the latest versions.

- Back in LrC, I checked the Excire Search version and temporarilly disabled it.

 None of these steps changed the situation in any way: the error is still the same. What can I do next?

Uninstall and reinstall Lightroom Classic? Can I downgrade to the previous version?

 
Per Berntsen
Community Expert
Community Expert
June 23, 2025

I forgot to address the "?:0: attempt to index a nil value " error message.

Take a look at this thread: https://community.adobe.com/t5/lightroom-classic-discussions/0-attempt-to-index-a-nil-value/m-p/12882163

It appears that there is no single fix for this that will work in all situations.

See the Word document posted by @Rob_Cullen in the thread.

The original poster fixed the issue by creating a new, empty catalog, and then importing from the original catalog.

Ian Lyons
Community Expert
Community Expert
June 21, 2025

Your System Info has a linee 

NVIDIA GeForce RTX 2060 (31.0.15.2849)

 

 

NVIDIA GeForce RTX 2060 (31.0.15.2849)

 

This version of the driver dates from April 2023. Best that your update to the most recent veersion. You should be able to download it from https://www.nvidia.com/en-us/drivers/