Skip to main content
J
jtaylor333
Inspiring
March 27, 2025
Answered

LrC 14.2 doesn't process warning messages correctly

  • March 27, 2025
  • 2 replies
  • 256 views

In LrC 14.2, if you try and open a catalog that is in a folder that it doesn't have permissions for, it reports the catalog as corrupt, which it is not.  Occurs starting LrC by double clicking a catalog or by opening LrC and using Open Catalog.

Correct answer jtaylor333

It got into the wrong folder because I put it there (in the default users heirarchy - don't know what I was thinking of)

2 replies

GoldingD
GoldingD
Legend
March 27, 2025

Please post your System Information as Lightroom Classic (LrC) reports it. In LrC click on Help, then System Info, then Copy. Paste that information into a reply. Please present all information from first line down to and including Plug-in Info. Info after Plug-in info can be cut out as that is just so much dead space to us non-Techs and it takes up vast amounts of scroll space making the reply less readable and less likely that others will bother with your post. Also large amounts of text in a post also render the Translate function inoperable.

 

largely interested in library path

J
jtaylor333Author
Inspiring
March 27, 2025

Here's the info.  Everything seems to work fine, with the exception of startup.  I get the splash screen, then I see one of my images, then it goes away to do something for about 20 seconds.  Then all is well.

 

Lightroom Classic version: 14.2 [ 202502071718-3869eef7 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 11 - Business Edition
Version: 11.0.26100
Application architecture: x64
System architecture: x64
Logical processor count: 24
Processor speed: 3.6GHz
SqLite Version: 3.36.0
CPU Utilisation: 1.0%
Power Source: Plugged In
Built-in memory: 64791.7 MB
Dedicated GPU memory used by Lightroom: 871.2MB / 15889.0MB (5%)
Real memory available to Lightroom: 64791.7 MB
Real memory used by Lightroom: 2648.9 MB (4.0%)
Virtual memory used by Lightroom: 3872.8 MB
GDI objects count: 1004
USER objects count: 4164
Process handles count: 3529
Memory cache size: 684.4MB
Internal Camera Raw version: 17.2 [ 2155 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 192MB / 32395MB (0%)
Camera Raw real memory: 197MB / 64791MB (0%)
 
Cache1: 
NT- RAM:0.0MB, VRAM:0.0MB, Combined:0.0MB
 
Cache2: 
m:684.4MB, n:0.0MB
 
U-main: 129.0MB
 
System DPI setting: 144 DPI (high DPI mode)
Desktop composition enabled: Yes
Standard Preview Size: 3840 pixels
Displays: 1) 3840x2160
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No
 
Graphics Processor Info: 
DirectX: NVIDIA GeForce RTX 5080 (32.0.15.7270)
Init State: GPU for Export supported by default
User Preference: Auto
Enable HDR in Library: OFF
 
Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: C:\Users\johnt\Pictures\Lightroom\Lightroom Catalog-2-2-v13-3.lrcat
Settings Folder: C:\Users\johnt\AppData\Roaming\Adobe\Lightroom
 
Installed Plugins: 
1) AdobeStock
2) HDR Efex Pro 2
3) Loupedeck
4) Loupedeck2
5) Topaz Photo AI
 
 
GoldingD
GoldingD
Legend
March 27, 2025

Brings up an odd inquiry. How did the catalog get placed into a folder lacking access rights. Perhaps using a different user account? Perhaps a change to the folders access rights after the placement?

 

But, yes, you would think LrC could show a proper error message

 

Some history as to how the catalog got placed, who placed it, who if anyone changed rights, etc, would help the Adobe techs if listing to attempt to duplicate.

 

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices