Lightroom CC Error

[DacrimL]

Ok since upgrading to Win 10 the problem is it won't load.

Have uninstalled and reinstalled but the same thing, the following is an image of the message I keep getting.

Any ideas on how to either get LR to open or how to fix this problem.

LR Capture.JPG

All the backups from LR are there but it just doesn't seem to recognise them.

Many thanks for any assistance

[Kym]

I'm running the Latest LR CC 2015 no issues.

What version are you running?

[DacrimL]

The same Kym

Lightroom CC 2015

[Kym]

Contact Adobe Support and find out how to repair a corrupt catalogue

[fillum]

All the backups from LR are there but it just doesn't seem to recognise them.

I'm not sure what you mean by "recognise" here DacrimL. Are you expecting LR to access backup catalogs automatically, or have you tried to load them manually?

If you haven't already tried I'd do this...

1. make a copy of your current 'production' catalog (or rename it)
2. copy your most recent backup catalog into your 'production' directory. Note that backup catalogs now appear to be 'zipped' since the latest release of LR so you may need to unzip it
3. open LR and see if it loads

If you get the same error it would indicate that the problem is likely not the catalog.



Cheers.

[DacrimL]

Ok have contacted Adobe in regards to my issue, so am waiting for an answer.

I did try their trouble shooting guide to no avail.

[DacrimL]

Issue fixed, thanks to Adobe.

However the issue is created by M$ and the update, as it changes many file and folder attributes. The following should remedy the problem (it has for me)

Open the Program Files/Adobe/Adobe Lightroom folder.
Right-click on the Lightroom.exe file then Choose Run asadministrator
Also
Go to Pictures/Lightroom folder
Right-click on Lighroom Folder
Choose Properties > Security > Edit.Select your usernamein "Group or user names". and
Choose Full Control under Permissions.
Select Ok

[arthurking83]

I edited your reply with the solution, and changed the text colour to make it more legible with the dark theme.

So it seems that it was s simple security issue.

good to know the solution.