Reboot fail after installing El Capitan help!!

Thank you very much GSfromNL! You made it easy for me. Made your lists that you described very well, used the Finder to dump stuff. I dumped the one that everyone seems to see, the Eltima, and also dumped one for a Wacom Pen Tablet. The pen tablet one had inspired some sort of incompatibility warning somewhere during the update process, so I dumped it. Was prepared to dump a bunch of unsigned stuff from Logitech, USBOverdrive & Canon, but left them and tried a restart. Two consecutive restarts with no issues.

Thank you, you are a wizard!

Same issue with El Capitan.

1. I was able to finally get to Recovery in order to go through the interminable re-install of El Capitan. Once that was finished a software update was started for Office.

2. Unsuccessful reboot that now hangs at the White Screen of Death (before I had Apple's Gray Screen of Death0

3. No ability to do Command Recovery

4. Holding down option to get to Disc Recovery now doesn't work either.

I am worse off HAVING re-installed El Capitan. My Imac is dead. El Capitan killed it

I"m surprised your comment wasn't censored. Mine was: complaining about Apple "geniuses" lack of interest in an obvious critical problem. This post will be censored too b/c it is Micro-softesque incompetence that is making it impossible to use my Imac for work productivity purposes.

I am typing this on my work PC

This is what sent me spinning back to ground zero.

Was able to do that full El Capitan download from the App Store (should be called Death Valley not some majestic mountain peak). Got everything back to normal. Was then prompted to update the download for Office via my automatic software update prompts.

Fatal mistake!

Went from Apple Gray Screen of Death to Apple White Screen of Death and interminable re-boots.

Have not tried the Kext removal. The wannabe geniuses at the Apple Genius Bar were totally clueless on this issue and just wanted to take my wallet for a service call.

Very disturbed by the continual Microsoftian lack of interest or concern about these major OS problems by Apple Corp. I guess I should have been "happy" when Yosemite only killed my Internal DVD drive. El Capitan has me dead in the water.

It's like the Bill Murray movie Groundhog Day

Many thanks, I was at my wits end on this one. In my case the culprits seem to be Blackberry/RIM, Harmony (remote control for AV systems) and 3Dconnexion (a 3D mouse I last used a long time ago). Not sure if it was some or all of them.

Do not really understand your problems, but from reading, do not believe it is OS related. You wrote:

After reinstalling your Mac works, meaning El Capitan is working.

After an Office update it hangs, so there something did happen...

Maybe your HD is failing?

Try make a bootable thumb drive and check with disk utility. Did you make any backups? If not, make it now, before it is to late...

Anyway:

Please write down exactly what happens, and keep in mind: If you are looking for faulty Kexts and started Terminal from recovery, it will only find the libraries on your HD if you do a change directory to your internal HD (not the recovery partition) as in: cd /Volumes/MacHardDisk/ (substitute MacHardDisk with the name of your HD)

Surely somebody comes up with the fix!

BTW: You also wrote that Mavericks killed your DVD drive, IMHO impossible to happen, unless you did things with the DVD drive firmware (to make it region free?)

Ok, so far this is great, everyone is happy solving their issues deleting Kexts 🙂 that's nice

Mine is the same, after putting my password, Gets stuck halfway on the loading bar..

But what if I cannot get into safe mode (holding shift key)

Or that repair mode (command r), I have been trying to get into it and after the loading bar is sometimes stuck halfway, sometimes it's done and just either brings me the grey screen or just now, it starts to beep sadly "beep, beep, beep" (3 times) continously..

I'm using my tablet to access the forums and typing on it is a nightmare.. Plus I have work to submit!

Yaaay 😁 Very nice...! Lol...

YOu know Apple has failed when I have to fire up an old Lenovo laptop to find out why my 4 year old Imac wont reboot.

no Gray or White Screen of death from Bill Gates

had to move that 2000 dollar paper weight into the corner to make room for finding asolution to my problem that doesnt appear to exist

http://www.cultofmac.com/392991/el-crapitan-the-biggest-problems-plaguing-early- upgraders/

so Apple knew there were problems with El Capitan in beta. Esp. With one of my serious issues: Mac stopped booting in middle of Office iupgrade.

but Katy bar the door, they forced this on us any way.

congratulations Apple El Capitan is the first non-operating OS

I am really sorry to bother you again, but I have finally been able to get into recovery mode

Terminal is open.. I did type the same stuff you posted (system profiler SPExtensions...) Reading it from my tablet and typing it in terminal as is

I cannot copy and paste the code since I cannot open anything when terminal is open..

This is what I got :

/var/root/Desktop/KextsList.txt: no such file or directory

I am a designer, I dont code.. Please bare with me

To Bob and Casey:

This should work, but terminal (read Unix) wants EXACT names, uppercase, lowercase, spaces and so on...

If there is a space in the name of your HD: it is crucial to type EXACT as I explained below:

So: Try the following commands in Terminal to list the kexts on your internal drive:

cd /Volumes/HDname

Replace HDname with the EXACT name of your harddisk.

If there is a space in the name of your HD: Type a slash after the first name, then a space, then the second name: Like HDname\ XX, otherwise terminal will NOT find your HD!

Then:

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:

Move all suspects to a different location with these commands:

sudo md ~/System/Library/KextNotSupported

sudo md ~/Library/KextNotSupported

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

Note: replace EXACT KEXT NAMES with for instance EtimaAsync.kext

Hope this helps!

If so: Check the "box" this helped me.... Thanks!

I am by no means a computer wizard, so I am kind of lost on your directions. Is there a way that you can dumb it down and list step by step? Because I really need my computer to work. I have been trying to figure out how to fix it for over a week now. Would it just be easier to delete everything and start over? Or would that not fix the problem? All I know is that I was updating to the newest update but had to leave before it finished. When I came back home I kept getting the kernel panic warning and haven't been able to use my computer since.

I had a problem installing El Capitain on a 3 year old MacBook Air. Three times I tried with fresh El Capitain installs on a reformatted internal drive. Then used El Capitain Migration Assistant to migrate stuff back from a SuperDuper created copy of the original drive. Each time the first startup attempt from the updated internal drive failed with the forbidden icon. This fix from GSfromNL fixed everything! Ensure you do this on the backup drive before you migrate it back!

Thank you so much for giving perfect, foolproof instructions on how to do this!

Char

I Have tried every one of your suggestions multiple times with no success.

what I am especially troubled by is that since I upgraded to El Capitan, and the interminable reboots started, I have been unable to perform a Command Recovery nor boot in Safe mode.

is there a reason other than El Capitan that would cause that problem?

LeeSniper:

Most of these problems are the result of software conflicts on startup with Kernal Extensions (KEXT).

The boot up process fails to even reach the user LOGIN screen.

Moreover, boot-up into SAFE MODE does not help.

The best way to avoid this is to do a clean install of the OS X and then a migration from a backup disk.

However, if a user had already performed the upgrade, one needs to boot up from a different drive and then manually remove the KEXTs from the non-boot system. A task of manually determining what software is causing the conflict and removing it.

In the past, Apple had run conflict checking software prior to major OS updates.

I did not see this problem until the 10.11.2 update installed much more security software.

My clean install to a different disk without a migration of computer settings worked for me.

To do a clean install, one needs a backup first.