Lightroom Classic takes 2:28 to start completely

[DenTech444]

• LRC Version is 13.5
• Processor            Intel(R) Core(TM) i9-14900   2.00 GHz
• Installed RAM    32.0 GB (29.7 GB usable)
• System type        64-bit operating system, x64-based processor
• Pen and touch   No pen or touch input is available for this display
• Display Adapters: Intel UHD Graphics 770 and NVIDIA GeForce RTX 4070
• Windows 11 Pro, 23H2, OS Build: 22631.4037, Windows Feature Experience Pack 1000.22700.1027.0

• Expected result is that LRC would fully start in less time than my older computer (15 seconds)
• Actual complete start time is 2 minutes and 28 seconds.

Here is a description of what I observed during that 2:28: 

1. 2-3 seconds: visible is a mostly Gray window, but with title bar, Library, Develop etc. tabs and Splash screen appearing. The app extends across the full height and width of the 49-inch screen (3840x1080).  At lower left, visible are inactive icons for Main Window, second window, Library Grid, Go Back, and Go Forward. An empty filmstrip is visible.
2. 25 seconds: Splash screen disappears. On the left panel, 16 outlines (probably representing catalogue and folders), some partially hidden, appear and on the right panel a drop-down rectangle appears
3. 2:28 Seconds: both side panels show normally, Previous photo shows, the Library Tab is active, the bottom filmstrip is shown
4. The "What's New"  description window shows

[Moved from ‘Bugs’ to ‘Discussions’ by moderator, according to forum rules. A ‘bug’ is not just another word for any problem with software!]

[GoldingD]

Suggestion: Reset the Lightroom preferences

    I found two preference files
        Lightroom Classic CC 7 Startup Preferences.agprefs
        Lightroom Classic CC 7 Preferences.agprefs
    I copied each and deleted the originals.
    I restarted LRC and received an error message “An error prevented Lightroom Classic from opening the catalog.”
    I put back the startup preferences file and LRC started, but it still took 2:28
    Surprisingly, the preferences file reappeared with today's date, I guess by LRC, so I decided to reset the preferences using a different method.
        I saved a copy of the preference file
        I started LRC
        I reset the preferences using Shift Alt and clicking
        Apparently, that caused LRC to be restarted, but since I had other apps open, mostly covering LRC, I didn’t realize that immediately.
        So I ended LRC and then started it so I could time it.
        Time was 2:29 so no change.

It may be a typo error, but something sounds wrong in both of those descriptions of how you reset the preferences file.

In the first case, I assume that LrC was not running, correct? Deleting the preferences file (and yes you can delete both of those files) should not cause an error upon starting LrC. Both of those files should get recreated from scratch, and LrC should start.

"an error prevented Lightroom Classic from opening the catalog"

This sounds a lot like "The Lightroom catalog cannot be opened because another application already has it opened.""

• https://helpx.adobe.com/lightroom-classic/kb/lightroom-error-catalog-cannot-be-opened-lrcat-lock.htm...

A somewhat clumsy video of my accomplishing the above:

• https://www.dropbox.com/scl/fi/idm9o1gideexgltcn2pjy/2024-08-18-19-58-11.mp4?rlkey=p1w7xntueh2i3cqmo...

In the second case, I think you skipped over the part where your closed LrC, and then while holding down on Shift and ALT you clicked on the LrC startup Shortcut Icon in the Taskbar. Correct?

And a video of that (shortened a bit)

• https://www.dropbox.com/scl/fi/ugu4c38l33kj3pq4opqcr/2024-08-18-20-04-20.mp4?rlkey=9tj63pvdn4276bi4h...

P.S. the difference in how LrC came back up after deleting the preferences file is due to my (in the first) deleting both files whereas the second method only deleted the one file. You may have noticed an issue in the first one with existing catalog to bring up.

[DenTech444]

Although I used Shift Alt from within the LrC Preferences General Tab, it may be true that somehow LrC was still running, but I’m pretty sure that LrC terminated itself when I performed that Shift Alt > Reset Preferences operation.

I will revisit that.

In the meantime, I renamed what I think are the correct preference files, started LrC and saw the error reported. The attached file is a word document showing what I did and the final results. Could the path for the preference files be the wrong path?

[GoldingD]

"I used Shift Alt from within the LrC Preferences General Tab"

Ah,  Ok, this method:

Yes, that will work, and it will close, then restart LrC.

____________________________________________________________________________________

