superdrive not loading discs after upgrading to el capitan

CD/DVD Loading Problems

CD/DVD Drive - Troubleshooting See troubleshooting section.

CD/DVD Drive - Troubleshooting (2)

Same problem here.

Superdrive connected to 27in iMac via USB port on connected dual Thunderbolt screen. Superdrive shows up in System Information but won't load discs.

Have tried SMC reset and PRAM reset - doesn't resolve issue.

Have connected the drive via USB port on second Thunderbolt screen connected to a MacBook Pro that is still running Yosemite and it works fine!

Definitely an El Capitan problem.

Same problem.

My USB Superdrive doesn't work at El Captain. I have a Macbook Pro mid 2014.

I have another Macbook Pro mid 2010 with Yosemite and it works fine.

I agree, problems with El Capitain.

Same here. I've been on the phone with support for 3 days now. I am waiting on a response.

Experiencing the same problem. When the drive is connected to a hub (and even the USB port on my Apple monitor), it doesn't work. When plugged into my Mac Mini, it works just fine. Is this some sort of energy saving feature?

Just figured this one out! I had the same exact problem on my iMac after the upgrade. Plug in the drive and restart the computer with it connected.

-John

This issue isn't really solved. Yes, I can restart my MBP with the SuperDrive connected, and it will work. But it should be recognized and accept disks even if it's connected after boot -- just as it did with Yosemite. I spoke with Apple several times, and engineers took a look at my logs. They thought there was a conflict with Logitech's Control Center, so I uninstalled it. But that did not solve the problem.

Hello Guys,

I am still having problems, even when I re-boot everything. Is this an ongoing issue with el capitan?

I have both IMac and Macbook Pro

Thanks guys

Hi

I think that the problem is With El Captain .

Because muito USB drive continue working with another Mac

With yosemite.

Come on guys lets help us.

I have a lot of information on DVDs

Hello,

the problem is the lack of record "mbasd = 1" in the system. To solve this problem you need to open the "/Library/Preferences/SystemConfiguration/com.apple.Boot.plist." and edit "apple.Boot.plist" - Text Edit is sufficient.

The key "Kernel Flags" is empty. You must add between start and end string "mbasd = 1" and the problem is resolved.

Oh one more problem: to manipulate the system, you must be "root" user and is not the end, because in this version of OSX is active

the "System Integrity Protection" or SIP for short. This is actually a way for Apple to push again the limits of the safety of your machine, prohibiting all users (including God Root) touching some critics judged files.

So even root will not have the right to go to copy any document in the following folders:

/ System

/ bin

/ usr

/ sbin

The idea behind this, is obviously to protect the user against any possible threat, a risk that weighs increasingly heavy with the growing popularity of OS X. After the much-maligned "Gatekeeper" (which required developers to sign their applications), Apple demanded that the systems extensions are in turn signed (and thus validated). Now it is the entire system that was padlocked. By doing so, Apple protects against particular vulnerabilities already present in OS X, and sometimes allow to "mount" the privileges of a normal user, to become administrator of the machine.

Fortunately for developers and hackers, there are (still) a way to disable SIP. To do this, reboot into "Recovery" mode (Command-R at startup) and run a terminal.

Then type the following line:

csrutil disable

Reboot and everything will be as before: the root and the administrator will again play with the system files.

I imagine you know how to activate root account :-)

Hello,

the problem is the lack of record "mbasd = 1" in the system. To solve this problem you need to open the "/Library/Preferences/SystemConfiguration/com.apple.Boot.plist." and edit "apple.Boot.plist" - Text Edit is sufficient.

The key "Kernel Flags" is empty. You must add between start and end string "mbasd = 1" and the problem is resolved.

Oh one more problem: to manipulate the system, you must be "root" user and is not the end, because in this version of OSX is active

the "System Integrity Protection" or SIP for short. This is actually a way for Apple to push again the limits of the safety of your machine, prohibiting all users (including God Root) touching some critics judged files.

So even root will not have the right to go to copy any document in the following folders:

/ System

/ bin

/ usr

/ sbin

The idea behind this, is obviously to protect the user against any possible threat, a risk that weighs increasingly heavy with the growing popularity of OS X. After the much-maligned "Gatekeeper" (which required developers to sign their applications), Apple demanded that the systems extensions are in turn signed (and thus validated). Now it is the entire system that was padlocked. By doing so, Apple protects against particular vulnerabilities already present in OS X, and sometimes allow to "mount" the privileges of a normal user, to become administrator of the machine.

Fortunately for developers and hackers, there are (still) a way to disable SIP. To do this, reboot into "Recovery" mode (Command-R at startup) and run a terminal.

Then type the following line:

csrutil disable

Reboot and everything will be as before: the root and the administrator will again play with the system files.

I imagine you know how to activate roo account

Disabling the SIP was the thing that allowed me to save the changes to the plist file. Thanks for the help.