Contribute
Register

[Solved] Security Update 2017-003 El Capitan

Status
Not open for further replies.
You can try reinstalling using the Recovery HD (if yours work).
Since the recovery HD doesn't work on my setup, I have tried reinstalling my second laptop's hackintosh with the USB I have created using the guide here. My files were still intact as it were before the 2017-003 update.


The recovery HD just hangs and eventually gets the color wheel.

To reinstall El Capitan, should I use the USB that I originally used to install El Capitan (when I created this Hack mini)? Should I use the directions from Ammulder's guide for installing El Capitan on the ga-h170n-wifi? (I followed his guide to create my hackintosh mini)

Edit: If I'm to follow Ammulder's guide for installing El Capitan, would I also have to follow his post installation instructions too?
Remember that I don't want to lose any of my data on my hard drive.
 
Last edited:
That would indicate to me that it's a BIOS issue with our machines. Since you swapped SSDs from machine to machine, I'd assume the config.plist remained the same when you did that?

Exactly, the config.plist remained the same.
I miss to add that I upgraded the BIOS with the hyper threading fix.
But the problem remains unsolved.
Sierra 10.12.6 works great, so I am happy with upgrade.
 
Hi! This is just what I did:
  1. On a MacBook Downloaded El Capitan from App Store :
    https://itunes.apple.com/at/app/os-x-el-capitan/id1147835434?mt=12
  2. Create a BootUSB with Unibeast
  3. Install El Capitan on the old one (Choose the same HD. You don't need to format it)
  4. After 18 min the System works again!
Just few adjustment for es: new NVIDIA Webdriver but I didn't lose any data.
I've to try again the Security Update 2017-003 but first a Time Machine Backup!!! ;)

EDIT: Security Update 2017-003 won't work!!!!
 
Last edited:
Could somebody move this thread to the OS X Updates forum? That's where I would look first, not in installation.
It was there originally, so I don't know how it got here.

Has anyone figured out a solution yet?
 
I've noticed everyone who posted has a gigabyte motherboard. I haven't done the update yet but was wondering if anyone besides voilet dragon who had success.
I'm actually having this issue on a laptop (Lenovo) so that might rule out that theory.
 
same here, on a HP laptop. but there will be definitely a common ground. are your CPUs broadwell, by any chance?
 
Got the same problem on my HP 820G2 with broadwell CPU. Real frustration with this update!
 
Status
Not open for further replies.
Back
Top