"and saw the error reported."

In Windows File Explorer, bring up the folder the catalog is in. Sounds like a lock file was not deleted.

 this was mentioned above and an Adobe document on it was listed:

• https://helpx.adobe.com/lightroom-classic/kb/lightroom-error-catalog-cannot-be-opened-lrcat-lock.htm...

If the lock file is indeed not getting deleted when LrC close, their is a problem.

[DenTech444]

Thanks for that suggestion.

With LrC not running, I see no lock file in the catalog folder.

But after LrC starts, I do see a lock file: Lightroom Catalog-v13-3.lrcat.lock. Based upon your link that appears to be normal behavior.

Again I appreciate your continued involvement with my issue!

[arjunhaarith]

Hi @DenTech444 ,

Thanks for sharing the information about the slowness. Inorder for us to investigate more on this issue, can you kindly provide the following files :

1. Diagnostic Report : You can go to Lightroom Classic -> Preferences -> Lightroom Sync

Hold the Alt key, and click Generate Diagnostic Report.  

2. Lrc_Console : Please go to C:\Users\xxxx\AppData\Roaming\Adobe\Lightroom\ and copy the lrc_console file

Please share the files mentioned in Step 1 and Step 2.

Thanks,

Arjun

[GoldingD]

Hi @DenTech444 ,

Thanks for sharing the information about the slowness. Inorder for us to investigate more on this issue, can you kindly provide the following files :

1. Diagnostic Report : You can go to Lightroom Classic -> Preferences -> Lightroom Sync

Hold the Alt key, and click Generate Diagnostic Report.  

2. Lrc_Console : Please go to C:\Users\xxxx\AppData\Roaming\Adobe\Lightroom\ and copy the lrc_console file

Please share the files mentioned in Step 1 and Step 2.

Thanks,

Arjun

By @arjunhaarith

As a member I am very happy to see that you are getting involved in this discussion.

You may have noticed one strange oddity in the info from the authors information. That being that the internal CAMERA RAW in LrC and the actual Adobe Camera RAW plugin used in PS are reporting that the GPU has 11.5 GB of VRAM available. Despite the LrC System Info showing 12 GB, and specifications on the GPU showing 12 GB. What is with that???? maybe a false hearing, but an oddity.

Also, a bit of confusion on the on Motherboard GPU or more likely Integrated Video Control vs add in GPU.

(My next reply to the author is to inquire on that.)

[DenTech444]

Thank you, Arjun.

I'm happy to see that a diagnostic reporting facility exists in LrC!

I have attached the specific file, lrc_console.log, you requested.

The process also created a zip file, but the upload feature in this thread does not allow it to be attached. So, I have attached instead a screen snapshot of the files extracted from the zip file. Please let me know if I should attach any of these files as well.

I very much appreciate your involvement and hope you can find a solution!

[arjunhaarith]

Hi @DenTech444 ,

This screenshot doesn't help much.

You can send them(diagnostic reports) over an email (haarithg@adobe.com)

Also another curious thought, have you enabled Sync (images either being downloaded/uploaded or paused)?

Thanks,

Arjun

[DenTech444]

Arjun, I emailed you the zip file. Please verify for me that it was received. Thanks.

As to your question, "Have I enabled Sync?",  I can say I did not select any button labeled "Enable Sync". 

Is there a procedure I should follow to enable Sync? If so, please share it and I will perform it.

In case it will help, I have attached a screen shot of my Lightroom Sync tab contents.

[arjunhaarith]

Hi @DenTech444 ,

I recieved the file, thank you !!

While we look at the files that you have sent, can you please try this activity and let me know if it is of any help :

1) Do you have Lightroom Desktop (just the LR as seen in Creative cloud) installed on your system ? If not, please install it once from Creative Cloud

2) Quit Lightroom Classic

3) Launch Lightroom Desktop

4) Quit Lightroom Desktop

5) Relaunch Lightroom Classic and share your experiences

Thanks,

Arjun

[DenTech444]

My pleasure, Arjun. I'm so thankful for your help!

I do have Lightroom Desktop. It started completely in 8 seconds and showed 26 photos. (I had tried using it a little in the past.)

I ended Lightroom Desktop and started Lightroom Classic. It again took 2:28 to start completely. Lightroom Classic's catalogue contains over 53,000 photos.

[DenTech444]

Arjun, it just occurred to me that you may have been asking if I had the cloud storage sync enabled. I checked and I see that it is paused.

[arjunhaarith]

Thanks for this information !!

[GoldingD]

On the:

• Intel UHD Graphics 770
• NVIDIA GeForce RTX 4070

I think that the Intel is an integrated video control, as opposed to the NVIDIA Dedicated GPU.

If you could reply back what your computer make/model is, and any options when purchased, that may clarify (a link to a web page would help)

If the Intel is just an integrated Video Controller, then LrC can basically ignore it. But some find it best to disable that in the Windows Device Drivers. Their are Adobe Documents on that. Some might even disable that in the BIOS (but can not recommend that as a non tech).

If the Intel is in fact an actual Dedicated (some say Discrete) GPU, with it's own VRAM, And you have that NVIDIA GPU card, then LrC will not like that one bit. (would you get an error???). LrC does not like multiple GPU's (if they are not the exact same make/model). Also, that high end NVIDIA would likely perform better than the Intel.

So, an inquiry, have you disabled the Intel UHD Graphics 770?

• https://helpx.adobe.com/lightroom-classic/kb/lightroom-gpu-faq.html
• https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html
• https://www.techpowerup.com/gpu-specs/uhd-graphics-770.c3844
•  

[DenTech444]

Thanks for the further inquiry and your interest in my issue.

The computer is a Dell XPS Desktop 8960. The Intel graphics card is described as integrated. I hope this link works and will help: Dell XPS Desktop - Computer Desktops | Dell USA

If you're asking if I disabled the Intel display adapter driver, then yes, I disabled each of the display adapters' drivers, but not both simultaneously. When I disabled the Intel driver, the load time actually took a little longer. The exact info is somewhere in this long conversation. 🙂

[DeeGee9229]

I'd be interested to see if there's been any progress on this.  Having very similar problems with a new HP desktop also with Intel UHD Graphics 770 and NVIDIA GeForce RTX 4070 cards (although mine is a 4070Ti). 

My system ran well for a few weeks but then developed the same Lightroom taking an age to open.  It went from a few seconds to over two minutes and the only thing I can think of which may have had an impact on it was me installing another program (Davinci Resolve 19)  which includied a number of Visual C updates.  I tried uninstalling Resolve, but it didn't have any noticable effect on the lag in Lightroom opening up.  I've gone throught this thread trying the various suggestions offered, but without any success

Hopefully this isn't seen as hijacking your thread, but very similar issue so having a common solution would be great

[AxelMatt]

What have you done exactly for trying to solve the issue?

Is your system up-to-date? Do you have installed all recent updates and patches for the operating system and the device drivers, especially the graphic driver. If you have a NVidia graphic card installed, make sure that you are using the recent Studio version of the driver, not the Game Ready version.

Please provide a copy of your 'System Info'. This can be get from the LrC Help > System Info menu item. There's a copy button in the System Info dialog. Press this button and paste the info into your next forum post.

Do you have try to disabling the processor internal graphic card? To disable the lesser of the two cards, use the Device Manager on Windows. In the Device Manager, right-click the card's name and choose Disable.

[DeeGee9229]

Hi AxelMatt

Thanks for your reply

As I mentioned previously, I didn't want to Hijack this thread hence why I didn't inlude my 'System Info'.  However, I do think that the issues I've encountered are too close to DenTech444's description to be coincidental, and since you've asked the System Info report from LRC is:

Lightroom Classic version: 13.5 [ 202408062022-6258095b ]

License: Creative Cloud

Language setting: en

Operating system: Windows 11 - Home Premium Edition

Version: 11.0.22631

Application architecture: x64

System architecture: x64

Logical processor count: 32

Processor speed: 2.9GHz

SqLite Version: 3.36.0

CPU Utilisation: 0.0%

Power Source: Plugged In

Built-in memory: 65216.9 MB

Dedicated GPU memory used by Lightroom: 1448.0MB / 11996.0MB (12%)

Real memory available to Lightroom: 65216.9 MB

Real memory used by Lightroom: 11053.8 MB (16.9%)

Virtual memory used by Lightroom: 12340.9 MB

GDI objects count: 1052

USER objects count: 2549

Process handles count: 13907

Memory cache size: 14291.0MB

Internal Camera Raw version: 16.5 [ 1953 ]

Maximum thread count used by Camera Raw: 5

Camera Raw SIMD optimization: SSE2,AVX,AVX2

Camera Raw virtual memory: 3002MB / 32608MB (9%)

Camera Raw real memory: -167338MB / 65216MB (-256%)

Cache1: 

Final1- RAM:273.0MB, VRAM:12.0MB, 1U1A6592.CR3

NT- RAM:273.0MB, VRAM:12.0MB, Combined:285.0MB

Cache2: 

m:14291.0MB, n:272.9MB

U-main: 167.0MB

System DPI setting: 96 DPI

Desktop composition enabled: Yes

Standard Preview Size: 1920 pixels

Displays: 1) 1920x1080, 2) 1920x1080

Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

Graphics Processor Info: 

DirectX: NVIDIA GeForce RTX 4070 Ti (32.0.15.6081)

Init State: GPU for Export supported by default

User Preference: GPU for Export enabled

Enable HDR in Library: OFF

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic

Library Path: C:\Users\daveg\Pictures\Lightroom Catalogs\Daves HP 23 August\Daves HP.lrcat

Settings Folder: C:\Users\daveg\AppData\Roaming\Adobe\Lightroom

Installed Plugins: 

1) AdobeStock

2) Canon Professional Print && Layout

3) Flickr

4) Nikon Tether Plugin

5) Topaz Photo AI

6) Tourbox

Config.lua flags: 

Adapter #1: Vendor : 10de

Device : 2782

Subsystem : 8771103c

Revision : a1

Video Memory : 11996

Adapter #2: Vendor : 8086

Device : a780

Subsystem : 8a9b103c

Revision : 4

Video Memory : 80

Adapter #3: Vendor : 1414

Device : 8c

Subsystem : 0

Revision : 0

Video Memory : 0

AudioDeviceIOBlockSize: 1024

AudioDeviceName: $$$/dvaaudiodevice/SystemDefaultAndEffectiveDeviceName=System Default - Speakers (Realtek(R) Audio)#{comment}DVAAU-4201250: Open the audio hardware preferences page.

AudioDeviceNumberOfChannels: 2

AudioDeviceSampleRate: 48000

Build: LR5x120

Direct2DEnabled: false

GL_ACCUM_ALPHA_BITS: 16

GL_ACCUM_BLUE_BITS: 16

GL_ACCUM_GREEN_BITS: 16

GL_ACCUM_RED_BITS: 16

GL_ALPHA_BITS: 0

GL_BLUE_BITS: 8

GL_DEPTH_BITS: 24

GL_GREEN_BITS: 8

GL_MAX_3D_TEXTURE_SIZE: 16384

GL_MAX_TEXTURE_SIZE: 32768

GL_MAX_TEXTURE_UNITS: 4

GL_MAX_VIEWPORT_DIMS: 32768,32768

GL_RED_BITS: 8

GL_RENDERER: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2

GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA

GL_STENCIL_BITS: 8

GL_VENDOR: NVIDIA Corporation

GL_VERSION: 4.6.0 NVIDIA 560.81

GPUDeviceEnabled: false

OGLEnabled: true

GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_AMD_vertex_shader_viewport_index GL_AMD_vertex_shader_layer GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_fragment_shader_interlock GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp GL_ARB_post_depth_coverage GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_locations GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shader_viewport_layer_array GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_sparse_texture2 GL_ARB_sparse_texture_clamp GL_ARB_spirv_extensions GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_filter_anisotropic GL_ARB_texture_filter_minmax GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transform_feedback_overflow_query GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_multiview_texture_multisample GL_EXT_multiview_timer_query GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_post_depth_coverage GL_EXT_provoking_vertex GL_EXT_raster_multisample GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_formatted GL_EXT_shader_image_load_store GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_sparse_texture2 GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_filter_minmax GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shadow_lod GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_R8 GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_EXT_memory_object GL_EXT_memory_object_win32 GL_NV_memory_object_sparse GL_EXT_win32_keyed_mutex GL_KHR_parallel_shader_compile GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_EXT_semaphore GL_EXT_semaphore_win32 GL_NV_timeline_semaphore GL_KHR_shader_subgroup GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_equation_advanced_coherent GL_NVX_blend_equation_advanced_multi_draw_buffers GL_NV_blend_minmax_factor GL_NV_blend_square GL_NV_clip_space_w_scaling GL_NV_command_list GL_NV_compute_program5 GL_NV_compute_shader_derivatives GL_NV_conditional_render GL_NV_conservative_raster GL_NV_conservative_raster_dilate GL_NV_conservative_raster_pre_snap GL_NV_conservative_raster_pre_snap_triangles GL_NV_conservative_raster_underestimation GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_feature_query GL_NV_fence GL_NV_fill_rectangle GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_coverage_to_color GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_fragment_shader_barycentric GL_NV_fragment_shader_interlock GL_NV_framebuffer_mixed_samples GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_geometry_shader_passthrough GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_program_multiview GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_memory_attachment GL_NV_mesh_shader GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_path_rendering_shared_edge GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_primitive_shading_rate GL_NV_query_resource GL_NV_query_resource_tag GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_representative_fragment_test GL_NV_sample_locations GL_NV_sample_mask_override_coverage GL_NV_scissor_exclusive GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_atomic_float64 GL_NV_shader_atomic_fp16_vector GL_NV_shader_atomic_int64 GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_shader_subgroup_partitioned GL_NV_shader_texture_footprint GL_NV_shading_rate_image GL_NV_stereo_view_rendering GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_dirty_tile_map GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_rectangle_compressed GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_uniform_buffer_std430_layout GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NV_viewport_array2 GL_NV_viewport_swizzle GL_NVX_conditional_render GL_NVX_linked_gpu_multicast GL_NV_gpu_multicast GL_NVX_gpu_multicast2 GL_NVX_progress_fence GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle

GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_OVR_multiview GL_OVR_multiview2 GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control 

My system drivers are all up to date, and I'D downloaded and installed the latest Nvidia Studio Graphics Driver from the NVidea website.

I disabled the Intel 770 graphics card and the NVidea RTX7070TI separately, and I also set LRC not to use Graphics card.  I reset LRC's Preferences and also created a new catolog adding only a few photos (My Catolog is on the internal C:: Drive which is an SSD.  My images live on an extrnal SSD)

After each of these changes, I've rebooted LRC and there's been no discernable difference in Startup time.

Once LRC is up and running it works well but the startup time is annoying me more than it should!!!

I've also copied my Catalog over to my laptop which struggles if you add more than a handful of masks and definitely doesn't like  the DeNoise function.  It opens LRC in  few seconds

Not sure there's much else I can add just now

Thanks

[AxelMatt]

Hi AxelMatt

Thanks for your reply

As I mentioned previously, I didn't want to Hijack this thread hence why I didn't inlude my 'System Info'.  However, I do think that the issues I've encountered are too close to DenTech444's description to be coincidental, and since you've asked the System Info report from LRC is:

...

By @DeeGee9229

"...are too close to..." aren't the same!! An this differences can be the reason for the problems.

I think you've reset the LR preferences to the default settings. If not, please check if the reset helps.

On which drive is your catalog stored? If it's a normal hard drive (no SSD !!!) please check the defragmentation of the drive and try to defrag this drive.

Another try is to create a new catalog, import several images and check if it's help. Alternatively, you can also export pictures from your old catalog to the new one.

If this all doesn't help I would try a complete and clean reinstallation of th Adobe applications.

Please follow the steps below:

