Reboot fail after installing El Capitan help!!

I turn it on and starts perfectly, works normal.

Then when I want to Shout Down or Restart I hit the option (apple/restart or shoutdown) and all the programs start closing as normal but the process do not finish, the screen stays with the background image and the Dock.

I can reopen the programs from there and work normally but it doesn't shout down nor restart. All I can do to turn it off is force the power button.

This is happening since I installed El Capitan, is a Mac Book Pro Retina Mid 2012. I've never had a problem with it.

Hi,

I tried all steps of the kext solution, but my kext.txt file comes out empty.
so if i try to reboot it's the same, apple logo and bar to zero, stuck there.
i already reinstalled el capitan from recovery mode three times to try different solutions.
any suggestion?
never reboot again for life it's not ideal 🙂

This is a different problem than addressed in this thread... Anyway, the reason is most likely a running program that causes shut down / restart to be cancelled.

First thing to do is CMD -Tab so see if everything is closed, then check activity monitor so see what is running.

I think you either made a typing error in Terminal, or you did not startup from your HD.

There are absolutely Kext files on your HD. Maybe they are all signed, but one of these can cause your trouble...

Thanks GS, I checked the activity monitor and apparently the problem was an application called Air Display Host, I uninstalled it and is working fine now 🙂

It may not be compatible with El Capitan or something. Still feeling that the restart is not as smooth as normal but at least it restart. Thanks again!

Finding and removing the kexts solved my problem completely. I preferred the approach of booting into recovery, re-installing OS X then searching and deleting, as described by pwa65 on page 4.

Thanks to all the heroes in this thread, and elsewhere, who diagnosed it, tested it and took the time to report it here. Better service from volunteers here than from Apple, that's for sure.

Why couldn't Apple's own installer program check for these problems and fix or report them first, or fail gracefully rather than abruptly if they prove unmanageable? The problem was first recorded during beta testing so it's not as if they did not know.

Looks like the golden age when Apple made hassle-free products and cared about its customers is drifting into history. As someone else said Steve Jobs would have fired the whole release team. Eventually Apple will go the way of all the other computer giants who had their moment of greatness then became too arrogant to respond.

Thanks Luca,

