Apple Event: May 7th at 7 am PT

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

Jan 23, 2016 3:14 AM in response to robertk1

Thanks for the detailed solution. I found this after I had done a complete reinstall / migration from a clone. Actually, this problem has occurred twice with me---when I updated to 10.11.2 and just recently with 10.11.3. After reinstalling, everything is running just fine now on my laptop, but I have a couple of questions:


1) Are those Launch Services Databases somehow damaged and I would do well to get rid of them now to preempt problems with the next update?


2) If so, is there a way to get to them using something like PathFinder (which shows invisible files) when up and running on my boot volume or must I login with one of my external clones?

Jan 24, 2016 8:58 PM in response to robertk1

I too have been having issues with booting into El Cap. The first time I migrated to 10.11 it hung in the gray zone during install but it went ok after booting into safe mode. Now after upgrading from 1011.2 to 10.11.3 I am having the same issue of hanging out in the "gray zone." I have been calling it that because I can hear the hard drive working so it sounds like if you are just patient it will finish.


As I found out that isn't the case and the guidance from Apple that it's a hardware driver problem isn't really accurate.


I was successful following YOUR WONDERFUL PROCESS... KUDOS 🙂 for discovering it and documenting the process so clearly. In my case I could get to single user mode but not safe boot. I did however have an old image of Mavericks that I had stored on a old laptop drive salvaged from my last windows machine (It committed suicide by flying off a 4th floor balcony to it's death.)


I was able to sign-on to the machine and could use a little copy-paste magic and automator (replacing the appropriate areas to search and remove the offending Launch Services Cache files. Shut down removed the backup image and booted into a working system.


As you said it does take a substantial time (I have a mid 2010 and it took a good 15-20 minutes for it to fully boot into the drive and to get to where I could navigate in El Cap. The rebuild of Launch Services, as well as El Cap doing a run through of all the programs and drivers installed. So about 5 minutes to get to the login window 5 minutes to get to the desktop and then 10 minutes I was looking at a El Cap desktop with no icons and nothing in the menubar except the apple icon in the top left, this felt painfully slow. Once it finished it got back to normal quickly and navigation was back to it's normal snappy self.


In response to Steve Dutton. I don't believe it's possible to correct these prior to the update as the launch services are being made untrusted/invalid by the update. Actually, it should have been a part of the install package to delete the launch services after the install completed, but prior to the final reboot. That would allow the launch services to be rebuilt based on the new OS install. Looking at logs it is most likely the security updates that Apple has been rolling out which are causing the services to be invalidated.


I have a feeling the headaches with this update are not over, there are a lot of processes and services that are listed in the logs as being voided, invalidated, and disabled. Fingers Crossed for everyone. (I'm holding on to the Mavericks Image, just in case) 😝


Thanks again to Robert!


---wb


"You must be the change you wish to see in the world." ~Gandhi

Jan 28, 2016 7:16 AM in response to robertk1

Thank you,


Today I updated to 10.11.3.

After getting stuck first at reboot (fixed with cold reboot and "option" at start up) and then

at login (spinning rainbow wheel), I followed the instructions and the problem is fixed.


Only 1:30hrs lost 😟 but multiply this by the number of Mac OS X user who will experience the same

problem and how many will not be able to find these instruction and you see what a problem

Apple has on their hands...

They really need to get their act together and restore the rock-solid stability of the OS.


cecosho

Feb 19, 2016 10:05 AM in response to robertk1

After over a week of grief trying to recover my iMac from a failed upgrade to El Capitan 10.11.3 (Some how trashed both my boot SSD and the external Carbon Copy Clone - I think the mains power went off for longer than my UPS lasted), I got to the point where I had done a clean install and restored from the Time Capsule Time Machine backup (That took two goes at 12 hours each!) and found I had the login hangup described here. I finally found this article and, joy of joys, its worked. If you are ever near Warwickshire, UK drop me a line and I'll buy you several beers!


N.B. it didn't work when I booted the iMac in single user mode. I could find all the .csstore files but when I tried to rm them I got a "Read-only file system" message. But it works fine booted from the Recovery portion and using Terminal from the Utilities menu - as described.

Mar 22, 2016 6:49 AM in response to robertk1

Thanks robertk1!


Same thing suddenly happened to me (after updating iTunes to 12.3.3, no idea if that's in any way related). Came back after lunch and couldn't login anymore.


Next to not being able to login, another thing that surprised me is that manpath wouldn't work anymore (stalled).


After removing all occurences of com.apple.LaunchServices-xxxxxx.csstore all is fine again.


Ernst.

Mar 22, 2016 8:10 PM in response to robertk1

Just updated to 10.11.4 . . . same exact beachball of death when logging in after the update. I removed three of the .csstore files and all was fine. This seems rather crazy. From .1 to .2, from .2 to .3, and now from .3 to .4, the computer becomes a brick after the update. My first two updates, I did complete reinstalls. Fortunately, i was able to use robertk1's fix on this last update.


There must be something unique on my system (and others) causing this problem.


Thanks for the fix!

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.