Skip to main content
Participant
March 22, 2024
Question

LrC 13.2 or any such iteration fails to load on Windows 11 Build 26085 inside preview

  • March 22, 2024
  • 2 replies
  • 149 views

some context: I am using my companys account which has an 80gb enterprise plan for all employees.

 

I was able to open and edit photos in lightroom about 20 days ago and since then lightroom was updated to 13.2 and it has failed to work on my system ever since. I tried many methods, changing lighroom.exe's priority to be high in task manager and ending task and opening again- Every time it opens as a background app and not a forground app which is wierd. 

 

I can share technical info in more detail if you direct me as to what to send as well.

Please help.

This topic has been closed for replies.

2 replies

dj_paige
Legend
April 8, 2024

I doubt there's anything you can do if it doesn't work on a development version of Windows 11. You'll just have to wait until Adobe releases a version of LrC that does work with the production version of Windows 11 Build 26085 inside preview  (which of course will have a different name indicating it is now production).

Sameer K
Community Manager
Community Manager
April 8, 2024

Hey, @Jagteshwar Preet Singh. Welcome to the Lightroom Community. I'll help you figure this out.  here is the catalog stored? On the internal or external drive? 

 

Try these suggestions:

1 - Launch Lightroom Classic with a new catalog by pressing the ALT key at launch & Create a new catalog.

2 - Try resetting Lightroom Classic following the manual method shared here: https://adobe.ly/4aPIWol

3 - For now, reverse any changes made to the Lightroom.exe in the Task Manager. 

 

Let me know how it goes. Thanks!
Sameer K

Participant
April 8, 2024

Hey Sameer, My catalog was stored on an external drive but i moved it to an internal drive and same issue kept popping up. retty sure its not a memmory type issue.

Ah thats the shortcut for the new catalog, about to try that right now; I've already reset it, still same issue was happeneing. At this point its been about 6 days since i started it and tried dealing with it again.

Changes have never actually stuck with the program in the task manager so i think they are already off?

I wonder if corrupted catalogs could cause this? i Heard someone talk about corrupted catalogs before on here