El Capitan won't Boot after update

What helped me was the following command line using the terminal.

sudo rm -rf /System/Library/Extensions/EltimaAsync.kext

All credit goes to Jaccofromalmere

Thank you carlos@mac. Modifying the filestamp with touch allowed me to reboot faultlessly (although slowly?) rather than reinstalling the OS as I had previously been recommended to do. That would suggest that the fault is definitely something to do with extensions, as you suggest. As a precaution, I also deleted the 'EltimaAsync.kext' file, but only after rebooting. So far I have rebooted only once more, but here's hoping…

This fix worked for me!! Thanks....

Thanks

S

Booting problem is solved with this !! Thanks a lot 🙂

I finally boot my MacBookPro after 3 days trying every solution mentioned. I think Fuse (previously installed) is the core reason for the problem, unfortunately "touch" solution have no success.

It would be a great help if everybody that responds with e.g. "This solved my problem", also mentioned to which "answer" he or she is responding. Now I don't know what exactly is "The Solution!" :-(

Working solution (at my case) can be found at RusFox message ( you can click "in response to RusFox" at my message)

I hope someone had an answer. I have a 2010 mac desktop that completely freezes when I boot it up. I get jagged lines all across the screen just after the apple logo comes on. It's like what old TV static lines looked like. I reinstall and the computer works fine until I boot up again.

Remember when Apple made stuff that worked!?

My MacBook had the problem: won't boot after update to El Capitan.

I tried different hard disks because it first looked like a hardware issue to me. But it wasn't. It's clearly a fault of El Capitan. It reminds me of the Microsoft world which I have left years ago. Since I have changed to Apple I was a believer that I would never ever have to spend so much time for a computer to run.

What helped me is the advice from carlos@mac, Oct 6, 2015 7:23 AM (... touch /Volumes/Macintosh\ HD/System/Library/Extensions ...).But unfortunately only until the next reboot 😟. So you have to follow the instructions of carlos@mac again and again - or never boot. I'm still waiting for the final solution.

Thanks to Jacco, this was the trick for me:

sudo rm -rf /System/Library/Extensions/EltimaAsync.kext

However if you can not boot, you have to go to recovery by pressing CMD-R during startup. Then start a terminal and go to the directory with this command: cd /Volumes/<YOUR BASE DRIVE>/System/Library/Extension

Then remove the Eltima module:

rm -rf EltimaAync.kext

Thanks, this helped me too: remove the /System/Library/Extensions/EltimaAsync.kext

Now my MacBook boots. Yippee!

The terminal needs "/Macintosh\ HD/"

I will not recognise "/Macintosh HD/" as a correct path.

Thanks. However I found it elsewhere as well. There appear also to be some old Virtual box kext files that may be a problem.

To make life easy and for those still struggling:

Usually the 1st start-up after install of El Capitan works. It's the second time start up (after shut down) when the problem does surface.

So for those who have experienced the problem and did install again: While in an operational El Cap just after install, go to your extensions folder and check whether EltimaAsync.kext is present.

When it is you need to use the terminal and type "sudo rm -rf /System/Library/Extensions/EltimaAsync.kext".

Alternatively you can type type "sudo rm -rf "and pick up via the Finder the file EltimaAsync.kext and drop it on the terminal screen. Push enter, give password and done.

Thanks for that. While people were replying, I was going through the second install of El Capitan. Now that I'm up and running, I'll try your fix and hope I don't have to reboot for a while.

This helped me

System/Library/Extensions/EltimaAsync.kext

I removed it after a successful start of my system after the 4th session of downloading the El Cap OS (Not Funny on my Data Bundle).

I also went a step further to delete

tun.kext

tap.kext

just to make sure (got that info from Max 108)

and now i can successfully reboot my Macbook Pro.

Thanks

Dear Carlos@mac

A new (?) problem came up: After any new software update (e.g. Office update, java update, App Store update), the problem comes back, and I have to go trough the whole "touch" process you describe to get my iMac back to life...

Any suggestions? Or must us wait for the Apple good will for a definitive solution?