El capitan freeze during install

If it can't boot into Safe Mode or Recovery mode, the stuff on your Disk (or the drive itself) is damaged.

One other possibility is a Memory problem, except on the Mac Pro with Xeon processor that features error-correcting memory.

Thank you grant for your quick assistance

This is an image of what appeared to me after I restarted into verbose mode, a lot of lines passed through, but these were the last until it stopped.

I hope this can identify the issue

After doing many disk repair functions (and all the time it says the hard disk is OK) and some NVRAM resets, I was able to get into recovery mode and did a format for the Drive "Macintosh HD" just below Toshiba xxxx and then I headed to the main menu and chose to install el capitan directly from the internet (I could not risk getting back to my usb bootable installer) and from there during the download while watching the log move endlessly, the screen went off, completely and the fans went running again...

If I open the computer now, the grey loading bar comes, and then at 70 percent goes away to give me a no entry sign against a grey screen..

I am pretty sure there is something wrong with the app, its not just hardware because I checked my drive..

Now I cant even access single user mode, because it goes corrupt at the end now (check the image below)

I dont think we have official Apple shops here where I live, we only have resellers and some may have a support and maintenance team. But the way I know it, there is little or no skill or craftsmanship in whatever field or industry here, people here tend to break things more than they fix them, a very unfortunate reality..

Is there a way I can download the last el capitan from somewhere other than the app store? because every time I download it from there something fishy happens, like the file starts halfways (not from zero) and fails to download several times,.. I have a strong feeling this happens because of that file I have, its just mutated or something..

Is there anything I can do on my own from here, before I surrender my machine to strangers who might not know what they are doing??

My El Capitan install to an external disk was hanging repeatedly. Usually it would start the installation saying I had 17 minutes left and then, after hours, would hang between the 12 and 10-minute mark. Meanwhile I inherited a Macbook Pro 2011 and, after successfully installed El Capitan on it, was finslly able to successfully install El Capitan on the external (firewire) drive.

So why the difference? I'm not sure. Both machines were already running El Capitan (I wanted to also install it on an external drive to test a third machine). The machine that failed to install El Capitan to the external Firewire drive was a MacBook Air 2011 that was running :

• OneDrive
• Dropbox
• iStat Menus

And had software installed that may have made a difference:

• Chrome
• Firefox
• Office 365
• VLC
• iWorks
• Steam
• Mainstage

Hope that helps.

I had the same problem on the following model with the May 2016 El Capitan update:

MacBook Pro (Retina, 15-inch, Late 2013)

I was banging my head against the wall for days trying everything listed on this forum and others. I finally found a solution which is as follows - i really didn't' expect these issues with an Apple product:

1. First of all before attempting any software update, as always ensure you have a decent Time Machine Backup in case it all goes wrong.
2. Initially I was getting the update freezing about 75% though the final stage (black screen with apple logo an white update bar);
3. After reading on this forum, I created a bootable USB drive with the new El Capitan software installed (download form App Store etc - many posts on how to do this on the forum and web and the benefits of doing so);
4. After using the bootable USB stick to get to the OS Utilities screen, I then went into Disk Utility option and erased/formatted the Macintosh HD hard drive - name the drive as you wish it to appear when you hopefully install the new software update;
5. I then went into the OS Utilities menu options and shut down the Macbook Pro.
6. I turned the Macbook Pro on and pressed the OPTION key - this should bring up the drive selection option - I selected my previously created bootable USB stick drive;
7. Follow the installation instructions;
8. VERY IMPORTANT - on my machine i tried installing and turning File Vault option ON. Install froze. I repeated the process and ensured file vault was turned off when prompted in the set up procedure. This time I opted ot try the Migration option to copy files form my Time Machine backup - this all looked good until very last moment and again the update totally froze. This time with a grey background screen, after entering the user login details;
9. FINALLY - I repeated steps 4-7 above, this time I ensured file vault was off and didn't use the Migration option;
10. My update completed and the only drawback was having to manually reinstall various apps, files etc. This was just a simple drag and drop from the Time Machine backup folders onto the newly named hard rive on the Macbook Pro.

Exactly the same problem on my late 2014 MacBook Pro Retina.

2nd time now trying to get the install to work, both times its frozen at 90% of the install on the plain white progress bar.

It won't restart in Safe Mode however I can get it to boot to recovery mode (which is the new El Capitan format) so the first time I restored from a backup.

I created a El Capitan boot USB stick using Yosemite and the El Capitan download.

Then I rebooted holding the "option" key to choose the boot disk. From here I deleted my hard drive (i have a time machine backup) then installed a clean El Capitan using the boot USB.

Then once finished I migrated my data using the time machine back up when the installation was complete.

All working fine now.

IF there is no Hardware problem:

Installing a new version of Mac OS X starts with a Restart. This boots up a stripped-down version of the new, incoming software. The Installer in that new software then unpacks and copies files, getting ready for the complete version of the new software. When all appears to be going well, it begins moving files into position to run the complete new version at the next Startup. If that goes well it moves temporary files to the Trash and Restarts. This entire process typically takes 10 to 30 minutes (not counting the download time).

If it dies early in the process, especially before copying files into position, the Install process is intended to leave your original System in place, unmodified. So you should see whether you can still boot the old System before you take desperate measures.

If it dies immediately after the first Restart, your Mac may not be compatible with the new System, the download could be damaged, or there may be a Hardware problem.

Thanks Denbee, I was facing this problem and it is solved now. But my question is, after moving back the .kext file one at a time, what happens when I find the bad .kext file? What to do with it? Should I delete this file or keep it in the unsupported folder?

Thanks Denbee for your reply. In fact, I have 13 .kext files. I copied all into the unsupported folder and then moved back each one, one at a time, followed by a restart for each copy-paste. However, I did not find any corrupted file, and I moved all 13 files with 13 restarts and it seems my computer is working fine after this. Now I have 13 .kext inside the unsupported folder and 13 copied one outside the folder. Not facing the screen frozen issue like before. Should I leave it like this for now? Hope Apple will release a patch quickly.

Thanks very much Denbee. My Mac Air was stuck at 90%, was upgrading from snowleopard so didnt know if this would work. In safe mode I couldn't see any kext files and could not use "Suspicious Packages" because finder wasnt working. So i just deleted my Firefox Web plug-ins in Terminal and the install proceeded fine. Thanks for directing me here!

Hi

I had a similar problem, tried rebooting in safe mode etc but not joy. I have disconnected all usb devices and something now seems to be happening. I will let you if the upgrade makes it through to the end