Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

system extension cannot be used AppleUSBEthernetHost.kext

I responded to the upgrade of iTunes today - to version 11.4. I did this in short succession on a Macbook Pro and iMac, both running Mavericks.


Silly me - Apple fails


On both machines I got an error message immediately after the upgrade as per the attached imageUser uploaded file


Suggestions on how to resolve this are most welcome


Oh - and somehow I cannot post to Apple Support Communities - go figure!


Thanks

MacBook Pro, OS X Mavericks (10.9.4), iTunes upgrade - 11.4

Posted on Sep 9, 2014 7:06 PM

Reply
142 replies

Sep 17, 2014 10:32 PM in response to bwanabonga

I placed a support call under the iPhone which we cannot connect. I ended up being passed on to 'CPU team'. The was not a good experience. The agent did not listen properly to the fact that this happened on THREE MACHINES. Even after explaining that I was pointed to a large total system update that pre-dates my problem by a number of months. I have not had the time and am concerned about such a large hammer for a specific problem.


It get's worse - my systems are now asking about the next update and the iPhone is announcing a new IOS. Apple seem to expect me to proceed without the ability to back up the phone!


I did some digging - this problem goes back to May this year when I stepped from Lion on one of the machines to Mavericks - evidence offered below from the install logs - it has been lurking for a while.


Come on Apple!


May 20 06:48:30 Norman-Burgesss-iMac.local installd[29832]: preinstall: (kernel) Kext com.apple.macos.driver.AppleUSBEthernetHost not found for unload request.

May 20 06:48:30 Norman-Burgesss-iMac.local installd[29832]: preinstall: Failed to unload com.apple.macos.driver.AppleUSBEthernetHost - (libkern/kext) not found.

Jun 9 19:40:58 Norman-Burgesss-iMac.local installd[3492]: preinstall: (kernel) Kext com.apple.macos.driver.AppleUSBEthernetHost not found for unload request.

Jun 9 19:40:58 Norman-Burgesss-iMac.local installd[3492]: preinstall: Failed to unload com.apple.macos.driver.AppleUSBEthernetHost - (libkern/kext) not found.

Jul 15 02:02:34 Norman-Burgesss-iMac.local installd[20753]: preinstall: (kernel) Kext com.apple.macos.driver.AppleUSBEthernetHost not found for unload request.

Jul 15 02:02:34 Norman-Burgesss-iMac.local installd[20753]: preinstall: Failed to unload com.apple.macos.driver.AppleUSBEthernetHost - (libkern/kext) not found.

Aug 11 08:00:59 Norman-Burgesss-iMac.local installd[8488]: preinstall: (kernel) Kext com.apple.macos.driver.AppleUSBEthernetHost not found for unload request.

Aug 11 08:00:59 Norman-Burgesss-iMac.local installd[8488]: preinstall: Failed to unload com.apple.macos.driver.AppleUSBEthernetHost - (libkern/kext) not found.

Sep 10 13:23:00 Norman-Burgesss-iMac.local installd[8488]: preinstall: (kernel) Kext com.apple.macos.driver.AppleUSBEthernetHost not found for unload request.

Sep 10 13:23:00 Norman-Burgesss-iMac.local installd[8488]: preinstall: Failed to unload com.apple.macos.driver.AppleUSBEthernetHost - (libkern/kext) not found.

Sep 10 13:23:27 Norman-Burgesss-iMac.local installd[8488]: kextcache: AppleUSBEthernetHost.kext is not authentic; omitting.

Sep 10 13:23:59 Norman-Burgesss-iMac.local installd[8488]: postinstall: //System/Library/Extensions/AppleUSBEthernetHost.kext failed to load - (libkern/kext) authentication failure (file ownership/permissions); check the system/kernel logs for errors or try kextutil(8).

Sep 18, 2014 12:20 AM in response to bwanabonga

It's difficult for somebody who is not involved in the development or support of software to determine the significance of a message in a log. Sometimes it is generated at a place in a module which should never be reached. In those cases at the very least they warn development that the matter should be investigated. Sometimes, such messages can help to explain why subsequent messages are being issued. In still other cases, the message is expected, given that the hardware or operating system does not support certain features, or some optional software has not been installed.


That said, these messages should be documented, and at some point in the process of supporting customers logs should be consulted to determine exactly what is happening in a machine when it isn't doing something that it should, or when it displays a message intended for the user. I can understand that most agents involved in first-level support are incapable of interpreting the contents of a log. What I do not understand, though, is, why they insist on running a customer who has evidently examined the console log through their idiot's checklist instead of passing him on to the level of support that deals with problems on that level. That just frustrates a potential troubleshooting ally, somebody who might also be able to subsequently help others to understand and work around the cause of the problem.


