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

Aug 21, 2016 9:33 PM in response to robertk1

i'm having the same issue with 10.11.6 but deleting the launch file thing didn't help. I also tried reinstalling the OS to no avail. I can't even get to time machine in terminal. Getting the following error:

"-bash: tmutil: command not found".


i'd go to the Apple Store but my applecare just ran out at the end of July and I have the mid-2012 version so they'll likely charge me some ridiculous amount to get it fixed.


any ideas on what I can else I can do? Can't afford a new computer at the moment and even if I could, I can't even backup the latest stuff to time machine.


UPDATE: I gave up and decided to restore from my last backup (1 month ago) which was 10.11.5. Anything ive done since then should be pretty easy to recover/recreate. Hopefully this will fix it.


<Edited by Host>

Aug 22, 2016 7:28 AM in response to epr329

same issue here, still having issues here. HOWEVER you can still backup your files by starting in safe mode. restart computer holding down shift key. I did 2 backups one of just my stuff, video, pics, docs, etc AS well as a full backup. still trouble shooting not sure if it is a certain program causing the issue. I had a guy look at this weekend (8 years at Apple as genius). He believes my issue (since I have done all of the above) may be related to hardware issue. While at the moment I do no have full use of computer is safe mode I can access files and most programs.

Sep 7, 2016 11:28 PM in response to Steve Dutton

In my case I tracked it down to a piece of software I had installed that was not updated since Mavericks. I needed to continue to use it for some tasks (I already use Parallels for VM of Windows) so setup a OS X VM for the legacy programs that I still need but that don't have an update compatible with 10.11


I haven't had the issue since I updated, removed, or moved the software that was out of date to a VM.

Sep 16, 2016 7:55 PM in response to robertk1

When you say casually "I hope this helps someone" you are being the Master of the Understatement. I swear that if you were in the same room as me right now I'd hug you. I've spent four hours trying to solve this issue, and was on the verge of a clean install when I found your post. You are a goddam GENIUS - and a generous one too. Thanks so much...

Sep 18, 2016 2:36 AM in response to robertk1

thanks robertk1!!


gosh! tried to run disk utility in recovery mode, safe boot the mac, file system consistency checks.. all up to no effects. was about to restore the mac from previous backups until i stumbled on this post. thanks again for sharing and u just save my 'life', literally 😁😁..


the reply from @hijoncon is helpful too.. =D

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.

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.