Windows 10: Lightroom Classic CC 7.2 Display Bug and workaround

The latest release of Adobe Lightroom CC 7.2 (Released a few days ago), contains an issue with rendering previews of large files.

The file renders at the "Fit" ( resolution but when you select a zoomed view especially 1:1 the image partly shows whilst showing loading but then disappears and will not appear at any any resolution other than Fit

Due to differences in the way that the Graphics processor is (or isn't) used the previews work fine in the Develop module and when edited in Photoshop.

Adobe is aware of this issue and is working on it but in the interim switching off the "Use Graphics Processor" and restarting Lightroom when this issue is seen is a workaround, until Adobe release a fix

This issue only affects some larger size files so is not a worry for most users, but of course with the current switch to UHD (4K) images the normal file size is growing

The file That triggered the issue for me was a DNG Panorama of 17748 x 3080 Pixels 246.36 MB but another similar file of 11390 x 6652 Pixel 227.94 MB displayed fine at all resolutions

:)

 

How to edit a default app list

Another link on Adobe being a default is using the registry.

Below is a link

I cannot associate files with Adobe Photoshop CC | Adobe Community

They talk about photoshop, however, it can be done the same way with Lightroom CC.

Just make sure when naming the default app in the registry that the .exe is “Lightroom classic CC” instead of the “Lightroom CC”

 

How to edit a default app list

Gail,

Sorry that these steps are not working.

However, after researching on Adobe’a page, I’ve found out Lightroom CC and Lightroom Classic CC are Data Base Applications. Which means can’t be set as Default Apps.

Below is a link to a similar question you’ve had, and a possible fix from Adobe.

Lightroom as Default Photo Viewer | Adobe Community

Once again, I hope this helps.

 

Go back to version 7.1 if it bothers you until Adobe fix the problem.

 

It does not bother me, I'm just letting others know how to solve the issue if they see it *092