• Backup all personal data, like templates, presets etc.
• Uninstall everything cc including preferences,    https://helpx.adobe.com/creative-cloud/help/uninstall-remove-app.html
• Then uninstall the cc desktop app,    https://helpx.adobe.com/creative-cloud/help/uninstall-creative-cloud-desktop-app.html
• Clean your computer of cc files per   http://www.adobe.com/support/contact/cscleanertool.html
• Restart your computer (don't skip this)
• Reinstall the cc desktop app,    https://www.adobe.com/creativecloud/desktop-app.html
• Use the desktop app to install your cc programs/trials
• Restore your personal data.

If you're unable to install the cc desktop app at this stage, use an administrator account (solution 4 here, https://helpx.adobe.com/creative-cloud/kb/creative-cloud-missing-damaged.html).

If that doesn't help, I would even consider a complete reinstallation (including the operating system)

[DeeGee9229]

Hi, AxelMatt

Thnaks for your further suggestions.  I'd addressed many of them in my previous reply so I won't re-visit those.

I did however, follow through on your suggestion of removing the CC Suite as per the guides you linked to.  I rebooted and then re-installed CC Desktop from which I installed LRC.  Even without adding any further Apps, the lag in startup showed no noticeable difference. 

I'm afraid a full system reinstallation is a step too far for me just now - I think it would be little more than a hopeful punt.  For now I'll see if GenTech444's engagement with Adobe Tech Support comes up with anything further.

Thanks again 

[DenTech444]

Hi, DeeGee9229,

I don't have a solution yet, but I did run into some surpising and bad developments.

I worked with Adobe tech support on this. Support had me create a some diagnostic logs, which I thought was a good idea. After I sent the logs, Adobe support asked me to try starting LrC in Map mode instead of development mode.  The procedure was to select Maps , then end the program and restart LrC. That seemed like a reasonable approach to me.

I noticed I was in Library mode, not delevelop mode. I selected the Map tab. 

Switching to Map from Library took 27 seconds. Thereafter starting LrC took over 4 minutes. And it started with the Library tab, not the map tab. Because of this extra long time I thought I should reboot my computer.

I rebooted. During boot, a new BIOS was automatically installed with a warning not to interrupt the process.

Now total LrC start time was 6:20 to the library tab. Collections but NO FOLDERS were shown in the left pane.

I ended LrC and ran Windows virus scan. No problems were reported.

I started LrC again. This time it took 10 minutes. The Library loupe view of a photo was visible, but right-clicking on it did not allow me any selections. I was hoping to have it show me the Windows folder in which the photo resided. So, it appears that LrC may not be fully loaded.

In summary, the LrC app appears to be in a state where I can’t even load it fully.

I asked Adobe Tech Support on Wednseday if I should unisnstall LrC and reinstall it. Support's Arjun, who had been very helpful, copied a different tech support person, Anadi,  who would assist me further.

When I didn't hear back form Anadi, on Saturday I emailed Arjun. Today (Monday) I receive an email from Adobe support's Ankit. He has suggested 5 things to try and asked me about my hard drive set up. I have already tried some of his suggestions and believe he should have know about that, but I will see where this goes.

[DeeGee9229]

Hi, DenTech444

Thanks for the reply. 

Worrying indeed.  I don't think I'll try the 'Open in Maps' suggestion unless there's any evidence it might help, clearly it hasn't helped at all in your case.  I'll keep tabs on this thread to see where it goes

[DenTech444 · Accepted solution]

Solution found by Adobe tech support's Alok! My Lightroom now loads completely in 7-8 seconds.

I'll start with the answer, and then fill in the details.

Actual "fix"

On my Windows 11 Pro PC, in C:\Users\ddm44\AppData\Roaming\Adobe, Alok renamed the folder, Lightroom, to LightroomOld and then started Lightroom.

Why this worked

After Alok systematically investigated various areas, he recognized that one or more (I'll call them) personal configuration files that contain info such as Presets I created, Plug-in links I added, etc. might be corrupted. To remove all these files from Lightroom's view, he renamed the folder described above and then restarted Lightroom. Lightroom created a default Lightroom subfolder in the Adobe subfolder and loaded quickly.

Why I think this corruption occurred

When I first bought my new compter, I had to tranfer more than a TB of data to it - from my D:\Pictures and from D:\Documents. I also think I copied other files as well, which likely included the AppData areas. 

To perform this copy I tried a copy over WIFI to the new computer. This failed several times, so I bought a 2 TB thumb drive, copied to it from the old computer, and then from it to the new computer. To save time, I opted to skip files that already existed.

I suspect that one or more of the skipped files was not completely copied...and maybe corrupted. This is just a guess.

Other things that Alok changed

NVIDIA driver

Alok also manually searched for and found an NVIDIA driver that was 4 days newer than my driver. He installed the Studio Driver, though he said the gaming driver would also be OK. He then rebooted the system and restarted Lightroom. We "felt" that Lightroom started a few seconds more quickly.

OneDrive-connected Lightroom Files

Alok noted that Lightroom files were being synchronized to OneDrive. He stopped any Lightroom files from being written to a OneDrive-linked folder, though I'm not sure how he did that. As a result, the load time decreased to a little over 2 minutes according to Alok. This was an improvement, though not a total resolution.

Otherwise, the system configuration is unchanged

For example, both GPUs are enabled. The screen resolution is 3840 x 1080. Lightroom occupies the entrie 49" monitor's width.

I'll need to work more with LIghtroom to see if everything is OK, but so far, the load time problem has been resolved!

[DeeGee9229]

Hi Dentech444

Brilliant news that  between you and Adobe Tech Support, you seem to have got to the bottom of th issue.

I tried the fix on my system and it's worked a treat, so thanks for the update

[DenTech444]

I'm very glad that worked for you, DeeGee!