Skip to main content
Participant
April 12, 2022

P: Crash (11.3) - Launch/Open Catalog - faulting module: substrate.dll : 411196 (Windows)

  • April 12, 2022
  • 140 replies
  • 16744 views

After updating LR today from the Cloud app on my PC it now fails with an error every time I open it. I have tried updating graphic card drivers, uninstalled and reinstalled LR itself but the problem persists. Was working fine yesterday. It is now unusable as the error occurs on starting up the software. Have sent crash reports via the error popup. Urgent help requested!

This topic has been closed for replies.

140 replies

Mario_tr
Inspiring
April 21, 2022

Thank you, no crash!

AntonioEdwardo
Participating Frequently
April 21, 2022

Thank you. I refreshed the list and did the upgrade.

All is well.

 

Images of RMNP
Known Participant
April 21, 2022

I just want to say thank you to the LR Classic team. The latest release fixed the problem! 

pab82_5
Participating Frequently
April 21, 2022

Yea! I just updated on my windows 10 and all works great now!!

johnrellis
Legend
April 21, 2022

"Creative Cloud still lists update available as 11.3 - does that really mean 11.3.1??"

 

No. If you don't see 11.3.1, you may need to refresh the Creative Cloud app -- see the link GoldingD just posted for details:

https://community.adobe.com/t5/lightroom-classic-discussions/lightroom-classic-release-11-3-1-is-now-available/td-p/12894053

AntonioEdwardo
Participating Frequently
April 21, 2022

Creative Cloud still lists update available as 11.3 - does that really mean 11.3.1??

Arnold-Norway
Known Participant
April 21, 2022

Today (21.04.22) I updated to 11.3.1 on my Windows 11. I can confirm that the to reported bugs are solved.
Exactly the same catalog file, which LrC 11.3 immidetately closed on startup, without any message, now opens perfectly in 11.3.1. The response is amazing. The other bug, showing incorrect cropped file size, is also solved. I will test more later.

RegardsArnold Hoddevik
DavinM
Participating Frequently
April 21, 2022

Also - I upgraded from 11.2 to 11.3.1, and the problem indeed seems to be resolved (with no catalog rebuild required).

 

Thank you!

Participant
April 21, 2022

I updated from 11.2 to 11.3.1 and the original bug from 11.3 seems to be solved.

A quick check on Windows and Mac works fine. 

I did not need to update my catalogue or similar, just start and it seems OK again. 

 

Thank you!