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

Sep 24, 2016 10:28 AM in response to robertk1

WOW oh WOW oh WOW! Like others, I want to THANK YOU so much for this info, Robert. I'm back to work, with a fraction of the effort it took the last time I had this problem (on a different iMac). I was able to SSH in to my sick iMac and used Terminal to rename the .cstore files.


One question ... is it possible to string ("pipe") the find and delete ("rm") or rename ("mv") commands together in one command, so that it is not necessary to copy the list of found files to a text editor and delete or rename them one at a time?


One comment ... I didn't get a consistent set of .cstore files. At first, I had perhaps 30 of them, but then a second "find" (after renaming only a couple) found only a few. But I did rename those (to .backup) and VOILA!


One other comment ... after logging out of the guest user and logging in to my actual username, it was as if OS X was resetting up my username. It said "Welcome", then asked me to go through (some of) the steps of installation (logging in to iCloud, allowing use of "Find My Mac", etc.).


After all this, I'm a bit reluctant to upgrade to Sierra, so I'll give it a few weeks before I do.


But again, THANK YOU!!!

Sep 27, 2016 2:40 AM in response to kenfrompark city

OS X will put you through initial steps similar to when you first started your Mac (not all steps). In particular many security updates will require you to input your icloud id, passcode, and confirm if "B2MM" should be active. The B2MM is so that sharing keys for B2MM can be generated that correspond to the new OS Version. The icloud ID - passcode likewise is to unlock keychain which is secured prior to upgrade of particular OS segments.

Oct 1, 2016 8:08 PM in response to robertk1

Well, it happened to me with new MAC OS Sierra. After update from El Capitan, I just type the password and stuck at login... But unfortunately my guest account was disabled for security reasons...

The good thing is my OS was running from an USB 3 HDD and I opened it from my another mac and did remove com.apple.LaunchService-whatever.csstore I manually found.

To enable hidden files to show up, I did those commands at terminal:


>sudo myusername

>defaults write com.apple.finder AppleShowAllFiles YES

>killall Finder


And boot it again and magically problem was solved.

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.

Jan 19, 2017 2:09 AM in response to robertk1

Robertk1,

Your absolutely straight forward guidelines work seamlessly and correct the issue even on 10.11.6.

The latest Security Update 2016-003 Supplemental Update gave me a hard time yesterday afternoon, letting me wonder about what's next, since no other solution could make me login into my account.

I left the office troubled but relieved, since I saw I could login with the root account I had well before activated, and was also able to create a new account that worked perfectly.


Today, I tried to lean on the Onyx solution but felt once more helpless after the respective rebuild that was mentioned above, proved unsuccessful in letting me in


After that, I restarted (once more...) and used the Terminal to enter the proposed commands and backed up the files found.


Restarted and violá! A happy Mac user again, greeting Robert and this wonderful community!

Feb 2, 2017 6:43 PM in response to robertk1

Solid thanks mate!

I'm running a mbp 17" early 2011 and was presented with this problem after updating to el captain os x 10.11.6

after a few unsuccessful tries via the terminal recovery mode, I started working through the single user mode (cmd-s on startup), followed your steps, and after a few attempts it finally worked and booted successfully.


for some reason, you have to trust that the path is being type, because it too long for the prompt. also you have to mount the disk and make it writeable, however those commands are included when you first boot in single user mode.


thanks again!

Feb 9, 2017 4:14 AM in response to robertk1

I recently had this problem too. On my MacBook Pro, I was updating it. I had MacOS Sierra beta but not the real one. On the startup screen (white background, gray apple logo), it was stuck at a very low percentage, I let it sit for 5 minutes, and that was it! I was very happy. However, when I went to login as admin, I just had a loading bar. I simply just waited for a while and everything was back!

Mar 7, 2017 3:08 AM in response to robertk1

ok so only 160 other folk have this question as well !!


Many , many thanks for posting this. Your solution worked for me using Terminal in Restore mode. The only addition, mentioned amongst these posts, is that I had to do the "find" on "/Volumes/MyHardDiskName/private/var/folders" ..etc..etc, even though I was doing this on internal hard drive. This revealed ALL of the .csstore files. (if I did the find on /private/var/folders - only one .csstore file showed up).


Never usually play around in this much Unix - many thanks again.


I only did a "recommended" Security update to El Capitan..............will I dare do another one !?

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

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.