System wont boot after OS X 10.11.2 update

Running a MacBook Pro with Retina Display, 1TB SSD, 16GB RAM. Downloaded and installed the 10.11.2 update, upon restart the progress bar gets to about 3/4 of the way to completion then stops, leaving a black background with the white apple logo and the locked progress bar. Recloned my computer's hard drive off the backup I made prior to installing the update, booted the computer again, then tried to apply the update once more with the same result.

MacBook Pro with Retina display, OS X Yosemite (10.10.1), 16GB RAM

Posted on Dec 9, 2015 7:50 AM

Reply
46 replies

Dec 21, 2015 9:44 AM in response to gestler

Hi Gestler,


Thank you so much for your suggestions.


it is likely that the issue I had was related to Symantec end point protection that my company's IT had installed.

However, I have no way to disable the antivirus once I boot from external disk. My external disk is taking a long time to boot (I fear that the clone I made on my external disk is not good either).


if you have any pointers to selectively disable AV during boot up it will be good.


I Do know that the TM Back up of a couple months ago is working fine.


Cheers

Yogesh

Dec 21, 2015 10:20 AM in response to PrasadYR

Hi, PrasadYR,


I believe there are a couple of ways to do what you are attempting. First, though, I downloaded the MacOS 10.11.2 update to my backup hard drive (cloned from my internal drive using CarbonCopy Cloner) and booted from that drive. Then I simply went to the Norton Antivirus app in Applications / Symantec Solutions and opened the Norton AntiVirus app. Under "Automatic Protection" I clicked "Virus Protection" to turn it off. I restarted by holding down the option key and selecting my backup drive, installed the update, and when the computer booted off the backup drive with the 10.11.2 updated installed, I went back to Norton AntiVirus and turned the Virus Protection back on. Then I used CarbonCopy Cloner to clone the backup drive to my internal drive.


Another approach would have been to uninstall Norton AntiVirus from the backup drive, install the update on the backup drive, reinstall Norton and the clone the internal drive from the backup drive.


As to the questionable external disk you have, I suggest you boot from your internal drive, run Disk Utility/First Aid on the internal drive, then use Disk Utility to erase and reformat your external drive before cloning to it. This is a little dicey since it means that you only have one copy of your disk (i.e., the internal disk) until you complete the cloning process. So, if at all possible, borrow another external disk and clone your internal disk to it and keep that disk safe until you have completed the process with your original external disk. Once you've done everything, you can erase that second external disk and return it to the place from which you borrowed it.


Good luck.

Dec 22, 2015 7:03 AM in response to gestler

I have tried to perform the upgrade to 10.11.2 4-5 times now Macbook pro - late 2013. The boot fails in a very early stage. I could restore everything to 10.11.1 form the backup every time but it takes hours. I have disabled(removed) everything from StartupItems. That does not help either. The startup disk is sane and ok, but it looks as if there are some essential files missing from the boot area. I will try the suggestions cloning external disk ->upgrading that external disk -> booting from external disk and finally if everything is OK clone the external disk again to the startup disk. Or maybe apple releases a fix first? Where is the quality?

Dec 22, 2015 7:21 AM in response to beljake

beljake wrote:


I have tried to perform the upgrade to 10.11.2 4-5 times now Macbook pro - late 2013. The boot fails in a very early stage. I could restore everything to 10.11.1 form the backup every time but it takes hours. I have disabled(removed) everything from StartupItems. That does not help either. The startup disk is sane and ok, but it looks as if there are some essential files missing from the boot area. I will try the suggestions cloning external disk ->upgrading that external disk -> booting from external disk and finally if everything is OK clone the external disk again to the startup disk. Or maybe apple releases a fix first? Where is the quality?


If the install fails there is no guarantee that you arrived at a stable state, so restoring to a known good state seems to be appropriate.


Another good thing to try when there are problems with updating, is to use the "combo" update.

Actually, that is what I always do except for .1 updates. A 10.11.2 "combo" update includes everything to go from 10.11 or 10.11.1 to 10.11.2.


You can try downloading the combo and see if it works that way.


Download OS X El Capitan 10.11.2 Combo Update

Dec 22, 2015 7:58 AM in response to Luis Sequeira1

I tried the combo update twice but that did not make a difference. I also tried a fresh install of OS-X (that did not work either) Maybe a significant detail, my Retina display is broken and I can't see what is displayed on it (but booting command-R shows it content nicely on the other connected screens) If the boot process asks a question before the other screen-drivers are loaded it can't work.