Having evidently been lucky that the simple fix of deleting the .kext and installing iTunes 11.4 from the Apple site works -- keeping my fingers crossed! -- I can say that I will not upgrade from OS X 10.7.5 Lion and iOS 7.1.2 until Apple fixes this problem to the satisfaction (almost typed "satisfiction", a Freudian slip on my part) of those running Mavericks who can no longer synchronize or use their iToys.

Sep 18, 2014 3:42 AM in response to bwanabonga

What I'd REALLY like to see is Apple tell us, or release to us, a method or update that effectively rolls back this lousy iTunes version. Before the update I had no problems...


I did a little more inspection of the log. During the many Mavericks months:

* This is the ONLY kernel extension that produces errors like this when an installer tries to do something

* This the ONLY component that is declared 'not authentic'

* EVERY time the AppleUSBEthernetHost is mentioned so is com.apple.driver.AppleMobileDevice (usually within less than a second in the logs)


I forgot to mention in the previous post that the tech said if all else failed I would have to re-install the OS from scratch. YOU HAVE GOT TO BE KIDDING - that is never what I would have expected to her from Apple. He also wanted me to validate system file permissions in the disk tool - hang on a sec whatever was destroyed in terms of correct permissions, if that was the case, took place on three separate machines all while running Apples fantastic installer!


Judging by the numerous posts here and in other forums this problem has actually started to render iDevices useless, because they cannot be synched or recovered.


I will be calling back to follow up on my support call for the iPhone. It is still in warranty for another 6 months. You can imagine the skepticism of my wife, for whom we bought the phone. In the first six months of life it has:

* spontaneously rebooted in the middle of the night into 'recover me' mode - restore failed, had to be a complete download from app store

* delivered us the 'red screen of death' - yes go and look for it

* got to the point in fabulous co-operation with the Macbook where we cannot connect, synch, backup to restore with Apples own software on their own hardware


I'd better stop typing - this just makes me mad!

Sep 18, 2014 5:04 AM in response to Greg Earle

Greg Earle wrote:


FYI - I have been contacted by someone at Apple and have been asked to talk to him via telephone to provide data to Apple Engineering about this. So they are on the case.


If there is any doubt that Apple Support does not read and monitor these communities, this and my past experiences show that not to be the case. My experience with the mid-2011 MBA EFI 2.9/2.9.1 issue is very similar.

Sep 18, 2014 5:10 AM in response to bwanabonga

If you are on the phone, and not happy with the current person, one option is to ask for an escalation. My experiences have been excellent and the resolution is usually quick and painless after such a request. The first level person usually follows a "canned" prescription to solve a problem. An escalation will get you someone more experienced and well versed in technical issue resolution, but do not expect the principal architect of iTunes or iPhone to be answering your calls either.

Sep 19, 2014 7:51 AM in response to tingly

I fixed it by opening up a Finder browser where I found AppleUSBEthernetHost.kext and dragged it into the trash can. Then, I downloaded and installed itunes from https://www.apple.com/itunes/download

This worked for me. I'm running OS 10.6.8 on my MacBook. After updating iTunes via software update and getting the error message, I never opened iTunes. Used Tingly's fix and haven't gotten another error message. All seems to be working well.

Sep 19, 2014 8:34 AM in response to Sandy B

Yes, as I said, Tingly's fix worked for me, too. I notice, though, that you and I are running older versions of OS X than some who report problems after doing what we did. That's why I would be interested in knowing (a) whether the problems with the fix only occur in Mountain Lion (one major version newer than my OS X 10.7) and/or Mavericks (two major versions older) and, for those encountering problems with the fix who are running Mavericks, whether the latest release of 10.9 solves the problems.

Sep 19, 2014 8:41 AM in response to bwanabonga

Just to relate my experience on a Mid-2011 iMac running Mac OS 10.7.5 (Lion)


On Wednesday, 17 Sep 14, I installed iTunes 11.4 to replace my previous iTunes 10 install. The same error message popped up. Today after reading this thread, I took the following steps:


1. Located the affected kext file and moved it to the trash (it was version 7.0 dated October 2009)

2. Re-installed iTunes 11.4 from the dmg.

3. Checked to see if the kext file had been installed and it had; now it was still version 7.0, but it has a date from July 2014.

4. Emptied the trash and shut down the iMac.

5. Re-booted the iMac and launched iTunes; no error message.

6. Connected my iPhone 3GS via USB and synced without a problem.

Sep 22, 2014 7:01 AM in response to FJD55

Anybody here who experienced the problem before the latest version of Mavericks, released just a few days ago? If so, did the new update solve the problem. Apple sometimes "quietly" fixes problems that it never acknowledges, allowing customers to work themselves into a tizzy discussing among themselves in such forums, while engineers quietly put the finishing touches on software that was (accidentally) released "half-baked".

system extension cannot be used AppleUSBEthernetHost.kext

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.