We've learned this morning that a backend problem has been identified for customers who had purchased the PS/LR bundle in the last few months which is blocking use of the Lightroom subscription build. Once fixed, signing out and back in from the Creative Cloud app should work, but I think it's still being worked on. Will update the thread as I have more info.

Thanks for the update.

Does this also effect the use of the 'Edit in" function? I had to replace my CC LR 5.5 installs with the standalone downloadable, even once I got them to launch because 'Edit in' was not showing in the context menu. Same issue on both macs.

John

I am not of the "Last few months" variety. I owed LR 5 before subscribing to the Photoshop only thingie a solid year ago. Later, it was upgraded to the PS/LR bundle. But the build was still screwed.

John, I'm not certain whether the missing 'Edit in' function was tied to this, but I suspect it was. Please continue using the standalone version if that is working for you.

Thanks for the add'l info, oldbalddude (I like your handle). Customers who were upgraded from PS to PS/LR are a specific category we are trying to fix.

Same situation here, was LR5 Perpetual + PS CC, upgraded to the photography program.

John

I'm having the same problem as oldbalddude. Like him, I originally owned the standalone version of Lightroom 5, and later subscribed to the Photoshop/Lightroom Creative Photography bundle. (Like him, I am also an old bald dude, but I think that's probably not relevant to this issue).

I upgraded Lightroom 5 yesterday through the Creative Cloud application. Since then, I have been unable to launch Lightroom. The splash screen appears for a moment, and then the application quits.

Output in the console says:

6/20/14 11:10:11.236 AM Adobe Photoshop Lightroom 5[1156]: Cannot add package named WFCoreTests

Looked in /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFCoreTests.f ramework, /Applications/Adobe Photoshop Lightroom 5.app/WFCoreTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFCoreTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFCoreTests.a gtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/WFCoreTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFCoreTests.agtoolkit

!! Did you remember to add a copy frameworks step to your project?

6/20/14 11:10:11.000 AM kernel[0]: CODE SIGNING: cs_invalid_page(0x100000000): p=1158[AdobeCrashDaemon] clearing CS_VALID

6/20/14 11:10:11.237 AM Adobe Photoshop Lightroom 5[1156]: Cannot add package named WFSQLiteTests

Looked in /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFSQLiteTests .framework, /Applications/Adobe Photoshop Lightroom 5.app/WFSQLiteTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFSQLiteTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFSQLiteTests .agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/WFSQLiteTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFSQLiteTests.agtoolkit

!! Did you remember to add a copy frameworks step to your project?

6/20/14 11:10:11.238 AM Adobe Photoshop Lightroom 5[1156]: Cannot add package named WFWebTests

Looked in /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFWebTests.fr amework, /Applications/Adobe Photoshop Lightroom 5.app/WFWebTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFWebTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFWebTests.ag toolkit, /Applications/Adobe Photoshop Lightroom 5.app/WFWebTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFWebTests.agtoolkit

!! Did you remember to add a copy frameworks step to your project?

6/20/14 11:10:11.239 AM Adobe Photoshop Lightroom 5[1156]: Cannot add package named WFOzClientTests

Looked in /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFOzClientTes ts.framework, /Applications/Adobe Photoshop Lightroom 5.app/WFOzClientTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFOzClientTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFOzClientTes ts.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/WFOzClientTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFOzClientTests.agtoolkit

!! Did you remember to add a copy frameworks step to your project?

I tried the fix described at Not able to launch Lightroom after updating it to 5.5 from Creative Cloud but this did not resolve the issue.

I also removed the only third-party plugin that I have, but this did not resolve the issue either.

For the time being, I'm going to try going back to the standalone version and using my old Lightroom 5 license key.

Addendum to above: this occurs on OS X 10.8.5 running on a MacBook Pro with 8GB of RAM.

In a related thread, Re: Re: I cannot open Lightroom 5., one user suggests renaming the SLStore folder (which, on a Mac can be found at '/Library/Application Support/Adobe/SLStore').

I tried this, and Lightroom prompted me to sign in to Creative Cloud to authorize the application. It then started up successfully and, as far as I can tell, is working correctly. The process also created a new SLStore folder.

So this may be a possible fix for the issue, although there is a risk that it could cause other problems down the line. Make sure to rename, not delete your SLStore folder, so that you can go back if necessary.

That worked on one of my machines, but not the other (both OSX - go figure!). And once working, both LR installations were missing the 'Edit in' context menu (which I use a LOT to send images to PS, nik collection etc.)..... installing the offline LR5.5 fixed that for me.

Lord, just getting around to trying to fix it now? Been a mess from day one.

The workaround to rename the folder worked but only half-way.

I signed out, restarted CC Desktop, moved the folders (both SLStore and SLCache), then started LR.

It prompted me to sign in. As soon as I did, LR started, and all was happy for a moment.

Then I closed LR and started it again. As soon as I did:

... "Develop module is disabled. Please renew your membership to reactivate the Develop module".

This is funny. Every time I remove the SLStore folder and re-activate, it works perfectly until I restart it.

The next time I start LR, it says, "Develop module is disabled..."

I do have a current subscription to Photography Program (PS + LR) and PS is working fine as far as I can tell.

Ok, so the following sequence of steps, mentioned in another thread, but slightly modified by me, worked for me.

1. Sign out from CC. I opened PS, then from Help menu selected "Sign out". It prompted me to confirm that this will remove licenses for PS and LR.

