Lightroom 8.3 crashes unless run as an administrator

  • 3
  • Problem
  • Updated 4 weeks ago
Hi,

Adobe did it again ! I installed the new LR 8.3 today and now I can't launch the program without running it as an administrator. Otherwise, it crashes immediately.

By the way, the name changed again : it's now Lightroom Classic instead of Lightroom Classic CC.
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes

Posted 1 month ago

  • 3
Photo of Carlos Cardona

Carlos Cardona

  • 428 Posts
  • 91 Reply Likes
Mac or Windows?
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
No. Windows 10. I should have mentioned this. Sorry.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5506 Posts
  • 1157 Reply Likes
I am not seeing any crash reports under this email address, Patrick. Do you get a Crash Submit dialog? Is it Microsoft or Adobe's? Any chance of a screen shot of the dialog?
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
Hi Rick,

I’m currently restoring my system to the state it was before the installation of 8.3. Actually, after a while, I could no longer launch LR, even as an administrator. PS has been also hit and has lost its preferences. I’ll give you more detailed information after the restoration terminates in a few hours. Sigh !

I’m retaining my comments for the moment but I do like these updates. Each one has its own “personality “.
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes


I have restored my system to its previous state, reinstalled LR 8.3 and I'm back to the same problem. LR crashes immediately before displaying anything when not launched as an administrator. PS is OK again now. (crossing my fingers). I have sent the crash report using the above address. If I launch LR as an administrator, there's no problem (for the moment).

Since it's obviously a permission problem, I'd like to know what are the permission requirements for LR. But nobody at Adobe has ever been able to give any information about that.  I have already checked this :

https://helpx.adobe.com/creative-cloud/kb/configuration-error.html

but this didn't help.

I'm really fed up with these permanent installation issues, be they with LR, PS or the Adobe CC Desktop app. I'm wasting too much time fixing this after almost each update. And no, this is not a problem with my system. I have absolutely no similar problem with any other application or with the OS (Windows 10 Pro 64-bit EN).
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5506 Posts
  • 1157 Reply Likes
I am not seeing any crash reports at that email address. Is that your actual Adobe ID also?
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
Yes, this is my Adobe ID. Could it be that the Crash Report tool be also buggy and doesn't send anything ? When I click on "Send Crash Report", the window closes immediately and I don't notice any network activity (I just checked this again). Any log about that operation that I could examine ?
Photo of G0apher

G0apher, Employee

  • 81 Posts
  • 27 Reply Likes
The crash logs are usually submitted in the background when you click Send. Do you see any logs under %AppData%\Adobe\CRLogs with version 8.3?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5506 Posts
  • 1157 Reply Likes
Still no reports from you - I have reports from others but none from your account, Patrick. 

Did you find them where G0apher suggested?
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
In the CRLogs folder, I can see an empty (zero byte) file named : crlog_91243384-8a38-46bc-9e49-42c4ae05c3d7_Adobe Lightroom Classic_8.3_[201905061635-edecdfdb].custom. The timestamp corresponds to the crash time. So obviously LR crashes before having the opportunity to write anything to that file.


Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
And yes, I have full control on the CRLogs folder, as well as the administrators and the SYSTEM. I have an administrator account and UAC is fully disabled on this system.
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
More info :

I deleted the empty crlog_91243384-8a38-46bc-9e49-42c4ae05c3d7_Adobe Lightroom Classic_8.3_[201905061635-edecdfdb].custom file. I noticed that it is only re-created when LR is run as an administrator. So, it's empty because there's nothing to report in that case, I guess (no crash).

If I don't run LR as an administrator, the file is not created. This seems to confirm that the crash occurs very early, before the program has terminated its initialization phase.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 5506 Posts
  • 1157 Reply Likes
If you create a new non-Administrator user and sign in with that user account does it crash?
Photo of J. Paul Moore

J. Paul Moore

  • 1 Post
  • 0 Reply Likes
I'm having the same issue on my Mac running Mohave 
Photo of Ad Dieleman

Ad Dieleman

  • 48 Posts
  • 3 Reply Likes
No such problem here with Lightroom 8.3 and Mojave 10.14.5
Photo of Carlos Cardona

Carlos Cardona

  • 428 Posts
  • 91 Reply Likes
J. Paul: Might be a corrupt cache or application state, or directory damage. Please give your Mac the "once over"! Run the free Onyx (https://www.titanium-software.fr/en/o...), reboot. (In Onyx just run almost everything in the Maintenance tab, deselecting things you may not want deleted, like Launch Services . Hit the "Options" button and deselect more stuff like Cookies & Other Site Data, Browser History, Form Values, etc.), then hit Run Tasks. After it's done it will ask for a reboot. Let me know if that worked, if not, I have other ideas.
Photo of Patrick Philippot

Patrick Philippot

  • 479 Posts
  • 134 Reply Likes
Just a guess...

Permission problems have appeared since years in various Adobe programs : Photoshop (which I always had to run as an administrator since the CC versions), installation of the Adobe CC Desktop app, now LR 8.3 (which has 2 related bugs : must be run as an administrator on my system + export issue), not mentioning other apps having similar problems.

Adobe probably have a (cross-platform ?) specialized code library handling access permissions that they use in multiple software. Maybe this code is buggy and fails in certain situations. This could explain why such problems appear so often and are in most cases never fixed.