Anyway the update process is visibly not working correctly. Not enough tested. I upgraded my macbook air without issues from 10.11.1 ro 10.11.2

Dec 25, 2015 11:48 AM in response to beljake

SUCCESS!!! FINALLY!!!


After being unable to install 10.11.1 or .2 (wouldn’t boot up), but sure that was due to some software incompatibility, I reformatted a big external volume and installed 10.11.2 successfully (no surprise), then repopulated it step by step, app by app, with all the stuff I use on my main (AirBook) drive (going from high-priority stuff like the MS Office and iWork suites, down to ever lower-priority stuff), with frequent cloning (to save what was good, and avoid a hung state) (yes, lots of time! 😟). One of the last apps was Kensington’s TrackballWorks 1.2.1 for Mac: BAM!!! No question about it. I removed the app and the associated .kext, and everything works fine. Actually, my trackball was misbehaving on and off since the initial 10.11, as if the pref pane had stopped registering the device; easy to correct, but unusual, and a pain.


This may not be the only SW causing the problem, and others may have other stuff, but I’m all OK now. It’s surprising that a big outfit like Kensington hasn’t updated their SW for El Capitan (it was issued June 22, 2015), but I hope they do so soon, because I really like their trackball.

Dec 25, 2015 2:12 PM in response to gbdoc

Perhaps what is causing so many aleatory problems for us trying to install the upgrade is what you just mentioned - incompatibility of one or more apps.

I think that when installing Yosemite apps that wouldn't be compatible where automatically dumped into an Yosemite-generated folder called "Not compatible software", and seems it avoided the hung state El Capitan is causing.

Wishful question : is there a way to anticipate what apps won't be compatible with El Capitan or the 10.11.2 and remove it before hand ?

Dec 25, 2015 3:50 PM in response to Mikile

I think there is are least some fair assumtions which might be useful - at least, that’s how I proceeded. The safest apps would likely be ones that Apple themselves had made; the iWork suite tops that list. Then come those that are so widely used that both Apple and the publishers are interested enough and have enough resources to make sure they’ll work, such as the MS Office Suite, and Skype. Dropbox and iPassword would be almost in the same league. After that, there’s a lot of guesswork and intuition involved, including your opinion of how widely an app is used, and whether the publisher has the resources (and connections) to make timely, important changes. I use Graphic Converter a lot, so I tried it, and it’s OK. Same with iClip and PopChar. But the aleatory can’t be entirely eliminated, as demonstrated when it turned out that a Kensigton driver was at fault, because I thought they’d be big enough and astute enough to have tested it, and fixed it, in time.


Another important criterion is whether you really need the app at all. I found I had quite a few which I’d hardly ever used, or not in a long time, so I dispensed with them.


Two apps I use and like have been mentioned in this thread as being potentially dangerous, but cause me no problem: CleanMyMac and Avast, an antivirus app (I know about "no viruses on Macs", but I can’t help think it’ll happen some day, and Avast, being free and problem-free seems to be a good investment).


But when you start experimenting like I did, it’s pretty risky unless you have a external clone to work with (I use SuperDuper! for that, which is also no problem), rather than risk your main boot drive. With such a clone, all you risk is your time.

Dec 26, 2015 7:07 AM in response to gbdoc

I am a computer-user veteran but not a computer-expert but I am willing to try what you did.

Can you help me with the process?

I understood:


1. Have handy a reformatted (empty) large disk.

2. Install 10.11.2 to this disk

3. From my main disk (or Time Machine?), manually copy and paste apps to the reformatted

5. Clone the reformatted after each app transfer (here a question: clone it where to?)

6. BAM ! , next question: not clear to me, you mean the app will not work?

7. Where are the .kext located?

Thanks!

Dec 26, 2015 11:17 AM in response to Mikile

My initial setup: a 250GB AirBook which already had 10.11, with about 200GB on it; regular TimeCapsule backups; and a 1TB external drive (FireWire 800 connection) divided into 4 equal 250GB volumes - 1 each for bootable clones (made with SuperDuper) of my AB (usually made about weekly) and my wife’s (same Mac, somewhat different SW), 2 more for different kinds of extras (neither of which has much on it).