Altima's SyncMate kext came up as loaded in my EtreCheck report (it's an Android sync utility for the uninformed which I don't use - it was poor software). I've downloaded the uninstall utility from their website (which wasn't signed or authorised - I had to bypass the security for non-App Store apps) and ran it. Of course, it forced a re-boot and I was very nervous (having completely reinstalled El Capitan x2 now to get past the issue!). I got through the re-boot in record time. I've not yet chanced my arm with a reboot initiated by me, but it looks promising. EtreCheck confirms the kext is no longer loaded.

Eamonn

OK gurus and hackers... here is my story, similar but some twists;

10.10.5 on Late 2009 Mini runs great. 10.11 install gets to about T-7 minutes then reboots. It goes into a Panic cycle, rebooting continuously.

Have done TM restore to 10.5 several times, then retried... have removed several apps and kexts that might be interfering, same results in many subsequent attempts (I have lost count).

I can do a clean install with no issues, but when I migrate all App, User, and System data from TM, goes into the same rolling reboot. I have even tried restoring just user files, just apps, and just system data, always gets back to rolling reboots.

I have tried CMD + R and re-installing the 10.11 install, no help.

Boot Drive is OCZ-Agility4 SSD with Trim Enabled via the new Apple TRIM support for third party SSD in 10.10.4.

Also, I have cDock\SIMBL installed which requires SIP disabled in 10.11, but my other machine (Mac Pro 3,1) upgraded fine with this in place.

So, wondering if TRIM on third party might be the culprit? Will try KEXT fixes again in the next round in case I missed any. But, have any of you heard of third party TRIM issues with 10.11? I have not found anything to that effect in dozens of forum searches.

Turned out to be kexts from a previous Mac.

Too bad SIP can't be disabled during the upgrade. Or maybe warnings that unsigned\incompatible kexts are present and give you the option to remove before upgrading.

Latest version of OSX checks for bad kexts during reboot.

However I had a new warning today (having cleared out all the offending kexts). "wado_d.kext incompatible".

When I searched for wado_d.kext I could not find it anywhere. Anyone know what it is, how to find it and how to remove it??

Strange that OSX now gives the warning message but no advice on what to do.

Posting here because it is likely connected to the problem reported in this thread. Will also post a new thread.

Thanks. Most likely correct. I did have Trusteer and it was flagged as no longer compatible with El Capitan.

I posted this topic as a new thread elsewhere on the forum. On that thread someone kindly explained that OSX now puts such kexts in a quarantine folder where they cause no further harm. Feeling more relaxed.

Thanks again.

Hi GSfromNL -

I waited until yesterday (i.e., Nov 23) to DL and install El Capitan, assuming that the past 7 weeks would have enabled Apple to ensure that the critical issues had been resolved for the first to take the 10.11 plunge. Wrong. Thanks for all your help.

To others after me who have just discovered this problem and read this -

I used GSfromNL's instructions in the reply to Markzol (Oct 11 2015 12:37 PM). It worked perfectly. I'll clarify a few things that were confusing to me. You will do a search within the kextList.txt file that automatically appears on your desktop post terminal instruction. This search is continual - you find one, copy the location line to a separate text/Word document and then proceeded to the next one via arrow at the top right. For myself, I had four kext that were not signed. These were as follows (this is what I copied to a separate text file).

/System/Library/Extensions/BJUSBLoad.kext

/System/Library/Extensions/EltimaAsync.kext

/System/Library/Extensions/JMicronATA.kext

/System/Library/Extensions/Soundflower.kext

The last three were often mentioned by others in this and other threads as being not signed. I followed GSfromNL's further instructions, finding, copying and deleting the corresponding extensions from the Locations.

And then I with excitment and trepidation and restarted. The screen went black, it seemed like a minute but it was probably about 20 seconds and THEN..........I saw the Apple screen with the bar proceeding from the left to the right with gradual darkness.

I gave myself a great hurrah internally and then found my husband and smiled from ear to ear.

Thanks again, GSfromNL. Much appreciate your guidance.

dear all,

i have the same problem as many of you.

i Can go to terminal only via utility os x.

The first thing I see in terminal is this: -bash-3.2#

I have tried to reach the kext extension files but I can not reach the folder using commands given on this support pages.

on the disc utility I can check all folders and I can see that I have many kext files, but from there I can't touch any of them.

I Need help!!

Think you did not start with your internal hard disk. If so:

Try the following commands in Terminal to list the kexts on your internal drive, (if asked for your password give it):

cd /Volumes/HDname (Replace HDname with the name of your harddisk. If there is a space in the name put in a slash before the space like HDname\ XX)

Then, but be VERY careful with these commands and use correct Uppercase and lowercase...!

sudo ls -1 /Library/Extensions/ ; sudo find /System/Library/Extensions -ctime +1d -depth 2 ; sudo find /Library/Extensions -ctime +1d -depth 2

This will give you all the kexts to sort out, if you found them:

Make different locations for the not supported kexts with these commands:

sudo md ~/System/Library/KextNotSupported

sudo md ~/Library/KextNotSupported

Move all suspects to the different location with these commands:

sudo cp ~/System/Library/Extensions/EXACT KEXT NAMES /System/Library/KextNotSupported

sudo cp ~/Library/Extensions/EXACT KEXT NAMES /Library/KextNotSupported

Delete them in original location:

sudo rm ~/System/Library/Extensions/EXACT KEXT NAMES

sudo rm ~/Library/Extensions/EXACT KEXT NAMES

Repeat for every suspected kext.

Note: replace EXACT KEXT NAMES with, for instance, EtimaAsync.kext and, again, use the EXACT Uppercase and lowercase...

Hope this helps!

Interestingly this problem only occurred on my, somewhat old, MacBook Pro when I updated from 10.11 to 10.11.1.

However the solution still turned out to be cleaning out the "obvious" crap kext files.

Thanks for the advice from those who contributed.