2. Quit from CC Desktop (Command+Q, not just close the window. Make sure CC Desktop icon is no longer shown on the menu bar.

3. Uninstall LR from Applications in Finder and clear out the Trash.

4. Remove the SLStore and SLCache folders from /Library/Application Support/Adobe/. I had those two folders backed up just in case.

5. Restart the computer.

6. CC Desktop loads automatically on startup. Click its icon and sign it to your CC account.

7. Install LR from CC Desktop.

8. Launch LR.

LR started with no problems and Develop module is functional.

Edit In... menu shows Photoshop CC (2014) menu item as expected.

PS 2014 starts up fine as well.

Hope this helps.

Thanks, Maksim. I'm being told the key step here is to sign out and then sign back in.

For those of you still having problems, either with the app not launching or getting blocked from Develop when you have a valid subscription, please try signing out from the Creative Cloud desktop app, then sign back in. If you are still blocked, reply here and I may need to follow up with you privately.

Just got a call back from Adobe wanting to help fix the problems they created. Told him I had already fixed it, sort of on my own. He gave me his name and supposedly will hep me personally if I have problems in the future. His listening skills suggest to me that he will be as inept as all of the other support people. But, I do have his name. He told me that the issue has been resolved for "many" people with solutions they have come up with. Not resolved for everyone, though. He asked if he could close my case since I have resolved the issue for myself. I told him he could do what he wanted, but that the real issue is a management issue and the only person I really wanted to speak to at this point was the CEO of Adobe. Suspect he won't call me, but in truth, he is the only person who is in a position to kick the butts of the development & support teams and get them up to snuff which they currently are not. These are supposedly professional level software products, and professionals can't afford to lose days of work due to developer/support inadequacies. I would still like to speak to the Adobe CEO to let him know what a mess his people are creating for users.

Julie,

I have tried various combinations of sign-out and reinstall, as well as moving around SLStore and SLCache folders and none of these worked until reboot. The key step for me was sign out, and removing those two folders, followed by reboot. I have a hunch that it may be related to a CC process/service holding on to some cached copies of files in those folder which prevented complete cleanup. This would explain why uninstall, cleanup, and reboot followed by re-install helped. It is no more than a hunch, of course, purely from my s/w development background as I obviously don't have access to LR source code.

    == Maksim

I followed Maksim's steps (thank you very much) and all is working now, however after the first reboot and before reinstalling LR, my creative cloud desktop was blank (hung).

I signed in via photoshop and then rebooted again and all was well, I then reinstalled LR and now all is well. Thanks Maksim for sharing detailed info and thanks Adobe for getting

right on the problem.

I am glad it helped, Jeff. If enough people confirm that this workaround works, maybe helpful folks at Adobe can update the knowledge base article here https://helpx.adobe.com/lightroom/kb/unable-launch-lightroom-55.html to include these steps.

Good catch. I will ask for that page to be updated pronto.

Julie it did the trick for me (logging out and in Creative Cloud)

Now LR 5.5 starts

I will check later on if this survives a reboot

Hi Julie,

Just followed up and looked at the updated KB article here: https://helpx.adobe.com/lightroom/kb/unable-launch-lightroom-55.html

The article now suggests installing LR from stand-alone installer instead of CC.

I do not believe this is the workaround described in this thread.

Installing stand-alone LR will require perpetual license and a serial number which will not work for CC subscribers.

Am I missing something?

Thank you,

      == Maksim

My solution -- of renaming the SLStore file -- turns out to be a partial fix at best. After I restarted Lightroom, I got the dreaded "Develop is not licensed" message when I tried to use the Develop room.

I shut down Lightroom and Photoshop, logged out of Creative Cloud and then shut down the Creative Cloud application. Then I tried to restart Creative Cloud. It wouldn't launch at all, so I restarted the machine. Creative Cloud started up again after restart, but went into "ever-circling blue wait cursor" mode, so I can't log back in or do anything else with it.

Restarted Lightroom, which told me that I would need to log in. I logged in as instructed. Develop and other functionality is now working again. After restarting Lightroom a second time (just to make sure) I still have Develop functionality. I'm not confident that it will last indefinitely, though. The Creative Cloud application is still unusable.

Dear Adobe, please take note. This kind of nonsense is why people hate Digital Rights Management and subscription-based software. If your implementation is anything less than rock-solid, you end up with a user base of very angry users who can't understand why they can't use the software they paid for. And that's not a good thing.

Thanks for calling that out, Maksim. I've got some further questions out to our support people on that change.

Did not work for me! LR still crashing...

Please try the steps in this link. The steps has been updated.

https://helpx.adobe.com/lightroom/kb/unable-launch-lightroom-55.html

None of these 3 solutions worked for me. LR still crashing when installed via CCloud manager.

If I install a copy that I previously downloaded from the web, it works.

Adobe does not seem to know what they are doing. Not impressed.

Hi Maksim,

Could you please give the entire path where you find SLCache and SLStore? I'm lost here

Thanks

Hi Lio,

Sorry for the delay in responding to your message - I was out of town and traveling with no mobile connection.

The files are located in "/Library/Application Support/Adobe".

Maksim

Way to go Maksim! Adobe needs to pay you! The process you listed in post 92 in this thread worked perfectly! Adobe's band-aid of installing standalone is not why we pay for cloud applications. Thank you!!