Skip to main content
Justice88
Inspiring
June 16, 2023
Answered

Lightroom freezes for 2 minutes, 20 seconds after launching.

  • June 16, 2023
  • 7 replies
  • 883 views

So this is an issue that's been on going for quite a while.  When I first started using Lightroom Classic about 2 years ago, I didn't run into this problem.  At some in the past 6 months to a year, I began running into my Lightroom Classic loading normally, and functioning normally up until about 20 seconds had passed, at which point it would freeze for 2 minutes with 100% consistency.  This issue occurrs on all catalogs - whether they be with only RAW, only Smart Previews, or both, also irrespective of which drive the catalogs are located on (I have an M.2 SSD, SSDs, and an External HDD).  This 2 minute freeze also happens irrespective of if I have LrClassic as the active window, it still goes into a "Not Responding" status on the window 20 seconds after launching for the duration of 2 minutes.  No other applications fail to respond during this 2 minute period.

The strange thing is though that I recently upgraded my Windows 10 OS to Windows 11 and did a fresh install and wipe of all my drives and for about a week (maybe 2) the issue went away.  However, the issue resurfaced again about a week ago, and it's finally baffled me enough to bring it around to the community.

Possibly valuable information but probably not:  I noticed while doing my timing of the freeze as making this post, that my task manager will show Adobe Lightroom Classic while its frozen, but it will disappear and then reappear (the memory usage and CPU usage both remain roughly the same between it's short and repeated hiatus).  

Specs:
i9-9900k
2070 Super 8GB
32GB DDR4 3200 (4x8GB)
WD NVME M.2 SSD 2TB - OS and LrC both installed on this with 1.6TB of free space.

I am using the most up to date version of LrClassic and I have tried: 
-Resetting preferences (alt+shift+launch)
-Removing all presets
-Removing all imported camera profiles
-Removing all local adjustment presets
-Disabling all plugins
-Turning Off GPU Acceleration 
-Reinstalling LrClassic
-Praying

Praying only helps slightly because I am distracting myself for a portion of the 2 minutes which makes time pass differently, but the stopwatch on my phone brings me back to the reality of the situation unfortunately.

Either way, I am at a loss, any suggestions would be helpful.
Thank you

This topic has been closed for replies.
Correct answer Justice88

So...  I feel a bit foolish at the moment, becuase I can't say with 100% certainty that this fixed it, but it seems a bit too coincidental.
When I created the new user account and went to sign out - I noticed I had 2 Windows updates and without thinking about it, I went ahead and restarted to update.  I then launched LrC on the second account and it worked fine, and then upon logging into my original account and launching LrC, the issue was no longer happening on my main account.  

I am only hesitant to state that this "fixed" my issue for sure because I had been dealing with this issue for a very long time on Windows 10 as well, prior to updating to 11, and I am pretty diligent on doing my updates.  However, maybe it was some long running issue with Windows OS that was causing it and it just recently got fixed.

Nevertheless, I'll leave it alone for now because if it's not broken I am not going to bother fixing it, but if I run into the problem again I will go with your clean uninstall and see if that resolves it.

Thank you for the help, and the (possible) moral of the story is to do your updates. Lol.

7 replies

Participant
June 16, 2023

Here are three additional troubleshooting steps that can help you narrow down the problem:

  1. Create a new test catalog and import a small number of photos. Then, restart your computer (not just LR) and check if the issue still persists. This step helps determine if the problem is related to the catalog or your computer.

  2. Create a new user account on your computer and repeat the previous step while logged into that account. Sometimes, user-specific files can cause issues, so this can help identify if any of those files are damaged.

  3. Perform a clean uninstallation and reinstallation of all Creative Cloud apps using the Adobe Creative Cloud Cleaner tool. This ensures a fresh installation and can resolve any conflicts or issues that might have occurred during the previous installation.

By following these additional steps, you can gather more information and potentially resolve the problem you are facing.

Justice88
Justice88AuthorCorrect answer
Inspiring
June 16, 2023

So...  I feel a bit foolish at the moment, becuase I can't say with 100% certainty that this fixed it, but it seems a bit too coincidental.
When I created the new user account and went to sign out - I noticed I had 2 Windows updates and without thinking about it, I went ahead and restarted to update.  I then launched LrC on the second account and it worked fine, and then upon logging into my original account and launching LrC, the issue was no longer happening on my main account.  

I am only hesitant to state that this "fixed" my issue for sure because I had been dealing with this issue for a very long time on Windows 10 as well, prior to updating to 11, and I am pretty diligent on doing my updates.  However, maybe it was some long running issue with Windows OS that was causing it and it just recently got fixed.

Nevertheless, I'll leave it alone for now because if it's not broken I am not going to bother fixing it, but if I run into the problem again I will go with your clean uninstall and see if that resolves it.

Thank you for the help, and the (possible) moral of the story is to do your updates. Lol.

GoldingD
Legend
June 16, 2023
quote I noticed I had 2 Windows updates and without thinking about it, I went ahead and restarted to update.  I then launched LrC on the second account and it worked fine, and then upon logging into my original account and launching LrC, the issue was no longer happening on my main account.  


By @Justice88

 

Having just put together a new workstation with Windows 11 (as opposed to 10) I noticed that the Windows update is quite a bit more inclusive as to non OS updates. I am refering to drivers, and not just the GPU driver (that it may or may not ignore, deferring to GPU mfg driver update support). You may have had a long standing driver issue, with say the Chip Set, or the USB controller(s), WiFi, Ethernet, etc. (update history should show)

Justice88
Justice88Author
Inspiring
June 16, 2023
quote
quote I noticed I had 2 Windows updates and without thinking about it, I went ahead and restarted to update.  I then launched LrC on the second account and it worked fine, and then upon logging into my original account and launching LrC, the issue was no longer happening on my main account.  


By @Justice88

 

Having just put together a new workstation with Windows 11 (as opposed to 10) I noticed that the Windows update is quite a bit more inclusive as to non OS updates. I am refering to drivers, and not just the GPU driver (that it may or may not ignore, deferring to GPU mfg driver update support). You may have had a long standing driver issue, with say the Chip Set, or the USB controller(s), WiFi, Ethernet, etc. (update history should show)


By @GoldingD


Totally possible, the updates that I had performed yesterday were the following -
2023-06 Cumulative Update (KB5027231)
2023-06 Cumulative Update for .NET Framework 3.5 and 4.8.1 (KB5027119)

There was also a Security Definition Update that happened yesterday (earlier though as it applies automatically without reset).  There were no driver updates since 5/26 (when I reformatted originally).

I like to consider myself somewhat technologically aware when it comes to Windows based computers, but to be honest, the information in the articles for Windows updates is over my head at times, including the ones from these two updates.  Basically, I can't say with any certainty (due to my lack of knowledge), whether or not the updates that I did yesterday, had any impact on the systems which Lightroom utilizes. It's a lot of jargon to me and I am not particularly interested enough in researching it myself to conclude one way or the other lol.  I am all ears if you are wanting to shed some light on whether you believe those particular updates could have impacted LrC, or if it's purely coincidental and I may end up experiencing the issue again.

Similarly to my Windows Updates, I am pretty on top of my drivers (as much as you reasonably can be atleast without continuously checking the manufacturer website), and typically performed clean uninstalls of drivers (that I comfortably could) before installing the newest updates.  As mentioned as well, this was a totally clean install of windows, I had wiped all of my hard drives and installed Windows 11 from an external SSD.  So if it was a driver related conflict that would have made it through by doing just an upgrade, I wouldn't see how it made it through with all of my storage devices being cleared.  Maybe I am missing something or there are hardware related updates through Windows which are stored in the motherboard.

I am mostly just happy it seems to be working for now, it's been super annoying to wait 2 minutes every time I launch Lightroom. My workflow involves opening a lot of catalogs with only Smart Previews to check the work of my editors.

johnrellis
Legend
June 16, 2023

Try the clean uninstall--that should remove all the user-specific stuff.

Justice88
Justice88Author
Inspiring
June 16, 2023

Well, creating a new user did alleviate the issue.
That being said, what is my course of action?

Justice88
Justice88Author
Inspiring
June 16, 2023

I know that #1 on your list can be ruled out because while I normally launch LrClassic by choosing a particular catalog, when I uninstalled and reinstalled, I ran LrC without a catalog chosen and it created a new catalog which had nothing in it, and it froze for the same duration as it always does.

I'll try the other 2 steps you mentioned and get back to you shortly.

johnrellis
Legend
June 16, 2023

Three more troubleshooting steps that might narrow down the problem:

 

1. Make a new test catalog and import just a few photos. Then exit and restart your computer (not just LR) -- does the problem still occur?

 

2. Make a new user account, and then while logged into that user account, repeat step 1. There are many user-specific files that can be left behind by a normal uninstall, and this could rule out that one of them is damaged.

 

3. Do a clean uninstall/reinstall of all Creative Cloud apps using the Adobe Creative Cloud Cleaner tool:

https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html

Justice88
Justice88Author
Inspiring
June 16, 2023

I'd like to add one other thing I tried, which was I also attempted to install LrClassic on a different drive than the M2 NVME SSD.  I attempted to install it on a 250GB SSD that had nothing else on it.

GoldingD
Legend
June 16, 2023
quote

I'd like to add one other thing I tried, which was I also attempted to install LrClassic on a different drive than the M2 NVME SSD.  I attempted to install it on a 250GB SSD that had nothing else on it.


By @Justice88

So, you attempted running with the LrC program installed on the extra SSD? Or are you referring to the catalog? Placement of the program should not be a big performance issue/fix. Placement of the catalog can. Mind you that NVME would probably be better than the SSD, assuming the read/wright speed to/from it is faster. OR if the NVME is running short on space, then yep, perhaps place the catalog on the SSD.

 

Also, placement of the LrC/ACR CACHE can be of importance, fastest drive, BUT on Windows OS, preferably not same drive as Windows Paging file (typically C)

 

Justice88
Justice88Author
Inspiring
June 17, 2023
quote

So, you attempted running with the LrC program installed on the extra SSD? Or are you referring to the catalog? Placement of the program should not be a big performance issue/fix. Placement of the catalog can. Mind you that NVME would probably be better than the SSD, assuming the read/wright speed to/from it is faster. OR if the NVME is running short on space, then yep, perhaps place the catalog on the SSD.

 

Also, placement of the LrC/ACR CACHE can be of importance, fastest drive, BUT on Windows OS, preferably not same drive as Windows Paging file (typically C)

 


By @GoldingD


I had uninstalled Lightroom and reinstalled it on the SSD just to see if there was maybe an issue with my NVME drive (C:), not that I've had any reason to believe there would be.  After ruling out that as a factor I did reinstall it again onto the NVME drive. 

I store my catalog files on 2 separate SSDs.  One SSD drive (E:) is for personal Catalog with RAW/Smart Previews, another SSD drive (D:) for work Catalogs with RAW/Smart Previews.  Once I consider a catalog "done" I store the RAW, Catalog files, and Smart Previews ZIP on my NAS.  If I ever have to pull a dated catalog, which is rarely becuase I also utilize 2 master catalogs (personal and work) that the individual project catalogs are imported into, I know that they can't be read from the NAS so they're just copied back to their respective drive.

On the subject though, do you think it would be beneficial to me to change my windows page file location to my 250GB SSD (F:) which is empty at the moment, and then transition my catalogs onto the NVME (C:)?  I don't know much about the effects of moving my page file system, I have only ever messed with it to change the page file size a long time ago becuase a certain game I played had a bug that increasing it's size would correct.  

To go even further with it... if I were to move my page file system, transition catalogs to the NVME, I would presume then I could see additional benefits of smart preview creation by also having RAW on the NVME for the smart preview creation process.  Given it's only 2TB, and the Smart Preview catalogs I am creating for editors contain RAW data anywhere from 500GB to 1TB in size (per catalog), it would add an additional transfer proccess to my workflow since I would not want to exceed 80%(?) space utilization on the NVME. 

I understand this probably doesn't make much sense, because my workflow is a bit unusual I think... but if you are following you can disregard my attempt here to simplify my process as it is and the proposed change I am questioning.

Current Process: Download event/project RAW via Dropbox App to SSD (D:)> Copy RAW out of Dropbox folder to Temporary RAW folder / [Project] on SSD (D:)> Import RAW into Work Master Catalog (D:)> Export [Project] Folder as new catalog with smart previews> compress smart previews> upload to Dropbox for assignment
-- 3 to 7 days later --
download edited catalog to SSD (D:)> open Work Master Catalog> import edited catalog into Work Master Catalog> Export edited [Project] as JPG >move RAW to NAS

Proposed Process: Download event/project RAW via Dropbox App to SSD (D:)> Copy RAW out of Dropbox folder to Temporary RAW folder / [Project] on NVME (C:) > Import RAW into Work Master Catalog (C:)> Export [Project] Folder as new catalog with smart previews> compress smart previews> upload to Dropbox for assignment > Move RAW back to SSD (D:)
-- 3 to 7 days later --
download edited catalog to NVME (C:)> open Work Master Catalog (C:)> import edited catalog into Work Master Catalog> Export edited [Project] as JPG >move RAW to NAS 

Ideally, I would like to keep the RAW on the (C:) until after I export the JPGs becuase I would imagine(?) it would be faster to export as JPG, but I don't think I could reasonably keep the RAW there for a week since I would have another 2-4 catalogs needing to be built in that time frame.  I don't have hard data to support this but it seems like Smart Preview generation is a lengthier process for my computer than exporting JPGs, but I could be wrong.

I am sorry if am feeding you more questions than you were willing to chew haha.  But, you got my brain considering another option that may be able to cut back on some time in my process, which largly consists of the bottleneck of creating smart previews.  Any advice or opinion would be greatly appreciated.  

Thank you