Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Okay so Displaced and Mrumsd I am in the extensions folder. I searched for VirtualBox and the name of the specific extension in my picture but it doesnt come up. Is there a particular name they like to use?

Daveak I dont have the dmg anymore, you think if I download it and try that it will work?

Thank you guys so much for your help

Mine was found under /Library/Extensions. The names are VBoxDrv.kext, VBoxNetAdp.kext, VBoxNetFlt.kext, and VBoxUSB.kext.
 
Okay so Displaced and Mrumsd I am in the extensions folder. I searched for VirtualBox and the name of the specific extension in my picture but it doesnt come up. Is there a particular name they like to use?

Daveak I dont have the dmg anymore, you think if I download it and try that it will work?

Thank you guys so much for your help

Hi,

No problem!

Ok -- so the name displayed in your picture is the 'bundle identifier', so the Extension filename as shown in Finder won't be the same. Do you have any that mention 'VirtualBox' or 'VBox' in their names? Feel free to post the names here in case you want a bit of confirmation before trashing it.

Rest assured though, as long as you're in /Library/Extensions and not /System/Library/Extensions, you cannot break OS X by deleting anything. Only /System/Library/Extensions contains stuff vital to OS X. And as I say, if the VirtualBox installer put its extensions in there, it's very, very naughty. That's exactly the kind of thing that the new 'rootless' or 'System Integrity Protection' feature in El Capitan will prevent.
 
Hi,

No problem!

Ok -- so the name displayed in your picture is the 'bundle identifier', so the Extension filename as shown in Finder won't be the same. Do you have any that mention 'VirtualBox' or 'VBox' in their names? Feel free to post the names here in case you want a bit of confirmation before trashing it.

Rest assured though, as long as you're in /Library/Extensions and not /System/Library/Extensions, you cannot break OS X by deleting anything. Only /System/Library/Extensions contains stuff vital to OS X. And as I say, if the VirtualBox installer put its extensions in there, it's very, very naughty. That's exactly the kind of thing that the new 'rootless' or 'System Integrity Protection' feature in El Capitan will prevent.
I found a couple files in named as VBox so I ended up deleting those. I am restarting now I will let you know the results
 
To all developers out there... DON'T UPDATE if you code. Xcode 6.4 will crash and Xcode 7.0 won't build at all.
 
To all developers out there... DON'T UPDATE if you code. Xcode 6.4 will crash and Xcode 7.0 won't build at all.
Xcode 6.4 hasn't worked in any of the previous builds, so that's not really new.

It's not posted as I write this, but you probably need Xcode 7 beta 5. (I can't confirm whether beta 4 doesn't work as you say, waiting on downloads.)
 
Ok - don't panic! This should be an easy fix.

The error's telling you the problem -- the VirtualBox kernel extensions are incompatible.

Turn off your mac, turn it back on. When you hear the startup chime, hold the SHIFT key to perform a safe boot (third-party kernel extensions won't be loaded).

Then, when you're in OS X, uninstall VirtualBox.

[EDIT: After that, it might be worth seeing if other VirtualBox users are having the same problem. It might be corrected in the next OS X beta, or it might need a VirtualBox update]
Hi, I am another person with the same error and I have followed this advice and other advice that follow:

Shift on start = get progress bar which is stuck two thirds complete
Cmd+S = same error as normal boot but on black background. Cannot enter anything.

Do you have any other suggestions? Thanks you

edit: the SHIFT method and the progress bar eventually worked after giving it several minutes. thank you very much!
 
Last edited:
El Capitan will be stable on christmas. Every year is the same, and let's be honest, it will 300% sure have bugs even on the version 1 when released...
 
Okay so after deleting all the VBox extensions everything worked normally. Thank you everybody for your help!!!

Excellent! No problem. I had the exact same problem a few years ago with another OS X beta. It wasn't VirtualBox that caused it -- it was something else.

I dare say that the final El Capitan installer will move those into the 'Unsupported Applications' folder which OS X updates create when they find existing apps/extensions that'll cause these kinds of problems.
 
Xcode 6.4 hasn't worked in any of the previous builds, so that's not really new.

It's not posted as I write this, but you probably need Xcode 7 beta 5. (I can't confirm whether beta 4 doesn't work as you say, waiting on downloads.)

Man, I was coding on Xcode 6.4 right before the update. After restarting, Xcode tried to reopen and crashed, so please: quit pretending to be a genius.

Plus, Xcode 7b5 will PROBABLY be out tomorrow at 2PM, but who knows.
 
Excellent! No problem. I had the exact same problem a few years ago with another OS X beta. It wasn't VirtualBox that caused it -- it was something else.

I dare say that the final El Capitan installer will move those into the 'Unsupported Applications' folder which OS X updates create when they find existing apps/extensions that'll cause these kinds of problems.
Good thing you as well as others were so willing to help. Knowing my impatience I would have just reinstalled everything.
 
Wow, overall feels must faster. Using firefox and scrolling is better than before updating. And cut and paste works in terminal again. iTerm is a nice alternativ I used when cut-n-paste was not so must paste.

regards
Claus

How do you enable cut and paste? I used to use xtrafinder for that, which is no longer functional in el capitan.
 
In the history view, select all and press delete. Done.

There should be an option with just one click like every other browser. Safari is the only browser not to offer the option. Odd thing it was there before Yosemite, can't figure out why Apple would make it so difficult to do.
 
This is new right ?
 

Attachments

  • image.jpeg
    image.jpeg
    1.6 MB · Views: 726
Xcode 6 and 7 won't even launch. Latest versions and everything.
These guys at Apple are unbelievable :D
 
Xcode 6.4 hasn't worked in any of the previous builds, so that's not really new.

It's not posted as I write this, but you probably need Xcode 7 beta 5. (I can't confirm whether beta 4 doesn't work as you say, waiting on downloads.)

Xcode 6.4 worked on Beta 1 and Beta 5. It's so pathetic that I can't help myself but laugh about it. :D
 
Same problem booting up. Appears to be vbox related. But the files previously mentioned aren't in /library/ extensions or /system/library/extensions

I can't use shift key after boot chime or command s.

Only command r works after I enter my firmware password. Then can launch terminal to navigate around

Im i missing something?Help!
 
I don't know what they did with this build, but EVERYTHING is so fluid and fast. I've barely had any UI frame drops. Animations across the board feel speedier.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.