Skip to main content
Participant
June 19, 2014
Answered

Lightroom 5.5 "Develop Module Disabled, please renew your membership"

  • June 19, 2014
  • 46 replies
  • 63760 views

Since updating throughout Creative Cloud" a couple of hours ago, I get "Develop Module Disabled, please renew your membership" with Lightroom 5.5 while all other programmes work fine. My membership is up to date and paid in advance! What do I do?

This topic has been closed for replies.
Correct answer Scott V

Hello All,

If you are having this issue still please try the following troubleshooting steps.

Solution 1: Sign out of Lightroom 5.5 and then sign back in with your Adobe ID.

Solution 2:

Set permission to SLStore & SLCache Folder ::

NOTE: Perform this procedure two times, once each for the SLCache and the SLStore folders.

Mac:

  • Use the Finder to navigate to Library/Application Support/Adobe/SLStore or Library/Application Support/Adobe/SLStore.
  • Control-click the folder and choose Get Info.
  • Expand the Sharing & Permissions section.
  • Click the lock icon in the lower-right corner. Enter your administrator user name and password when prompted, and then click OK.
  • Set permissions:

System: read/write

Admin: read/write

Everyone: read/write

  • Click the Gear icon, and select Apply to Enclosed Item. Close the Get Info dialog box.

Win 7/ Win 8:

SLStore :: ProgramData\Adobe\SLStore
SLCache::

Win 32 bit: Program Files\Common Files\Adobe\SLCache\

Win 64 bit: Program Files (x86)\Common Files\Adobe\SLCache\

  • In File Explorer, right-click the SLCache or the SLStore folder and choose Properties.
  • Click the Security tab and set permissions:

Administrators: Full Control

Power Users: Everything but Full Control and Special

System: Full Control

Users: Read and Special

  • Click Advanced, and, if asked, accept the User Account Control (UAC)elevation prompt.
  • Click the Owner tab, select Administrators, and click Edit.
  • Select Replace Owner on Subcontainers and Objects. Click Apply, and then click OK.
  • Click the Permissions tab and click Change Permissions.
  • Select Replace all Child Object Permissions with Inheritable Permissions from this Object. Click OK, and then click Yes.
  • Click OK, and then click OK again in the Windows Security dialog box. Click OK to close the Advanced Security Settings dialog box.

Suggestion 2: Rename the SLCache folder and re-launch Lightroom 5.5

We are tracking this Lightroom issue. Please let me know which solution resolved your issue.

If these solutions did not work resolve the problem for you, let us know.

Thanks

Scott

46 replies

Participant
December 16, 2016

This doesn't seem to work for Lightroom CC and a Mac Sierra 10.12.1 - I have uninstalled and reinstalled and rebooted. I don't have the options above as my version of MacOS is not allowing for those instructions. Can anyone help. I have 21 days left on my trial, and now I'm thinking this will happen on my Mac if I pay for it. It's been a big waste of time.

Participant
February 3, 2016

I'm having a similiar Problem with LR 6 - it's a standalone I've had it 6 months and now suddenly the developer mode is deactivated and a message comes up that says they want me to register with the program with creative cloud; which I'm not interested in doing - first off; I paid for this programm I own the license,  secondly, the machine on which the program is running is offline; so don't understand what they want from me; I reinstalled the program and now see that they want me to activate the programm, by getting some code from somewhere; the orginal code has expired, but you can regenerate a new code what's good for 72 hours; the only problem is THAT DON'T WORK EITHER!!

are there any humans actually working for Adobe who you can talk to get any help on this???

Participant
December 28, 2015

I am also having this issue and get the message that the develop module is disabled!

Participant
December 27, 2015

I have the same issue. Any update?

natashas23262056
Participant
November 11, 2015

None of these solutions work for me. Nothing opens it.

Inspiring
November 11, 2015

LR 2015.2.1 on El Capitan Mac.

Perceived issue is different: no error message going to Develop module, but the cursor turned into a Light plus sign in a black square box and left a trail, the top part of the screen was light grey, the bottom black, and no controls visible.

Happened last week and I used solution 1, which fixed the problem until this week.

Tried solution 2 and it fixed the problem, although the Info screen did not have Admin rights shown. I just clicked the lock and clicked the checkbox that said apply this to all contents.

Good luck.

Participant
November 6, 2015

Im in trouble... having the same issue, already in November and cant fix this.. what a pitty.. can someone tell me if there has been a fix published???  thanks

Participant
January 20, 2015

I'm having exactly the same issue

Participant
January 7, 2015

I can't understand what's the problem!!!! 6 months later, the users don't have any good solution for this problem. In the last 4 days, I've tried every solutions that I could find and I can not use Lightroom. So, I am losing money.

If Adobe pays us for every minute of our time that we spend in trying to restore our Lightroom, I am sure Adobe hasn't enough money.

Please, I need a solution.

Participating Frequently
January 4, 2015

This is the reason everyone was scared to move to the cloud format.

As a professional photographer, I don't have time for this BS. I am on a work assignment in the US and have limited time to get this work to a client.  I have just encountered this same problem. If I don't make deadline, I will be sending adobe the bill for $2k for loss of income on the job plus loss of billable time on the next job I'm now unable to process.

You guys need to get your house in oder. It's issues like this that have the potential to ruin a brand completely.

This issue arose in June 2014 and 6 months later is still evidently occurring. That's unacceptable in any business.

Keith Reeder
Participating Frequently
January 4, 2015

jimmysalsa wrote:

This is the reason everyone was scared to move to the cloud format.

I didn't get the memo telling me you'd been elected to speak for "everyone".

The problem isn't with "the cloud format" - it's just a bug, and precisely nothing to do with "the cloud".