Since I lost all my data twice long ago, I’ve become a belt-and-suspenders user. Not only do I have 2 **’s (TC and my clone), I also have TechTool Pro, which makes an “eDrive”, a small bootable partition on my AirBook from which I can run TTP; and a bootable USB of DiskWarrior (which is also on my AB).


  1. Make fresh clone of AB to “AB Clone” (ABC)
  2. transfer the stuff from one of the “extras” volume to the other, so as to have yet another 250GB volume free, which I formatted and named ElCap (EC).
  3. Install 10.11.2 on EC, make sure it boots (it most likely will, mine did)
  4. booted up from EC, used Migration assistant to migrate only the system settings, and the documents and data (the 2nd and 3rd choices you’re offered), but none of the apps, from my AB to ElCap. Rebooted a couple of times, to make sure it was OK.
  5. (Ah, yes, now it turns out I used 2 external volumes!) Booted up from EC, DL’d and installed SuperDuper! on it, made sure it booted with that.
  6. Booted from EC, I cloned that to ABC (using SD’s “Erase then copy” option).
  7. Booted from ABC, to make sure it was OK.
  8. Booted from EC, I started to repopulate my apps by DL’ing and re-installing them, according to the theory I described above, starting with the most essential. (Copy and paste or drag and drop won’t work for me here, because most apps install arcane things throughout the system which I don’t know about).
  9. After every few installs I’d see if EC booted up, and if it did, I cloned it to ABC (this time using SD’s “smart update” function, which only copies changed items, and is thus much faster than “erase then copy”).
  10. Every few times, for safety’s sake, I tried booting from ABC. Also, every now and then I booted from the AB, from where I ran DW on both EC and ABC, to make sure the directory was OK (occasionally it found something to repair, but I never had a problem in this regard).
  11. Somewhere toward the end I installed that Kensington trackball driver, which hung my system (that was the BAM).
  12. Booted into AB (but it might have been ABC), and opened up EC, and hunted down the trackball driver and its .kext (*), and deleted them (and emptied the trash).
  13. EC now booted fine, so I installed everything else I wanted - omitting the Kensigton driver, of course - until I was done. I encountered no more problems.
  14. Finally, I cloned ABC to AB (“erase then copy”).


* I don’t remember any more for sure where I found the files. But the trackball driver is a pref pane, and .kext files are kernel extensions, and thus in an Extensions folder. Both are in Computer>My AirBook>Library, then >Extensions, and >PreferencePanes. That said, there’s a strange thing about .kexts: I read that they’re ony functional if the related app is active, or trying to be, otherwise they just fill space (but they’re small). So, despite also reading that not only the app, but its kext must always be removed, which I did, I’m not sure it’s really necessary.


In retrospect, though, I could have saved the time I spent hunting, and it would have been safer, had I done it differently, not as in 12 (above). Still, the way I did it pretty much proved the culprit. Instead, though, I could have done this, which I recommend, since then you don’t have to hunt anything down to throw out:

12. Boot into AB, clone ABC to EC (“erase then copy”), and go on installing apps, omitting, of course, the Kensington driver.


Two more things:

First, I had a few games, which use Steam. Feeling no great need for them, a bit wary of that installation (perhaps needlessly), and tired of fooling with my Mac for now, I haven’t re-installed that yet. But I will, sooner or later, and then I’ll see.

Second: There might be an easier way to do all this using something like CleanMyMac, installed on a functional clone, (which plays well with El Capitan) to delete all the things which you suspect might be problematic (or, conversely, delete everything except for “sure things”), reboot, and, if you got the right files, the update via the App Store to 10.11.2 should go fine. But that’s another story, which I never played.


Good luck! And be prepared to not see your family or friends, or use your Mac for many, many hours! Get a good book to read while the time-consuming stuff is going on.

Dec 26, 2015 12:07 PM in response to gbdoc

Uahu! That's a piece of work.

Thanks for dedicating so much of your time, I will learn it well and then make a trial.


In parallel, still pursuing your idea that isolating the culprit(s) app(s) solves the problem, I thought to use a short cut: find and delete "suspicious" apps before upgrading to 10.11.2.

As a help for finding "suspects", I checked that Roaring Apps site mentioned by linda2009. Also dedicated some thought to apps that are behaving odd since installing El Capitan, like your TrackBall.

Roaring Apps has very few apps tested for 10.11 but for Yosemite or Maverick some apps that I have installed are red: Photoshop Elements 9, Parallels 7 and Viber (redundant anyway, don't use it). Perhaps for El Capitan these apps might be red as well?

Checked with Parallels website: they issued a warning that Parallels 7 will not work with El Capitan (in fact, it already made me problems with Yosemite and Maverick).

And Elements (like your Trackball) is behaving very odd since 10.11 installation.

Both are very suspicious indeed !


Thanks again for your help.

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.

System wont boot after OS X 10.11.2 update

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