Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

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

Oct 12, 2016 6:47 AM in response to robertk1

Here's another way to do the search for the .csstore files to check them before deleting - making use of the find command without an additional pipe to grep for the filtering:


cd /private/var/folders

sudo find . -name '*.csstore' -exec ls -l {} \;

Then to turn it into a delete command:

sudo find . -name '*.csstore' -exec rm {} \;

Be careful with the syntax. If the search term after the '-name' parameter is wonky you can easily do collateral damage.

This fix didn't work for me though; I believe I have something else going on besides launch services.

Oct 26, 2016 10:29 AM in response to robertk1

My El Cap problem started when I changed the user name that I set when I first began using my mid-2013 MBA. The user name change when fine (i.e. I could login and logout using the changed user name) until I applied a security update from Apple. On restart from the security update, I would only get a grey screen with a pointer (i.e. no login icons). Fortunately, I was able to get to a login icon screen using Safe Mode. Fortunately as well, I still had the user account that I created to change the user name that I set when I first began using the MBA. At safe mode login screen, I could log into the that newly created user account, just like it was a Guest account, as suggested by hijoncon. (At the safe mode login screen, I could enter the password for the changed user name, but I'd only get a non-beachball spinner.) Once in the new user account, I launched Terminal and followed hijoncon's steps. I got three file names returned using the sudo find command. I could rm one of them. When I tried to rm the other two, I got an overwrite? to which I typed y, and then got a "Don't have permissions." When I restarted, I could log in to the changed user name account with no problem. Apparently, using rm on the other two file names returned by sudo find was not necessary. Thanks to hijoncon.

Nov 21, 2016 10:43 AM in response to robertk1

The issues described are typically to do with the LaunchServices database; the manual methods here do work well but do require some more technical knowledge incase it all goes wrong.


I had this issue and quickly resolved this by running Onyx - http://www.titanium.free.fr/ - and running (under utilities) the LaunchService rebuild (and also fix your disk permissions while you're at it). This took about 10-15mins and all is now working as expected.

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 ID.