More ways to shop: Visit an Apple Store, call 1-800-MY-APPLE, or find a reseller. Apr 14, 2017. 'root device uuid is '0000334A-4BA2-0000-00' Loading drivers. Error loading drivers' If that helps. I also saw people restoring macbook's with Target Disk Mode but that needs a firewire cable, I haven't tried it yet because I dont have a firewire cable and another macbook, is also using a.
Apple MacBook Pro 'Core 2 Duo' 2.8 15' (Unibody) Specs Identifiers: Late 2008 - BTO/CTO - - - Distribute This Page: Download: The MacBook Pro 'Core 2 Duo' 2.8 15-Inch (Unibody/Late 2008) technically is a 'build-to-order' configuration of the, but also is documented as a separate model for reader convenience. Other than processor, these two models are identical. With a black and silver design reminiscent of the models, the 'Unibody' MacBook Pro 'Core 2 Duo' (Late 2008) models have an all new case design milled from a single block of aluminum that provides greater strength and a superior finish than previous systems. Details: These Geekbench 3 benchmarks are in 32-bit mode and are for a single processor core and all processor cores, respectively. Both numbers reflect an average of user provided results as submitted to the. Higher numbers are better.
You also might be interested in reviewing single core and multicore Geekbench 3 user submissions for Macs with the MacBookPro5,1 Model Identifier, which may include. To dynamically compare 32-bit Geekbench 3 results from different Macs side-by-side, see EveryMac.com's. Details: These Geekbench 3 benchmarks are in 64-bit mode and are for a single processor core and all processor cores, respectively. Both numbers reflect an average of user provided results as submitted to the. Higher numbers are better. You also might be interested in reviewing single core and multicore Geekbench 3 user submissions for Macs with the MacBookPro5,1 Model Identifier, which may include.
To dynamically compare 64-bit Geekbench 3 results from different Macs side-by-side, see EveryMac.com's. Details: By default, 4 GB of RAM was installed as two 2 GB modules, no slots free. *Apple officially supports a maximum of 4 GB of RAM.
Originally, this model was only unofficially capable of stably supporting 6 GB of RAM, but as by site sponsor OWC, it is capable of supporting 8 GB of RAM if updated to Boot ROM Version MBP51.007E.B05 and running MacOS X 10.6 'Snow Leopard' or higher. In the US (and many other countries), site sponsor sells memory -- as well as other upgrades -- for. In the UK, site sponsor sells memory and other upgrades for. In Australia, site sponsor sells memory and other upgrades for. In Southeast Asia, site sponsor sells memory and other upgrades for.
Details: 15.4' color widescreen LED-backlit TFT active-matrix 'glossy' display with a 1440 by 900 native resolution. Apple reports that it also supports '1280 by 800, 1152 by 720, 1024 by 640, and 800 by 500 pixels at 16:10 aspect ratio; 1024 by 768, 800 by 600, and 640 by 480 pixels at 4:3 aspect ratio; 1024 by 768, 800 by 600, and 640 by 480 pixels at 4:3 aspect ratio stretched; 720 by 480 pixels at 3:2 aspect ratio; 720 by 480 pixels at 3:2 aspect ratio stretched'. In the US, site sponsor sells Apple OEM parts.
Apple parts available include display panels, logic boards, graphics cards, interior cables and sensors, and more for. Worldwide, site sponsor sells quality, brand new, factory-direct parts with global shipping and bulk discounts for repair shops.
Replacement parts include displays, keyboards, trackpads, speakers, cameras, and more for. Details: Apple reports that this slot-loading 'SuperDrive' drive (DVD±R DL/DVD±RW/CD-RW) has a maxium write speed of '8x DVD-R, DVD+R; 4x DVD-R DL (double layer), DVD+R DL (double layer), DVD-RW, DVD+RW; 24x CD-R; 10x CD-RW' and a maximum read speed of '8x DVD-R, DVD+R, DVD-ROM; 6x DVD-ROM (double layer DVD-9), DVD-R DL (double layer), DVD+R DL (double layer), DVD-RW, and DVD+RW; 24x CD'. Site sponsor offers a 'Data Doubler' mounting kit that may be of interest. It makes it simple to install a second hard drive or SSD in the optical drive bay of. Details: One ExpressCard/34 expansion slot. Also see: is ExpressCard/34?
Is it compatible with PC Cards? In the US (and many other countries), site sponsor sells a wide variety of ExpressCard/34 cards as well as external expansion options and accessories including docking stations, adapters, input devices, cases, and more for. In Australia, site sponsor offers an extensive selection of ExpressCard/34 cards in addition to external expansion options and accessories like docks, stands, chargers, cases, security products, and more for.
Details: Apple reports that this model has a '50-watt-hour lithium-polymer battery' that provides '5 hours of wireless productivity'. Also see: is the 15-Inch 'Unibody' MacBook Pro battery life in 'real-world' tests? What is the difference in battery life when using the NVIDIA GeForce 9600M GT compared to the NVIDIA GeForce 9400M? In the US (and many other countries), site sponsor sells quality batteries for. In Australia, site sponsor is a local distributor of OWC batteries for. In Southeast Asia, site sponsor sells OWC batteries for.
Details: *This system fully supports the last version of OS X 10.8 'Mountain Lion' and OS X 10.9 'Mavericks' except for 'Power Nap' and 'AirPlay Mirroring' (which also requires an Apple TV 2nd Gen or higher). It also supports the last version of OS X 10.10 'Yosemite' and OS X 10.11 'El Capitan' -- including Mac-to-Mac AirDrop capability -- but no other advanced features are supported.
It is not capable of running macOS Sierra (10.12) or subsequent versions of the macOS at all. Please note that OS X 'Lion' 10.7 and subsequent versions of OS X are not capable of running Mac OS X apps originally written for the PowerPC processor as these operating systems do not support the 'Rosetta' environment. To run PowerPC applications on this Mac, it will be necessary to use Mac OS X 10.6 'Snow Leopard' or earlier. Also see: Macs are compatible with OS X El Capitan (10.11)? What are the system requirements? Which Macs support which features?
If your OS X El Capitan/Sierra update won’t reboot you can or check here for the (mostly). Otherwise feel free to read the saga below! Update 3/23/2016 – It happened again when I updated to 10.11.4!
Even fewer clues this time, additional details and an updated script to remove non-default kext files at the very bottom. Update 5/14/2017 – This has been an issue for myself and others running OS X Sierra as well. Update 8/01/2017 – I updated to 10.12.6 and once again was unable to boot. This time I had to remove kexts from /System/Library/Extensions. Removed after running ls -lat. After Update, OS X Won’t Reboot After upgrading to OS X El Capitan (10.11) when it was released, I had been generally pleased with the new version but there were a few quirks – like random beach ball pauses – that made me think the 10.11.1 update would address some of them. Thus when I was notified that it was available, I dutifully upgraded and then my MacBook Pro Retina wouldn’t reboot.
I reset the ( Shft+Ctrl+Opt+Pwr while off, then Pwr), I reset the ( Cmd+Opt+P+R+Pwr while booting, then hold until the chime sounds again), I tried to boot into ( Shft+Pwr). Single User and Verbose Mode I was unable to boot into ( Cmd+S+Pwr), but it and ( Cmd+V+Pwr) did show that the boot process was hanging and the last message it displayed was: pci pause: SDXC This seemed to be meaningful, but was ultimately a wild goose chase. Recovery Mode Reinstall I could boot into ( Cmd+R+Pwr) and used this to access Disk Utility to run First Aid (no errors were found), and then used Terminal to run resetpassword which was then used to reset permissions on my user folder. I reinstalled the operating system over the Internet. Using Terminal accessible in Recovery Mode I found several crash logs located in /Volumes/Macintosh HD/Library/Logs/DiagnosticReports/. I took a look at the latest one and it had the following details about the crash.
Spoiler alert, this also ended up being a dead end, but I’m posting it because the only other place on the Internet it exists is a deleted Apple Developer Forum post that I was able to view using the Google Cache. Hi All, Thanks for all the replies and suggestions, its indeed super helpful in saving the macbook without reinstalling. I just want to add on some details incase some of you have the same issues as me. The primary issue is indeed a malfunctioning Kext file.
To resolve is to simply move the files to another folder and try starting up. Moving non-familiar kext to the system is sufficient.
Now here comes the tricky part. For some of us, our logical volumes are encrypted and for some of us like me, we will be stuck on trying to find out which kext files as non-familiar on a volume that is the recovery volume. What we need to do is to mount our logical volume. To ascertain if you need to do that, start system in recovery as per instructions: 1.
Download Facebook Messenger For Sony Ericsson X10 Mini here. Command + R while powering up to reach recovering mode. Login as per normal and start Terminal 3. At the bash command prompt type: diskutil list 4. You should see the a list of /dev/disk.
If you have an offline disk which is listed as encrypted. That will be your logical volume. Type in diskutil corestorage list 6. A list of corestorage logical volume group will be shown.
Look for the information Logical Volume with a string of UUID (e.g., Logical Volume 43E6C312-24EA-4987-AA65-FB517AA966AD ) 8. Highlight and copy the UUID: 43E6C312-24EA-4987-AA65-FB517AA966AD 9.
Next unlock the volume and it will mount: diskutil corestorage unlockVolume UUID -stdinpassphrase —-( replace UUID with yours in this example its the 43E6C312-24EA-4987-AA65-FB517AA966AD) 10. System will prompt you for the passphrase to unlock your volume, Key in your password and the drive will mount. Once mounted. You can follow the instruction to move the unsupported kext to a folder and restart it. For me the issue was some LG 360 camera usb kext and the Huawei data card kext. For the benefit of those who is wondering what I am talking about: 1. Cd /Volumes/#your Macintosh volume id/Library/Extensions 2.
Ls -lat or ls -lrtc 3. Mkdir /Volumes/#your Macintosh volume id/Library/backup 4.
Mv /Volumes/#your Macintosh volume id/Library/Extensions/*unfamiliarext.kext /Volumes/#your Macintosh Volume id/Library/backup/ 5. Move all the unsupported kext over and you can type: reboot. If everything goes well. You will boot back into your system! Hope it helps some one!!! Thanks for the hard work.
This may be a simple/silly question, but I need to ask it. This is all caused by stuff that’s kept when you install an OS version upgrade right (at this point in time it is going from Sierra to High Sierra)? If you boot into recovery mode and wipe the disk first, and then clean install, will it fix the problem? I’m having this issue with my MacBook Pro, and all my files, photos, etc.
On it are back up (not Time Machine, but manually to an external disk), so I’m not worried about losing anything. That’s correct! If you wipe the disk and do a fresh install it should work fine 😛 The issue in this post that seems to be fairly common is related to old kernel extensions left over from previous installs. Even though all my data is backed up externally (currently my data goes to Time Machine, NAS, Dropbox, and cloud backup) I am a web developer so setting up my machine again is possibly many days of work, and as they say time is money, so an upgrade is often preferable to a fresh install.
Unfortunately several of these issues were caused when I accidentally clicked the “upgrade” button in the OS alert instead of “later” and wasn’t actually planning to upgrade at the time. Good Day, Mr Silver: Big problems with my iMac with progress bar frozen ar 100% after taking 20 minutes to get there. Apple care people have taken me through umpteen attempts to work through problem which seems identical to the one for which you have found a much praised solution.
I have never written code and find it almost impossible to summon the courage and confidence to start now. But, is there anyone out there living near Barnet in north London that you know of whom I could hire to come and fix things for me? My machine is late 2009 model and recently upgraded to High Sierra. This took four hours last weekend and it seemed to work well at first. The problems started when I tried to log on last Monday and I’m now desperate as to next step. Many thanks for your attention. – Peter Shrubb.
Hello, Can this be made into a script so it will just run every time you shut down? There are two canon extensions that keep the machine from booting when we restart, every time we delete them they reappear. I tried putting your code into script editor but it gives me an error: # mount the drive as read/write mount -rw / # create a directory for “disabled” extensions mkdir /Volumes/Macintosh HD/Library/ExtensionsDisabled # view files that exist in your Extensions folder but not the recovery partition kexts=`comm -23. Where is it giving you an error in the script editor? Are the files visible before you reboot? If they are getting reinstalled it makes me think there is something triggering it. Do you have any other Canon software installed?
Do you have any printers listed under System Preferences >Print and Scan? Once there are no printers installed delete the kext files using Terminal and then reboot, it shouldn’t keep creating the files. There are also some pretty involved guides out there for getting rid of Canon drivers, for example and. First of all, thank-you for this guide. I’ve been struggling with a loading screen stuck at 100% after updating to High Sierra.
It was good for two boots and by the third, right after I installed Paragon Driver, I have been stuck at with a loading bar at 100%. Listing my System Library.kext files does not reveal there to be anything from older than a year ago, they only go back to last July. Problematically, I can’t even seem to delete (though I can copy) them even using rm -rf. It also doesn’t recognize sudo as a command. Do you have any suggestions? Justin, after trying various things I think I have the same issue but I’m running into some trouble. I’m not sure if my version of terminal is outdated (Version 2.5.3 (343.7)) but it starts every line with “-bash-3.2#” if that means anything to you.
A “mount -rw /” command has no effect, so when I paste your script, after “mkdir /Volumes/Macintosh HD/Library/ExtensionsDisabled” it tells me “/Volumes/Macintosh HD/Library: No such file or directory”. It seems like a slightly different Terminal from yours; any idea what I should do here?
Thanks for any help you can provide! I have bash 4.4 on my main system, but not sure if it is an older version if you reboot into Recovery Mode or not. Either way, it should be fine. >bash --version bash --version GNU bash, version 4.4.12(1)-release (x86_64-apple-darwin16.3.0) It sounds like you might have a hard drive with a different name?
Try typing ls -la /Volumes and see what it says there – you may need to use something other than “Macintosh HD”. The other possibility is that you have damage to your drive in some other way and it’s not being read properly – you could try using First Aid in Disk Utility or for rebuilding it. Hi Charley, “VeryOldKernelExtension.kext” is just an example of an old kext file, you would get the actual names from your system. I installed bash 4 via – I forgot that OS X is stuck on 3.2 for licensing reasons. /usr/bin/ruby -e '$(curl -fsSL brew install bash With an older version of bash you might need to mount your drive as read/write with this command: mount -u -w / I’m not sure how to convert the find command to the older syntax off the top of my head so you will need to do some research. Thanks a lot Justin.
Your trick has helped me for the last couple of years, but as I forgot the procedure I had to come back here today. I’ve narrowed this boot problem down to being the printer extensions from either Epson or HP causing havoc, as every time I delete them, my macbook pro late 2011 boots w.o. The problem reoccurs when I – or rather apple updater installs the printer drivers included in an OSX software update.
Thus I’m very aware not to install these printer updates when I go near the app store, but apparently accepting “Later” when prompted by mac updater is equal to accept installing these – that’s the only way I can explain why I suddenly find my mac not booting and them in my extensions folder. Does it really work like that?
For those of you who have access to a second mac, here’s another way of reclaiming your mac’s bootability. I usually boot my problem mac up in target mode (holding down T at bootup) after connecting it via firewire or thunderbolt to the other well functioning mac. From the “good one” I can open the problem mac’s harddrive, locate the library/extensions folder and delete the Epson and HP kext files. This way I don’t have to deal with terminal.
Al, Technically booting to the Recovery partition is the same thing as booting to a USB drive – in both cases the OS is loaded from a different disk than your “Macintosh HD”. There are some protections in place on the /System folder and I have had problems removing files from there as well.
Writing is typically where I run into trouble so I moved a backup to /Volumes/Macintosh HD/Library/ExtensionsSystemDisabled (note that it is not under the /System path). If that doesn’t work you can use cp to copy them and them rm -rf to remove them. You should already be root but trying sudo rm -rf can’t hurt.
You also want to make sure that the drive is mounted read/write with mount -u -w /. All that said booting to a Linux USB will do the trick too 🙂. Hi Kyle – I just got back online after a few weeks of travelling. It’s very strange that you can get to single user mode but not recovery mode.
The former should load your system with most extensions/drivers disabled, whereas the recovery mode should load from a completely different partition. It’s possible that your recovery partition was corrupted?
It’s very hard to say what the issue might be in your case. I would recommend looking around for debug/crash logs to see if there are any clues there, as well as looking at any software you recently installed or updated. Hi Justin, Thank you for your kind reply and for your help! I was unable to boot my mac after updating to 10.12.6, but, after using this script, I was able to boot my mac once again: mount -rw / cd /Volumes/Macintosh HD/Library/Extensions/ mkdir Unsupported mv *.kext Unsupported reboot The problem is that my Mac is running extremely slow, all the time I get the spinning beach ball, basically every time I do something. What do you think I should do now? Should I open Terminal and run the other scripts?
Glad to hear the script let you start your computer again. It’s really hard to say what the other issues might be. I would recommend booting into Recovery Mode again and running First Aid using Disk Utilities to verify your hard drive and repair permissions. You might also want to try running the maintenance scripts using (I’ve not had issues, but proceed at your own risk). You might also want to check the /System/Library/Extensions to see if you have anything old there (I personally removed all the kexts older than 2016).
Also check out the console/crash logs to see if there is anything interesting there. Another thing to keep in mind is that I have read that FileVault can bee very slow to decrypt, especially with a full drive, so it might take some time to complete. Hi again Justin, I was unable to update my Mac with High Sierra as I received the same message when I tried to reinstall OS in Recovery Mode, it wasn’t possible due to Filevault still being in the process of decrypting.
Before that I forgot to mention that I was unable to backup with Time Machine and Super Duper, the process would always fail, I then installed StellarDriveClone and was finally able to backup. Filevault never got pass the decrypting process and I was forced to erase the disk, reinstall and migrate all my system and files from the bootable backup external drive. My Mac is now back to normal. Thank you again for your help! I wish I had found your post before talking to Apple, they were the ones who told me to turn off Filevault thus getting it stuck on decrypting. Hi Andy – I think that unfortunately you might need to use trial and error to determine which kext is causing the problem, and then it will be easier to determine why it keeps coming back.
If you are removing all of them then there should just be one or two showing up in /Library/Extensions. My guess is that you have some software on your system that sees that the kext is missing and replaces it, so uninstalling that software (or installing a newer version) would fix it if that was the case. Hard to say without more details but if I had to speculate I would guess it is hardware related like scanner or printer software. If you can post a list of the extensions on your system maybe something will stand out. Hi Justin, thanks for the reply!
I think this is the problematic kext: EPSONUSBPrintClass.kext Although these also keep reinstalling every time I reboot: BJUSBLoad.kext CIJUSBLoad.kext hp_io_enabler_compound.kext I’ve removed every possible piece of Epson related software I can find on the machine, don’t have an Epson printer installed, but lo and behold, every time I reboot, these four reappear. But by process of elimination, I think it’s the EPSONUSBPrintClass.kext that is causing the problem. Any ideas how I might hunt down what’s installing it? Does the system keep a log of this anywhere? Thanks so much! First, I would just like to say thank you, you wonderful wizard! Your script saved my MBP after I upgraded to Sierra 10.12.3.
Second, I have no idea what any of these kexts things are, so I am terrified to shut down my computer and reboot now in fear it will happen again. How do I find the offending kexts and the apps connected to them?
If you can, I will need super N00b instructions. Third, before I found your instructions page, I tried rebooting from my TimeMachine, but that was hanging up upon booting, too. Does that mean the problem is in my TimeMachine, also? Can I even fix that? Thanks again for saving this poor doctoral student from having to sell an organ for a new computer! Hi Brenda, A “kext” file is a “kernel extension” – in simple terms it is a plugin for OS X similar to a plugin for your browser. The problem is that some older files that are no longer compatible with newer version of the operating system may still be on your drive and because it tries to load these when it is starting it just hangs.
If you move them out of the extension folder and were able to restart your Mac then you should be good to go. The files won’t re-appear unless you move them back, reinstall the incompatible software that put them there, or restore from an older Time Machine backup.
Regarding Time Machine, definitely go ahead and make a new backup (assuming you are up and running). Lady Gaga The Fame Monster Zip Rar Files more. One nice feature of Time Machine is that you can completely restore all of your files (including the kernel extensions) however this can be a problem if one is broken.
Your older backups are still super useful for accessing older versions of your files (perhaps a paper you are working on, pictures you accidentally deleted, etc) but you won’t want to do a full restore from these older backups because they will put the incompatible kext back on your system. Once you have a new backup you should be fine though – as far as Time Machine knows you just uninstalled something and it will use the latest (working) version to do a restore. Hi Justin, I have the same problem, my Mac few weeks after updating to OS Sierra stopped working, I’ve done the Hard Disk Utility which said that there are no errors, I don’t have access to the recovery mode at all, the loading screen stops at 50% and I have to restart the computer. I tried to gain access through single user mode, but even after changing the user to ROOT I couldn’t change anything in the code, I didn’t have permission to write. When i tried to change anything, that line: PCI:Pause:SDXC would pop up and I couldn’t do anything else. Thanks Justin, you are a genius and a lifesaver.
Win 7 in bootcamp worked fine with Option + Power to boot up. Mine was an Epson printer kext that during a system update caused El Capitan to hang on the update, waited forever. Tried everything reset SMC and PRAM, first aid on disks, could not boot in Safe Mode. Was about to launch the mid 2012 MBP non retina out the window when I found this post on my phone and thought I would give it a go. Fixed straight away.
I do not know how to thank you enough but I hope these thanks go some small way to saying how much time, grief and money you have saved me. Hi Justin, I’m running 10.11.6 on a late 2013 Mac pro. I followed your steps and successfully moved all the.kext files from the extensions folder to the unsupported folder. The computer rebooted successfully from the terminal, but would not reboot after that. I have to do a hard shutdown to reboot.
I then tried your second set of instructions, and moved all the.kext files to the ExtensionsDisabled folder within Library, but the same problem happened. It reboots successfully from the terminal once, but then will not reboot again after that, it just hangs. Any thoughts? Thanks for your help.
Congratulations Justin You deserve a medal for documenting a solution that so many other experts failed to propose. I even think that what you propose is applicable to more than just El Capitan upgrade stalls, and that there might be a way to simplify the fix without having to use terminal and cmd-R I was facing a stalled boot (stuck at end of apple bar) on MBP 13 and 15 running El Capitan but also Yosemite.
I tried all the classical SMC, PR NVRAM, single, re-install, with absolute no success So I ended up re-installing clean, migrating and it worked but only for a while 🙁 Your solution fixed it for good on Yosemite and El Capitan. Hi Justin, The number of people you have been able to help on this issue is astounding. I do hope I can get some success also.
I have exhausted several searches online but nothing works. My MacBook was operating fine prior; I have el capitan installed been using for months now. I launched a new app, that I recently installed, and I got a blue screen, with no other option but to power off. Since then, when I boot, I am able to enter password but then my progress bar boots up half way then stops. – I have a grey screen whenever I try to go to safe boot. This I suspect is because filevault is enabled on my hard drive, which makes it encrypted.
– Whenever I also try to launch in internet recovery mode. It loads the process completely with the globe, but afterwards a quick flash of a black screen then permanent grey screen. – I cannot get into Recovery mode, when I hold down Option it does not show my recovery partition, therefore I cannot get to a Terminal via the method you described. I can however get to single-mode but what can I do once I am there?
Do the steps you have listed still apply based on my scenario? Any advice would be extremely helpful. Hi Jeff, it’s hard to say for sure what is going on, but if you can get to Single User mode you should be able to do all the same things that you can in Recovery Mode, the biggest difference is that you are starting from the boot partition rather than the recovery partition. Since you install the software recently you could look for any recently added kexts, but that might not necessarily be your issue, but it might be worth a shot. The other thing I would recommend is to look for your crash logs – from the GUI it’s Applications >Utilities >Console, if you are using the command line it’s likely in /Volumes/Macintosh HD/Library/Logs/DiagnosticReports/. Thank you very much, your page helped repair our mac after the latest captain update.
I booted into recover mode and opened a terminal. Checked the Extensions directory with “ls -lart” to sort them with oldest first, this is an older mbp from 2009. I took the kext extensions dated back from 2009 and 2010 and moved them into another directory. My mbp is now booting again. I removed some old hp printer driver extensions and EyeTv extensions. 3 days ago the mbp crashed with hardware fault and blue stripes and could no longer boot. I disassambled it and used a heat gun on the motherboard to try and repair any bad solderings.
I put it back togheter and the the hardware fault was gone and I was soo happy that I managed to repair our 7 years old mbp. Then I updated the software and ran into this new problem not certain if it was hardware related or a new software fault. The factory had done a really poor job with the cooling paste on the chips, I was very surprised at the poor workmanship. I am a supply chain manager and have overseen electronics assembly at factories before and this was by far the worst I have seen including other devices that I have disabled in the past.
The cooling paste only covered half the cpu and gpu chips. There was about 10 times too much paste on the side of the chips as if they had added a thick layer and scraped it off, not removing it but just scraping it down the side of the chips. I have never seen factory assembling handling cooling paste in such manner, normally they should add a framed when adding it. This mbp has always been noisy and quick to ramp up the fan speeds.
Now it is silent and keeping the chips cool when wathing netflix, before it would allmost max the fans when watching Netflix. Your post here solved my problem some months ago, when I upgraded to El Capitan.
Great – Thanks. I was totally lost for a while, but fortunately I had a bootable system on another disk, and from there I opened “my main disk”/Library/Extensions and moved/deleted all kext files in my system.
Eventually the programs I used afterwards pretty much pointed me to which kext files I needed, and all other files stayed out of the Extensions folder. That solved my problem then. Now, however, as I narrowed the obnoxious extensions down to being one of four printer extensions [BJUSBLoad.kext, CIJUSBLoad.kext, EPSONUSBPrintClass.kext, hp_io_enabler_compound.kext], I have to be cautious every time I update OS X as these files are a part of every update I’m offered. Eventually I will find out which of them is causing havoc on my computer. I don’t know if anybody else have trouble with these specific files or if there is a randomness to these issues. Anyway I just wanted to share my way to obtaining the desired goal.
Suggestion: If you have another Mac available you can boot one of them in target mode (Hold down “T” when booting the machine) and connect the two machines via Thunderbolt or FireWire. From there you just have to navigate to the System/Extensions folder on the machine that fails booting and extract the kext files to new folder ie. “Bad Extensions”. Keep in mind that moving the files to another folder does not delete them within the Extensions folder – you have to do this after copying them.!
Best Vibes, Mo’. Hi Justin, I’m glad I came across your page on this issue. However, the troubleshooting steps didn’t work in my case.
I have a early 2011 MBP 17″ w/512GB SSD and 2.3GHz i7 & 8 GB RAM. About two months before I decided to upgrade from Snow Lepoard to El Capiton my MBP was acting sluggish. I’d get the death spiral from time to time. About two weeks after the upgrade was the first time my MBP EVER crashed.
This would occur several more times before it would have problems booting up. Now months later it won’t boot at all.
I tried your suggestions, Safe, Recovery & Verbose. In Verbose, it go thru the logs and then a black screen and then white screen.
I videoed the screen in hope of reading it, but there is too much glare to read it. When I tried to boot from my backup drive it would show the white screen after about 3/4 progress.
Any advice you can share would be greatly appreciated. Kind regards Ivory. Hello Justin, It turns off. I followed your instructions to the letter, so i am pretty certain i moved all the kext files. Like i said earlier, I had tried to fix the boot problem initially, by using disk utility and the repair function. I got the following message from using the first aid option (while the First Aid option was running, I noticed my Macintosh HD available space had changed to 0KB, even after the process completed it showed this), after the process completed it came back with this error “First Aid process has failed. If possible back up the data on this volume.
Click Done to continue.” when i clicked the Show Details option. It had this: “The volume Macintosh HD could not be verified completely. File system check exit code is 8. Updating boot support partitions for the volume as required.
File system verify or repair failed. Operation failed” Before using the Disk Utility First Aid Option, it would boot up to let’s say 90% and just freeze, but after doing that process it would boot to about 60 -70% and then turn off. Where do I access the crash/debug log, so I can send for you to see?
This guy is good. Thanks and yes it worked a treat. In my case it was an Epsilon printer kernel extension. My procedure for solving a hanging boot: 1. I thought a core file had been corrupted.
Checked the logs Zero. Repaired file permissions. And single user mode. A DSMOS error appeared, so.kext error suspected, 5. Removed my graphics.kext files in /System/Library not very clever at all. Later I returned them and had to delve into a backup for the one I deleted. I followed the instructions here to remove /Library/Extensions/.kext Bingo!
I placed all the non-suspect files back to the Extensions dir, except the Epsilon file, which was the last “alien” file to be downloaded before the hanging job error occurred. Hi Justin (et al.), First of all thank you. Thank you, thank you. I’ve had your page open all day.
Your work, knowledge, and presence are exemplary and critical to users like us finding solutions to Apple’s wormhole-like unanticipated technical problems. Secondly: your fix ended up not being my fix. I did your thing and wrestled with my.kext files for hours.
I’ll get to my solution but first of all, when moving kext files back from the Unsupported folder, I did this step straight-up in my normal Mac OS, not in terminal during recovery mode. That is to say, I did your steps in Recovery Mode and rebooted and then from Finder moved all but the logitech drivers BACK into /Library/Extensions — upon which I was greeted with both a permissions pop-up and, after providing my password, an error message.
The kext files were in /Extensions but I’d then deleted the “originals” from /Extensions/Unsupported — looks like the originals were not moved back to /Extensions, but copied. I’d emptied the trash and deleted the originals. I was still having rebooting hangup issues, so I continued to troubleshoot various things. At some point I re-did your initial steps on this page: in Recovery Mode, moved kext files from /Extensions to /Extensions/Unsupported. Then I followed the advice someone else here commented to press Command while dragging the kext files back — no error messages.
So right now I have copies of the kext files in my /Extensions folder At this point I’m still unable to restart. The one workaround I found was to go to the Login Window (by clicking my username in the upper right) and restarting from there. It asks you to provide user/pass for whoever’s still logged in, but it will restart. What I think fixed the restart hangup was related but different. Related because it’s to do with outdated driver conflict.
Different because it was solved, ironically, from within the easy-to-use Mac OS System Preferences pane. As others have noted, old Wacom drivers will sometimes remain on the system after apparently full Wacom uninstall.
I went to System Preferences –>Users & Groups –>Login Items and noticed that a “Bamboo” helper app was still opening automatically upon login. This means that this invisible, conflicting app was hanging up my OS whenever I was trying to restart or shut down. At least, I think it does? Things seem to be working now. I may have used your advice to ultimately just delete my original.kext files, but nothing so far has fallen apart. Thanks again and I hope my advice can help someone who’s unable to solve their problem with your post. Aloha Justin, It is so encouraging to see all the posts of success stories.
I am just tech savvy enough to follow your instructions. Otherwise I know nothing about Terminal commands. I feel like an idiot because I have no idea how to bring up this list everyone has of their.kext files. If you can share that command line with me I would like to see what comes up. I followed the steps in your article – first the 4 steps moving the kext files to Unsupported and rebooting which did not fix, then the steps to Disable kexts, and I still get the gray screen with the progress bar stuck at about 3/4 of the way.
I have been working on this for 2 days as time permits, and do not have the money to pay the $300+ I will be charged to recover my data. I also tried someone’s (was it yours?) suggestions for trying to back up my files to an external using Disk Utility, but the instructions were for maybe 10.7 not 10.11 so I may not have done it right – I had to guess on some steps. Any help would be greatly appreciated! If you have Apache OpenOffice and removing old extensions didn’t resolve your boot problems, or only resolved them temporarily try booting into Safe Mode by holding down the Shift button after you power on your Mac until the gray screen lights up. If you can boot into Safe Mode uninstall OpenOffice. Make sure there are no OpenOffice folder or files inside the Library/Application Support folder.
This worked for me! Thank you Justin, for taking the time to help out those of us who know our way around computers, but aren’t experts!
You’ve saved a lot of frustrated people like me a lot of unnecessary frustration! I was having this problem of being not being able to boot my MacBook Pro past the gray apple loading screen. I followed your instructions for disabling extensions you had found incompatible such as old HP and Epson printer extensions. This allowed me to boot again but only for several days. I checked everything I could find other people having problems with on this thread and others I found from countless google searches.
Finally I remembered that I had recently installed Apache OpenOffice 4 and that shortly afterwards it frooze up my MacBook while I was editing spreadsheets a couple times. As I remember, this was not long before the boot issues began.
I booted into Safe Mode by pressing the Power button and before the screen lights up white or gray pressing and holding down the Shift key until the Apple logo and/or progress bar appears. After a few minutes it was able to boot in Safe Mode. Once in I uninstalled Open Office support files by opening Terminal, typing “open library”, once it opened a Finder window in the Library folder I opened the Application Support folder in it and located the OpenOffice folder inside it and dragged it to the trash. Then after deleting those support files I opened my Applications folder and dragged the OpenOffice icon to the trash to uninstalled the program. Then I emptied the trash to delete everything permanently, and VOILA, I checked for and installed system updates, restarted, and I am happy to say it booted up quickly on the very first try and everything seems to be back to normal.
Hope this helps anyone else who has been dealing with this issue for the last several weeks now like I have! My advice for anyone with this same problem, try installing Libre Office instead. It is also freeware compatible with MS Office file formats, and I haven’t had any problems with it since I installed it on the bootable external hard drive I’ve been using the last few weeks while I’ve been working on this issue with my internal hard drive not booting up. My Macbook Pro (2009) couldn’t boot up after the 10.11.5 update. I was able to log in as Guest but unable to access my account.
I tried your fix but it didn’t resolve the problem. I found the solution here: 1. Login as guest 2.
Open Terminal (cmd + space then search terminal) 3. Enter su “your_account” 4. Enter your password 5. Sudo find /private/var/folders/ grep com.apple.LaunchServices grep castor 6. Sudo rm /private/var/folders/cd/someLongRandomNameHere/someFolderNumberHere/com.apple.L aunchService-whatever.csstore. Kevin, thanks for pointing to this forum article.
I had tried everything, and then Justin’s method didn’t resolve things either. So happy to have found your reference to this forum article. I would suggest to Justin to update his article and mention this method at the end. Just point to it as an: “in case the above fails”.
Note that when you go into the recovery console and then terminal, you do not need the su and sudo commands, you can start the find straight away and then delete reach of the cache files. When you copy/paste the cache file names, do not forget to add an escape before the space in the hard drives name.
Also, applicable to all things here: my drive is called “Macintosh SSD”, as that is similar to “Macintosh HD”, it is easy to overlook that your disk name is different. Absolutely fantastic! Thank you so much, you helped me save some very important stuff that I hadn’t backuped yet!
I was wondering about these kext files that seem to be default and unproblematic: ACS6x.kext ArcMSR.kext ATTOCelerityFC8 07.08.53.kext ATTOCelerityFC8.kext ATTOExpressSASHBA2 07.08.53.kext ATTOExpressSASHBA2.kext ATTOExpressSASRAID2 07.08.53.kext ATTOExpressSASRAID2.kext CalDigitHDProDrv.kext HighPointIOP.kext HighPointRR.kext PromiseSTEX.kext SoftRAID.kext I’ve noticed that they are also in the System Library Folder, so perhaps they don’t need to be in the Library folder as well? My problematic files were some surfstick drivers. The following don’t seem to cause any problems, but do you happen to know what they might be from? Cdc_10_9.kext cdc_ecm_qmi_10_9.kext Ann. Justin, thank you so much for sharing this – YOU SAVED MY DAY!!!! My problem was not with “El Capitan” but Mavericks (10.9.5).
After a shutdown (for cleaning, normally machins keeps running) system wouldn’t restart. Hung at “installing drivers” (CMD+V).
With your help, I found a recently installed Kernel Extension from a CITRIX Receiver named “CitrixGUSB.kext”. Moved this away (I have a recovery partition arranged which can access my normal boot partition – comes handy sometimes), and the problem was fixed (after all other popular tricks, like fsck, NVRAM reset, SMD reset, fix permissions on FS failed). Possibly more expensive than if you had a working laptop 😛 It sounds like your drive is either corrupted or has errors, so if you don’t have a second Mac to boot from you can try to boot from a Time Machine backup into Recovery Mode. With your Time Machine plugged in, hold down Opt/Alt while it is booting to select the external drive. Hopefully from there you can run DiskUtil to fix an errors. I have never done this before and I’m not sure if would work on your system but I think you can replace the hard drive entirely and when you boot up it will ask you for your Apple ID and then re-install the OS from the operating system.
Hi Justin – All your advice and efforts on this page is so much appreciated!! I had found my mid 2009 MacBook Pro essentially unresponsive after I accidentally left it sleeping for several days last week. It has been slower and aloof since updating to el Cap a couple months ago. Then, on the restart last week it was just hanging forever. I tried your basic suggestions with some success (also reinstalled O’s 10.11.4 in recovery mode and some terminal fixes, then rebooted etc). A question tho: being completely new to using terminal commands myself, when I type your script I don’t really know when to hit return during the “view files” and then the “move extra kexts” parts.
In other words, after each line or after the complete command? I’d also like to check out which kexts I currently have now that I’ve rebooted, but not sure I’ve figured it out. I’d like to know whether I still need to move some again. Thanks again – this has really saved me! Thanks so much Justin.
I had the same problem after updating to 10.11.4. I spent 2 days trying to resolve the issue to no avail. Your fix worked.
I did however have some issues which I’ll mention here in case others have had the same. First, typing the script didn’t seem to work despite writing it exactly as instructed. I kept getting invalid command errors or directory not found errors. To resolve this I ran safari in recovery mode and copied the script off this website right into terminal. This worked for me.
Second, I discover that Little Snitch was the likely cause of my grief. After successfully running the script and booting I installed the latest version of Snitch and I am now able to boot without issue. Hopefully the system remains stable but if not I can just run the script again. Thanks again, you’re a legend. I have an early 2009 mac mini with 2Gb ram. I’m having problems with OS X 10.11.4 randomly hanging at boot up.
It was working fine with 10.11.3. Here is a list of the.kext files on my system. Hello Justin, I am glad I found your post and I see others have benefited from you. However I am quite new at this and I think I have messed up the steps. This is what I see after I try to write the commands please note that my hard drive name is MacBook Pro HD Mount -rw Cd /Volumes/MacBook Pro HD HD/Library/Extensions/ Cd: /Volumes/MacBook: No such file or directory Mkdir Unsupported Mv *.kext Unsupported Mv: rename *. Kext to Unsupported/: No such file or directory Please where did I go wrong and what is the way forward.
Hi Jay, You should probably use the script at the very bottom of this post as it’s a bit more clever and only removes non-default kext files. That said the problem you are having is with the hard drive name – the default is “Macintosh HD”, but it sounds like you might have renamed yours “Macbook Pro HD”?
No matter what the name is, it’s important that you escape the spaces in it with a backslash. That means that “Macintosh HD” becomes “Macintosh HD” on the command line, and “Macbook Pro HD” becomes “Macbook Pro HD”. I’m sure you noticed that it is case sensitive, so you need to use lowercase mount (don’t forget the “/” at the end to indicate your root), cd, mkdir, and mv. That makes it sound like your hard drive isn’t mounted, which might not be a good sign. It’s possible that it’s not mounted because it’s using FileVault or something? At any rate you probably want to check out DiskUtil and see if you can see your drive there, and if so run a Verify / Repair on it.
If you want to try from the command line type diskutil list to show your drives, then diskutil mount /dev/disk1s2 where disk1s2 is the ID of your disk. Some more details on mounting/unmounting disks here:. Hmm, not sure if that’s your issue. SoftRAID.kext is there, I just didn’t include it ’cause you mentioned that it’s a default.kext file.
Hi Justin Thank you so much for the tutorial, first of all. I successfuly installed El Capitan just now (version 10.11.4, I believe), but after typing my password in to login, the progress bar seemed to stop moving after it reached 100%. Talked to some guys in Apple Support and they all wanted to do a clean install. Hi Janet, For the first mount command you need to make sure to include a forward slash at the end for “root”, so mount -rw /. It looks like you did escape the space in “Macintosh HD” the second time, and it seems like you probably already did this since the “Unsupported” folder already exists.
My guess is that the last mv says “No such file or directory” because you have already moved all the files to “Unsupported”. If you want to move them back try the following, and then just run the script at the very end of the post to automatically remove anything that isn’t also found in your Recovery Partition. Mount -rw / cd /Volumes/Macintosh HD/Library/Extensions mv Unsupported/*.kext. I appreciate your post so much, but my MacBook still won’t boot after performing your fix. I only had 1 kext file that was not on your list (an HP file), which I moved to Unsupported, but no luck. The interesting part is that my MacBook “crashed” literally right before I was to run Migration Assistant and transfer files to a new MacBook over wifi. The new MacBook does not have any ports (except USB-c).
I bought a new MacBook b/c my old one was dreadfully slow and low on memory. Could that be the problem? I saw one line on my terminal that read “cache too full for physical memory” (or something like that). You’ll have to forgive me. I’m tech savvy but definitely not as computer-gifted as you! I would greatly appreciate any advice you have. Thanks very much for your very informative post, saved me a lot of time not having to do another fresh install and backup recovery.
I left my Macbook on for months out of fear I might have to restart 🙂 Great to post all your.kext files, so I could move all.kext files back that you show in your list (excluding the Logitech ones). And voila, I was able to reboot as well! In my case the culprit was a printer related.kext file from 2010 from an Epson A3 printer. So I downloaded the newest, reinstalled the printer and all OK. Now all.kext files are back again in my /Extensions, but this time it all works. From my experience with this fix: – the final Terminal command “reboot” did nothing visible, so I rebooted myself, which worked as well – I dragged the correct.kext files from /Unsupported to /Extensions and got weird error messages.
Then I realised I was not moving them back, but copying them. Holding the Command-key solved that. Trawling around the web looking for possibly suspect.kext files I stumbled across thes following.kext files reported by other people: Virtualbox Evernote EltimaSync JMicronATA LivescribeSmartpen SSuddriv Videoglide Airparrotdriver LogitechHIDDdDevices Logimgrdriver Logitechunifying EPSONUSBPrintclass I also have a question: there are also.kext files in System/Library/Extensions. Could they also cause startup problems? Thanks for posting the additional details, that’s actually why I made this post originally when Google wasn’t returning anything for some of my specific searches. To add a few more to your list based on my upgrade to 10.11.4: • 360Controller • Wireless360Controller • WirelessGamingReceiver I also had an issue with the reboot command yesterday – it told me the disk was locked – but closing the Terminal window and selecting Reboot from the menu did the trick. As for the kext files in System/Library/Extensions, I don’t see why they couldn’t also cause a problem, however from my experience and what I’ve seen on the Internet it only seems to be ones in Library/Extensions.
Hi Justin your tips seem to ‘ve helping a lot of people. I tried doing them for my MBP but I screwed up? When the next files were being moved to the unsupported folder I quit terminal because I thought it was being unresponsive. Now I realized it was moving the files. When I try to do the process over again it tells me that the unsupported folder already exists. I created another folder “not supported” and tried to move them there but is says: rename *.kext to unsupported/*.kext: no such file or directory. What can I do???
Hope you can help thanks. Yes actually I got it to work now. My slootiun was:Make sure USB drive partition is Active after you format to FAT32Go to CMD.exe in windows and run these commandsDISKPARTlist disk (to find the disk number of the USB drive)select disk n (n is your USB drive’s disk number)select partition 1ACTIVEit should now say your partition is active. Now run ddmac and prep the USB drive per Guillaume’s instructions.Once prepped, plug the drive in to you Wind U90.
Power on, but go to your BIOS Go to Advanced tab, then down to USB settings. Find the USB drive that you have plugged in, and set it to USB Hard Disk (mine was FDD Disk as default). Save & Exit, and then boot to the USB drive when it restarts. Mine started booting at this point, no errors. Your set of musings/instructions is really first rate, an excellent examplar of how to troubleshoot. Against my better judgement, and in a hurry, I updated my son’s MBP (mid 2012) from 10.8.5 to 10.11.2.
Natch, it didn’t worknor go into safe-boot. So, into Recovery I went, and moved only those extensions to Unsupported that you hadn’t ultimately (and successfully) moved back in your description above. BUT, still no luck, indeed, the bar went less far than it had done. Fortunately, you still provided the key (to me and anyone who reads closely)I went to Logs, found the latest crash report, and lo and behold it turns out that an extension I’d stuck in Unsupported was neededso I moved it back, and am looking proudly at El Capitan now. Many thanks, you’ve made a friend and supporter/promoter. Hi Clanker, I feel your pain – I’m a developer so having a computer is pretty important for me too.
I’m going to be out of the country as of this weekend and am rushing to finish a bunch of stuff but will help if I can. When you say that the only valid command is mount, are you not able to run ls, mv, mkdir, etc? That should be all you need to move the kext files to a new location so that they don’t load. If you can send the exact output you get when you try to run the series of commands in the post it might point to the issue. Thank you so much for this post. After consulting two times the Apple Care hotline, – they gave up, – after 20 hours, — and recommended I should visit a local service point to reinstall my hard drive. Thrn I found your post, and the easy to handle instructions how to remove the incompatible.kext files.
(In my case it were two outdated HP printer driver files, and two files named klif.kext and klnke.kext). I only moved these 4 files, as all others were those in your list not causing problems. El Capitan finished installation and started! Have been lurking around on apple support forums and found almost same info, but less informative, here it’s very useful! BUT I have a bit different situation, maybe you can help me on that, or give a better advice? MBP retina 15 2012(mid), updated – then stuck, but(!) had something like that before, with Yosemite and prev. I dunno what exactly could it be but things got worsen for me during Yosemite, I upgraded with problems but uprgraded, then – I forgot (completely) my password and had to overran a system ( reinstall or smth like that) do not remember exactly.
Hi — Could someone have a look at my kext – list – Which ones might not be compatible with El Capitain. Or how do i find out? I’ll add that, for me, moving my extensions to Unsupported allowed me to boot once.
I then restarted to see if all was well, and it would not restart correctly (gray screen). I noticed a crash report from Flux about a month back in my Diagnostic Reports, so thought Flux could be the culprit.
I booted into recovery mode, opened terminal, deleted the Flux app, and was able to restart. I upgraded all my software, including 10.11.1 to 10.11.4, and things are working fine now. Haven’t yet tried to reinstall Flux or move any extensions out of the Unsupported folder. Hi Nana, If you are having the same problem I was the cause is incompatible kernel extension files which have the extension *.kext. In my case it was some Logitech files, but it could be a different filename in your case. This is the step by step process I took.
• Reboot into Recovery Mode by holding Cmd+R before you hear the chime while starting, keep holding while it boots. • You should see a prompt asking you to choose a language, then you are in Recovery Mode.
• From the file menu at the top choose Utilities, then select Terminal. • In Terminal you need to use cd to change directories to your extensions folder, then use mkdir to make a new directory called “Unsupported”. Cd /Volumes/Macintosh HD/Library/Extensions/ mkdir Unsupported • From here you can use ls to list the files in the directory. Refer to the article and the list of extensions on my system – if they are in the list then they are probably fine. Anything that isn’t in the list might be the culprit, so you can move it to the Unsupported folder with the mv command. Replace “Filename.kext” with the name of the kext file you want to move.
Mv Filename.kext Unsupported • After the kext files you suspect are causing an issue have been moved to the Unsupported folder type “reboot” to restart the system.