Contribute
Register

macOS 10.12.3 Update

Status
Not open for further replies.
Can anyone help me with this? I updated my Z170M-D3H on my backup drive to 10.12.3 through the App Store and it kp's here:
Screen Shot 2017-02-22 at 6.16.12 PM.png
 

Attachments

  • IMG_6023.JPG
    IMG_6023.JPG
    2.5 MB · Views: 144
Updated without any issues...Hardware spec bellow:
CPU-i7SK - Intel® CoreTM i7 6700k 4-Core 4.0GHZ, 4.3GHZ Overclocked
Motherboard - Gigabyte GA-Z170-Gaming motherboard
RAM - Crucial Ballistic 64GB DDR4 2400 MHZ DDR4 RAM
Graphics card - 4GB MSI GTX 980 GAMING 4G Twin FrozrV
Hard drive (Solid State) - 500GB Samsung 750 EVO
WIFI-450 - 450Mbps Wireless N Dual Band PCI Express Adapter
BL-Dongle - Bluetooth V 4.0
Cooler - be quiet! Pure Rock Compact CPU Cooler, 4 Heatpipe, 120mm Silent PWM Fan
PSU-700W-EVGA - 700W EVGA 700B, 80 PLUS Bronze, SLI/CrossFire

strangely didn't have any NVIDIA issues upon re-boot...so hope this helps
 
I have updated to Sierra 10.12.3 via AppStore, everything is working fine except "Restart" (even while updating it stopped at reboot). Whenever I try to restart my hackintosh it cannot complete the cycle of system down and up. After completion of the system down process motherboard's fans and LEDs continue running and then no sign of system-up process to start.
Then I have to press "Reset" button of the PC to reboot.

Please help.

My system is:
CPU - Intel Core i5 6500
Motherboard - Gigabyte GA-Z170N-Gaming 5
RAM - Corsair 16 GB DDR4 3200MHz
Graphics card - On-board Intel HD Graphics 530
Hard drive - Boot - (NVME) - INTEL SSDPEKKW256G7 256GB / Data - (SHDD) - WDC WD10S21X-24R1BT0-SSHD-8GB
WIFI - BCM94352Z NGFF M.2 WiFi
 
@KnoGo My guess is that the system is unable to access the user account. After an update this could easily be permission related. Have had this happen once or twice before on genuine Macs. The screen shot would indicate that you are operating the machine from a single user account with admin privileges. I would recommend setting up an admin account and a separate user account.

It’s a safety strategy, in that operating as a user without admin privileges, I am alerted to process that need admin permissions and can abort them if I am suspicious about the activity. This has saved my bacon more than once. It also allows the possibility to "trouble shoot" by logging into a different "clean" account when not able to log in to the regular user account.

I also keep a separate emergency SSD which allows me to boot up my machine and rerun the update file, which has resolved situations like this in the past. Good to have a backup.


I'm installed SIERRA (10.12.0) on a new drive. I added two users, one with admin privileges - one without. Than I start the combo-update (10.12.3): Computer starts and boot until it reach the Login-screen. After login (type PW and enter) it hangs as bevore. It was the sam procedure...

My solution was: Boot with -x -v -no-zp
After reach the login-screen and login it works. I migrated the old account from the other hard disk.
 
Can anyone help me with this? I updated my Z170M-D3H on my backup drive to 10.12.3 through the App Store and it kp's here:
View attachment 237805
I got the same kernel panic after updating.

I'm not entirely sure if I left the original IONVMeFamily.kext in /S/L/E/ after using RehabMans script to generate the HackrNVMeFamily-10_12_2.kext and installing it to /L/E/.

Anyways, I did a backup, applied the update from the App Store and upon reboot I ended up with the same kernel panic as you:
Code:
com.apple.iokit.IOAHCIBlockStorage(295.20.1)
  dependency: com.apple.iokit.IOAHCIFamily(288)
  dependency: com.apple.IOStorageFamily(2.1)

Removing the IONVMeFamily.kext from /S/L/E/ finally did the trick and macOS did boot up again. I had to use the USB installer to remove the kext, since even the recovery wouldn't start (showed the stop sign).

Now I have kind of a strange state where it only boots with HackrNVMeFamily-10_12_2.kext. Maybe @RehabMan has an idea why.

I tried moving IONVMeFamily.kext back to /S/L/E/ and using the patch to generate the new 10_12_3.kext but my system won't boot using it (the same with IONVMeFamily in /S/L/E or without). If i remember correctly it shows the progress bar at startup but that stays empty (doesn't find the driver and thus no system data?).
 
I got the same kernel panic after updating.

I'm not entirely sure if I left the original IONVMeFamily.kext in /S/L/E/ after using RehabMans script to generate the HackrNVMeFamily-10_12_2.kext and installing it to /L/E/.

Anyways, I did a backup, applied the update from the App Store and upon reboot I ended up with the same kernel panic as you:
Code:
com.apple.iokit.IOAHCIBlockStorage(295.20.1)
  dependency: com.apple.iokit.IOAHCIFamily(288)
  dependency: com.apple.IOStorageFamily(2.1)

Removing the IONVMeFamily.kext from /S/L/E/ finally did the trick and macOS did boot up again. I had to use the USB installer to remove the kext, since even the recovery wouldn't start (showed the stop sign).

Now I have kind of a strange state where it only boots with HackrNVMeFamily-10_12_2.kext. Maybe @RehabMan has an idea why.

I tried moving IONVMeFamily.kext back to /S/L/E/ and using the patch to generate the new 10_12_3.kext but my system won't boot using it (the same with IONVMeFamily in /S/L/E or without). If i remember correctly it shows the progress bar at startup but that stays empty (doesn't find the driver and thus no system data?).

https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/
 
Okay, silly question (as I've done updates before) I plan on updating via the MacOS Combo pack.
Because I lost my last USB, should a make a bootable USB (as back up precaution) of my current build/previous version of
OS X Sierra 10.12.2 (16C67) - would seem to be the right thing, OR, bootable with the new 10.12.3? Seems to me if I have issues with 10.12.3 I'd want to be rescued by 10.12.2.
 
Okay, silly question (as I've done updates before) I plan on updating via the MacOS Combo pack.
Because I lost my last USB, should a make a bootable USB (as back up precaution) of my current build/previous version of
OS X Sierra 10.12.2 (16C67) - would seem to be the right thing, OR, bootable with the new 10.12.3? Seems to me if I have issues with 10.12.3 I'd want to be rescued by 10.12.2.

The latest version of Sierra should work fine if you want to recover a borked install.
 
Wow. I finally got the nerves to update to this. I downloaded the combo update, installed, rebooted, upgraded the NVidia drivers. rebooted.. Heaven. Only trouble I seem to have picked up is dying sound, when sound decides to go away, fading into nothing. Not bad. :)
 
Status
Not open for further replies.
Back
Top