You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Fix for El Capitan stuck at login

Last month I updated to 10.11.1 and my system would no longer log in. I would enter my password correctly and then the cursor would change to the spinning pinwheel and just sit there forever. The only way out was a power off reboot. I later found that when it was in this state I could SSH into it from another machine, and the system log revealed that /usr/libexec/lsd (the Launch Services Daemon) was crashing repeatedly. I searched these forums and others and found lots of ideas, none of which helped.


No problem, though, I've got hourly time machine backups, right? Well, no. Apparently El Capitan had not been doing the hourly backups so my most recent backup was from sometime in October, which was a month old at the time. Not good.


Fortunately, I had an older boot drive that I put in an external enclosure and was able to boot from that to experiment. The drive I normally boot from was fine -- permission checks and disk repair and all that all came back good, and I could read and write files to it just fine.


After lots of experimentation and frustration I was just about to give up and add another drive to do a clean install and start moving everything over -- a process that I *really* hate doing. But one last web search and a bit of luck gave my one last shot at fixing it.


To do this, you'll either need to be in a recovery console, or ssh into the machine, or boot from an external drive, or otherwise somehow get to a command prompt. Once you are there, do this:


find /private/var/folders/ | grep com.apple.LaunchServices | grep csstore


Note that if you boot from an external drive, you need to run that command against the boot drive you are trying to fix. Just add the /Volumes/Whatever_Your_Boot_Drive_is to the path, like so:


find /Volumes/YourBootDriveHere/private/var/folders/ | grep com.apple.LaunchServices | grep csstore


That will find the cache databases that Launch Services is using. They will have long and random-looking names that end in csstor. Make a note of every file shown, then delete them, by a command like this (obviously using whatever paths the above command found instead of this example):


rm /private/var/folders/cd/someLongRandomNameHere/someFolderNumberHere/com.apple.L aunchService-whatever.csstore


If you're more cautious, you can rename them instead of deleting them, so you can put them back if necessary. That would look like this:


mv /full/path/like/shown/above/to/whatever.cssstore /full/path/like/shown/above/to/whatever.csstore.backup


After removing or renaming those files, restart your Mac. You should now be able to log in. Or at least, that's what finally worked for me. The login did take longer than normal -- a few minutes -- to rebuild those files, but the desktop finally appeared, and now I'm back to running on my normal boot drive.


Hopefully this helps someone.

Mac Pro, OS X El Capitan (10.11.2)

Posted on Dec 13, 2015 3:47 AM

Reply
123 replies

Mar 26, 2016 1:39 PM in response to robertk1

Cheers +1. Worked for as me well going from 10.11.3 to 10.11.4. I was pulling out what little hair I have left thinking I was looking at a full system restore.


Just a quick note of thanks for taking the time to document the problem and solution. It came up basically as the number 1 hit in Google. You saved me hours and hours of time and frustration.


🙂

May 3, 2016 9:27 PM in response to robertk1

So awesome. I was down for a week after the update to 10.11.4 and had already reinstalled El Crapitan before I found this - that did NOT work, BTW. Tried many other useless things, like booting into safe mode. (crap, it won't let me type now unless bold or italics are on)

This fix worked first time. I read so many otherthreads that were no help. Boy has Apple lost their touch

May 17, 2016 12:08 PM in response to robertk1

I had the same problem after upgrading to 10.11.5 and your procedure fixed the problem. You can also do it if there's another account on the machine that can still be logged into. If you want to do it from another account, you'll probably need to prefix each of those commands with sudo to override permission problems (e.g., "sudo find ...", "sudo rm ...").


Thank you for the solution to this problem!

May 24, 2016 1:43 PM in response to robertk1

I am a novice, at best, when it comes to Terminal. When I enter the command, I get the response of "no such file or directory". I feel like I'm entering the text after /folders/ wrong. Can anyone help? Is there a space and then the letter "I" or is that a vertical slash, or something else? I've tried it both ways, but I still get the same error.

I Wish I could just copy/paste but the computer with the problems isn't working, obviously.


Thanks in advance.

May 24, 2016 2:24 PM in response to Joel Smith2

i'm also a novice but with some patience worked it out. copy and paste this line 'as is' into terminal and enter:


sudo find /private/var/folders/ | grep com.apple.LaunchServices | grep csstore


copy the list that is revealed in terminal into textedit, then copy and paste the line below into terminal, copy each line from textedit (one at a time) and paste directly after sudo rm / and run each line one at a time.

sudo rm /

example:

sudo rm /private/var/folders/cd/blahblahblah/blahblahblah.csstore

May 25, 2016 3:51 AM in response to hijoncon

Thanks hijoncon for this summary and alternative option. This is the one that worked perfectly for me!

I have got this problem with El Capital 10.11.5.

Fortunatly for me Guest user was still functional so I was able to execute the procedure that, as I said, worked like charm.

Amazing that Apple is not able to address this issue after more than two years!!


Thanks again to all the community.

elchurles

May 25, 2016 10:36 AM in response to pwp69

Thanks, pwp69, your "patience" suggestion helped. I finally figured out that since my boot drive has spaces in it's name, "Mac Pro 3 HD" I have to use the backslash and a 'space' when typing the 'space' into Terminal. /Mac\ Pro\ 3\ HD/

Unfortunately, it didn't help my situation. I ended up installing a fresh copy of El Capitan on a new drive and starting from scratch.


And SimonAntony, thanks for the 'pipe' character clarification. Now I know for next time.



Joel

Jul 19, 2016 7:03 PM in response to robertk1

Updating from 10.11.4 to 5/6


Wahoo! After four days and two visits to the genius bar I also was about to dredge through a manual recover. I am hugely relieved to have found your post.


It appears that the Utilities option in the command R recover window has been removed. I could not access terminal in this window. However, I was lucky to have a workable guest account so I opened terminal and SU'd to my main user account and sudo'd the csstore files as you suggested. Yeah

Fix for El Capitan stuck at login

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.