Having many hours of mind numbing experience with the Adobe authentication nightmare, it took me 5 minutes to fix on 2 of our 32 Macs here. Re-installing the apps themselves will do nothing as the autemtication folders are not altered when you do this. So, on a Mac: Log out of your Adobe CC account. Go to: /Library/Application Support/Adobe Rename SLStore folder to SLStore_OLD *IMPORTANT* Make a new, empty folder called SLStore (the reason you need to do this is because the Adobe authentication needs a folder called this to populate. Wihout it, you'll get a different error message). Restart your Mac. Log back into CC Cloud. Boot all your Adobe apps. Will take you under 5 minutes. ... View more

Amen brother!! I only bring it up to illustrate how far this actually goes back and all the billions of things that users have tried over the YEARS. And then to have yet another Adobe staff member come on and ask for more details! Just really sums up how much Adobe care about their customers, ie, either can't be bothered to read through the back posts or doesn't have the logic to prompt them to do so. Don't know which is worse. One thing for certain, the £1600+ subscription for our 32 licences never fails to be taken out of our bank account. Funny that isn't it? glad your login problem is solved. ... View more

This is a 184 post thread!! Just read back and you'll see EXACTLY the issue edwin is having. Actually, this resolution "Thank youchristo101. Your 9-step coup de grace technique worked! It was the only one that worked on my macbook - with every single software already being the latest version. I am surprised that this issue seems to be occurring even 4 years since it was posted about." was mine. (my solution at post 104 of this thread 104.). Glad some people are still finding it useful. It took me 3 weeks to work it out and it helps a lot of people. After spending 9 HOURS in online chats with Adobe (with no resolution at all), finally getting a solution myself was not as satisfying as it may seem. It's really because of replies like yours where previous posts have gone into minuscule details of their issue (it's a flowing evolving thread) but you ask for more info and regurgitate the same steps that were put forward over 4 years ago, none of which fix a very long-term, cross platform Adobe issue. ... View more

Try my solution at post 104 of this thread 104. I've done it on 24 Macs in our office and cured them of this..... affliction. Be careful of the cold boot. If you do a restart instead of a cold boot at that step, it won't fix it and you'll be back to square one. This is still a terrible, terrible bug that Adobe simply refuse to admit to. Our office is now paying over a grand a month to Adobe. Stuff like this shouldn't be happening and that's an understatement. My post is all I can do to help, I hope it does. Good luck. ... View more

If you're on a Mac try my solution at post #104 of this thread. It cured it for 28 macs in the office but at 30-45 minutes per machine it wasn't a quick fix. If you're on windows then I can't help you at all although my steps may help. Not that you or I, or any user, should be going to such lengths. I think Adobe have just buried their heads in the sand with this one. A deep coding error on authentication, affecting all platforms. My steps have worked with no re-occurrence of the issue. I hop they are of some help. Don't hold your breath waiting for Adobe. You'll suffocate. ... View more

Adobe answer only what they want to answer. They fix only what they want to fix. The only constant in Adobe life is that pin-point, never failing debit going out of your account every month. ... View more

It took me a long time to work that out. Glad it worked for you and I agree with every other forum poster with this horrendous issue. WE shouldn't be spending hours trying to fix Adobe authentication coding issues. Adobe help still insists that the first step is to uninstall and re-install the APPS. This does nothing but waste your time. The fault is in the authentication code and authentication apps not the apps themselves. Can't believe, after all this time, they are still telling people to do that. We have 39 licenses here and we were having this with about 28 of the machines. My method solved it in all cases but at 30 to 45 minutes per machine…. Adobe owe me lots of what they love most. Money. ... View more

Floramc, As I've said quite a few times now, I have no issue at all with the wonderful volunteers. You keep explaining about volunteers and their role in the forums. I know all this and have no issue with the great help you provide. I didn't say or mean Adobe should say sorry for their subscription model. I said that they should say sorry for me having to spend 38 work hours figuring out a solution to this particular bug then a further 30-45 minutes per machine implementing the fix. That's a lot of company time and expense. I also understand you went as high as you could with Adobe. So did I. But Adobe, the people who code this stuff, didn't come up with the (or a fix). Again, I had to do this myself. I am grateful that you tried to help, I really am, but this is the 3rd major bug I have had to fix myself without even an acknowledgement from Adobe that the bugs even existed. Adobe is not a charity. It is a multinational, multimillion dollar company and although I like the forum a lot (and contribute any info I discover to try and help others) Adobe shouldn't rely on either volunteers or discussion participants to come up with solutions to serious issues and bugs, because that is what they are doing. If I could find the fix why couldn't the coders? I am not a coder. It looks as though the forum (i.e. volunteers and ordinary members) are now solving most of the issues that Adobe are not even acknowledging but where do I get back those 38 hours? How do I justify it to the people who pay my wage? Interestingly enough, in 2014 Adobe's profit (profit not turnover) went up to $88.5 million from $76.5 million over the previous year on an increase (5.7%) revenue of $1.07 billion. That makes the 38 hours I spent to get their software to work properly on our machines a real kick in the teeth because I too work for a company that need to make a profit not waste a week getting authorisation code to work properly. And for the subscription model, all I'm saying is that there should be a choice. Subscription suits some users, perpetual licences suit others. That's all. And it wasn't a change in the market that led to Adobe's subscription only model. It was a decision in the board room based on profit forecast. Having no choice does not constitute a change in the market. Even Microsoft, who offer 365 subscription for their Office suite also offer perpetual licences for it as well. They let the user choose what suits them best so although a lot of companies are offering subscription methods there are not many that offer only that method without choice. That is my point. ... View more

As I've said before, the volunteers on this forum, including yourself, are great. But in MY experience and in a lot of other peoples experience (just reading through these forums), Adobe, as a company do not care about the customer. It was Adobe who completely removed the option of a perpetual licence for people who suited that work method (i.e. people who would upgrade in 3 yearly cycles). No one made Adobe do this. They decided to do it despite a lot of very good reasons put forward of why different options suited different situations. Of course companies are moving over to this, it is a perpetual revenue stream and this does not suit all situations. Has it really come to the point where volunteers and ordinary members of a forum fixing the majority of the bugs has become acceptable? Adobe doesn't even recognise half the stuff hundreds and hundreds of users are reporting as even being bugs. We pay every month and we are also beta testers and now we're doing in-depth bug fixes for things that are not even connected with the software (i.e. authorisation bugs). No refunds, no apologies (official apologies) but I notice the monthly payments are taken bang on date every month. If that's not a definition of not caring about the customer then I don't know what is. At the end of the day it is incidental if Adobe actually care about their customers or not. What matters is if, from the customers point of view, they appear not to care and they certainly don't appear to care. ... View more

Can't help with why this is happening but the reason is because Adobe no longer give a stuff about their customers. They only care about getting and holding onto a constant revenue stream (i.e. CC subscription). My only guess is that there is still a background process and/or startup procedure still present and running that is calling the cloud service for authorisation. What platform/OS are you running? ... View more

Hey vanselman, I completely sympathise with your situation. Went through a lot of denials with Adobe. I'm not familiar enough with the Windows system to identify the files you need to delete but I will try to gain access to a Windows machine here so that I can maybe do a similar walkthrough to the solution I found for the Macs. As you have found out, and are correct; the following things do nothing to help this situation. So... Don't uninstall - reinstall you apps. This has nothing to do with it at all and is just a waste of time. Don't make a new user. Although this will delete some files that need to be gone, unless all are deleted (and a lot are not at the user level) it won't fix it. Has nothing at all to do with any browser setting or file/folder permissions. Once this starts happening on your system a CC Desktop app update will not cure it, it has gone deeper than that as my post above illustrates. Certain background processes need to be killed before you begin. Through task manager, kill all of these (hoping they show up in task manager) First quit out of the CC Desktop app then in task manager, kill: Core Sync   AdobeIPCBroker   Creative Cloud   CCLibrary   Adobe Desktop Source   Adobe Installer *And anything else you see with Adobe at the front* *Do Core Sync and AdobeIPCBroker first to stop anything else re-spawning* When all the processes are killed you should be able to move/delete any file you want. I'll see what I can do but if you can follow and find the equivalent files/folders as in my Mac fix above it may just work. I agree, this is a bigger problem than Adobe give credit for and they seem to have no idea how disruptive this is. ... View more

OK, here’s how I fixed it on Mac 10.9.5. For this issue there is no need to uninstall your actual apps. If Adobe tell you to completely uninstall your apps for this authorisation issue don’t bother doing it. It’s a complete waste of time. This has nothing to do with the apps themselves just all the authorisation stuff. 1. Log out of your CC Desktop Control Panel 2. Quit all Adobe apps 3. Go to Activity Monitor (Applications/Utilities) and quit out of:   Core Sync   AdobeIPCBroker   Creative Cloud   CCLibrary   Adobe Desktop Source   Adobe Installer *And anything else you see with Adobe at the front* *Do Core Sync and AdobeIPCBroker first to stop anything else re-spawning* 4.Rename to _OLD or delete if you’re brave: ~/Library/Application Support/Adobe/OOBE /Library/Application Support/Adobe/OOBE Delete ~/Library/Application Support/Adobe/AAMUpdater /Library/Application Support/Adobe/AAMUpdater /Library/Application Support/Adobe/AdobeApplicationManager /Applications/Utilities/Adobe Application Manager /Applications/Utilities/Adobe Creative Cloud 5. RENAME /Library/Application Support/Adobe/SLCache to SLCache_OLD /Library/Application Support/Adobe/SLStore to SLStore_OLD IMPORTANT - On earlier OS’s you can just rename and new SLCache and SLStore folders will be made automatically. This doesn’t work on 10.9.5 so you have to make new, empty SLCache and SLStore folders which will get populated. So… Make new, empty SLCache and SLStore folders. They’ll end up sitting right above the _OLD ones. When I deleted the folders entirely InDesign decided it wasn’t authorised anymore! 6. Download the CC Desktop Control panel app and install it but don’t sign in yet or boot any Adobe app. 7. Shutdown your machine. We need to do a cold boot here, not a restart. 8. Once your machine has rebooted sign into the CC Control panel. 9. Run your Adobe apps. Hopefully, and I’ve done this on 10 machines now, you won’t constantly keep being asked to sign in every time you boot an Adobe app. I would not like to thank Adobe for any of this extra work and headache. Thanks floramc but I don't believe Adobe will ever fix this for people who already have this issue. This is the last machine here showing this symptom. If any others pop up I'm just going to smash them to tiny tiny pieces with a gigantic sledge hammer. ... View more

Creative Cloud control panel update this morning. Lots of bug fixes...... On booting of very app, every time..... still being asked to sign in despite already being signed in. I come to the conclusion that on machines that are already showing this behaviour, a control panel update is not going to fix it. Only a lengthy, in-depth hit and miss tour of your system by the user will eventually do it and hopefully (fingers crossed) it will stay fixed. One more machine to do here (in this 30 license studio), and it's the machine I use. I just can't bring myself to plough through it all again. Maybe in a week or so. ... View more

And on Mac: /Users/<your username>/Library/Application Support/Adobe/OOBE ... View more

‌Actually, this is a way better and satisfying answer. I heartily agree. ... View more

If you're on a Mac open Activity Monitor (in HD - Applications - Utilities) and quit: Core Sync Adobe CEF Helper Creative Cloud Adobe Desktop Service Adobe IPCBroker Then try trashing your Opm.db ... View more

Hi floramc, I don't want you to confuse rudeness with arrogance. He wasn't rude. When a lot of users are experiencing the same thing and a user finds a solution that works for all concerned and a Staff member flatly refuses to even contemplate that things could even happen that way, to me, that is arrogance. The solution cured this issue for a lot of users and I was merely enquiring if there was a similar thing to fix Photoshop 2014 running on the same OS. For all concerned it only occurred and affected Adobe ID, PS and IL 2014 and it came about when those 3 apps were released and when they called certain routines. The Staff member blames an OS issue but all 3 of those apps are specced to work on 10.7.5. Because he pretty much refused to look beyond the fact that a lot of users were experiencing the same thing, and found relief in the same cure, is what I would class as arrogance. I don't, for a second, rule out that it's something on the OS level which is why I said in the thread it shouldn't be specced to run on 10.7.5. because no other app (including the non 2014 Adobe apps) was causing such a freeze. I think I was being pretty fair with some fair questions. The replies are all pretty much 'it cannot happen that way', but somehow, it was, for a lot of users. I don't doubt the skill of the engineer at all but one thing has nothing to do with another. All any of us (users) were trying to do, and continue to do, is to get the software working. The basic definition of a problem is that something is happening that should not be happening and the causes are often things that should have nothing to do with the problem. That's their very nature and to properly and logically get to the bottom of an issue one has to be prepared to investigate all avenues. Simply saying it cannot happen that way is arrogant, in my opinion. As always I appreciate your replies ... View more

Hi floramc Here is a fantastic example of what I would call Adobe Staff arrogance... October 6 updated freezes my Mac Read the whole thread, I come in with what I think are some valid points about half way through. I still have this issue on 1 of our machines but hopefully that machine will be retired soon. I don't want you to do anything with this except to read it and see the total blinkered and unmoving responses from a Staff member. We didn't solve it but at least the phone support people could duplicate it which does go a tiny way in indicating that I was on the right track and I did have a valid point backed up with research and experimentation. Thanks for your help. ... View more

Hi floramc. Many thanks for your interest, and it is very much appreciated, but you are making my point. After going through 9 assistants, being passed from one to the other, I shouldn't need you to reach the chiefs of support for me. I should have already been put through and the issue officially admitted to or dealt with. There were a few mail addresses I had and eventually one of them replied and after a bit of haggling gave the company I work for a 15 day discount for ONE of the (30) licences. That was pathetic, it cost the company I work for way way more than this in hours troubleshooting just online with Adobe. It just goes to show how much Adobe do not care about their customers. At this point I had no solution at all to any of my issues. The fact that I have another 5 of our 30 licences doing this too, they don't seem to care about. It happens when I update the CC app, so I've stopped doing this so that no more machines get caught in this annoying loop. I have had consistent unacceptable support from Adobe right down to them giving me the 'freephone' UK tech support number. Although it wasn't freephone. It was national call rate. When I pointed this out they said it was the only number they had. They couldn't answer why they were telling me it was a freephone number when it clearly was not. They were also deaf to the fact that despite paying a grand a month I was now expected to pay to phone tech support too. This is when I was pointed to web chat help and what I now refer to as the spiral of support hell. The guys who cough up the money are already pretty angry at the amount of time I have had to spend to try and get this stuff working, and I don't blame them. It cost us £24000 in the initial upgrades for machines and licenses in the first year to move from a very stable perpetual licence system with the assurance that all licensing would be completely seamless. These forums attest that this is not the case and until Adobe fix this properly I am sick and tired of going back and forth with a corporate brick wall - I do actually have work to do. We're running Macs from 10.7.5 to 10.10.3 and Windows machines from Windows 7 to Windows 8 and all flavours are affected. As I said in an earlier post I have various methods that I have come up with myself to help deal with this but you can't do the same thing on 10.7.5 that you do on 10.10.3. Deleting a file as told by an Adobe employee rendered InDesign to say it was no longer licensed and it took me a day to fix that. Uninstalling and re-installin InDesign did not fix it. Again it was the authentication system. The assistant said it may be our network even after I pointed out that Photoshop and Illustrator were booting and authenticating on the same machine. Ground hog day. I could type on for an hour or two… but I won't. I really do appreciate your concern but they don't care and I have got the machines to the point where they can do the work, which is the point. I wanted to post here so that other people would know, despite what Adobe tell them, they are not alone in experiencing this. Many thanks again ... View more

No, not people from this forum, not the great volunteers, I should have made that clearer. It was official employees of Adobe I was speaking to through chat who gave me their mail address when I said I really had to go after hours and hours in the same chat session. I emailed them several times across 2 weeks. I was worried that when I continued fault finding I'd have to start all over again when contacting chat support and having to re-live the whole thing over and over, like ground hog day. Which, funnily enough, is exactly what happened. ... View more

I don't believe that Adobe are upsetting people on purpose and I also don't believe it is an 'evil plan'. What it is, is poor programming and implementation. I was in an online chat for 6 hours with this constant licensing issue and got passed through 9 assistants. Yes, 9. Each one, without fail asked "Hello, what is the issue?". None of them read the thread of the text and after hour 4 I got angry at having to explain what the issue was from scratch every time. There was no solution found during this chat and each person stated they would pass me to a higher level of support. We're paying nearly £1000 per month for our 30 licenses and after 6 hours I'm not at the top level of support? I have found various ways around this but they take ME (not Adobe) 30 to 45 minutes to implement. We have 30 users. And it's a grand a month. When we used perpetual licenses with serial numbers we never ever had a problem. This is beyond a joke and I shouldn't need to even clean caches or change permissions or manually delete files to make the software work and keep it working. It's a joke and Adobe should be thoroughly ashamed of themselves. Plus, when an Adobe helper gives you their email address and asks you to mail them it would help if they ever replied or got back to you. It's rude, arrogant and unprofessional but I notice they still take their money bang on time every month without fail. It needs to be fixed in the code and Adobe need to compensate users for wasting enormous amounts of time to make their hired software work properly. Adobe designed and coded the system. Fixt it, or at least admit you have no clue what is going on. Then fix it. ... View more