JohnZonie

Q: Security Update 2016-001 reboot hangs iMac

This is a late 2013 iMac running OS X 10.11.6. Installing Security Update 2016-001 10.11.6 requires a restart. The iMac hangs on this restart with a black screen showing a responsive cursor but not restarting. The only alternative is to power cycle the machine. I downloaded and reinstalled OS X 10.11.6 from the App Store. After installation, restart from the Apple menu worked fine and directly for 3 successful restarts. I then tried again to install the security update. When it initialed reboot, the machine again hung as earlier described. I power cycled the machine and, after completing restart, restart from the Apple menu was not successful, resulting in the same hang on restart as described above - black screen, responsive cursor.

 

The machine is running a 3.5 GHz i7 processor with 16 GB 1600 Mhz DDR3 RAM and a 256 GB SSD.

 

Any ideas on how to resolve this would be greatly appreciated.

 

TIA,

 

John

iMac, OS X El Capitan (10.11), Parallels for XP, Win7-64, Win8-64

Posted on Sep 11, 2016 11:52 AM

Close

Q: Security Update 2016-001 reboot hangs iMac

  • All replies
  • Helpful answers

  • by Eric Root,

    Eric Root Eric Root Sep 12, 2016 5:01 AM in response to JohnZonie
    Level 9 (70,176 points)
    iTunes
    Sep 12, 2016 5:01 AM in response to JohnZonie

    If the problem is still there, try booting into the Safe Mode using your normal account.  Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don't do them all at once. If that works, try running the combo update again. If that is successful, use the link below for the security update.

     

     

     

    Safe Mode - About El Capitan

     

    Safe Mode Startup – El Capitan.


    10.11.6 combo update


    Security Update 2016-001

  • by JohnZonie,

    JohnZonie JohnZonie Sep 12, 2016 7:32 AM in response to Eric Root
    Level 1 (36 points)
    Mac OS X
    Sep 12, 2016 7:32 AM in response to Eric Root

    Thanks for the reply, Eric. I already tried this. I can not restart even from safe mode (all peripherals disconnected)  once I run the security update. I get the same behavior when trying to restart from safe mode as described above: black screen, responsive cursor. The only way I can reboot from the Apple menu is to reinstall OS X from the App store. But once I try to run the security update, the system hangs during its restart process with the black screen. From then on, restart from the Apple menu fails.

  • by JohnZonie,

    JohnZonie JohnZonie Sep 12, 2016 7:38 AM in response to JohnZonie
    Level 1 (36 points)
    Mac OS X
    Sep 12, 2016 7:38 AM in response to JohnZonie

    Some other observations.

     

    1. I can log out my user and log in to a "test user" successfully.

    2. I can not restart from the test user - same black screen hang problem.

     

    I suspect the problem is between the log out process and the restart process.

  • by JohnZonie,

    JohnZonie JohnZonie Sep 12, 2016 7:53 AM in response to JohnZonie
    Level 1 (36 points)
    Mac OS X
    Sep 12, 2016 7:53 AM in response to JohnZonie

    Another input...

     

    Console, Diagnostic and Usage Messages shows the following every 2 - 3 seconds:

     

    9/12/16 7:51:46.620 AM ReportCrash[1163]: com.apple.message.domain: com.apple.crashreporter.writereport.crash

    com.apple.message.signature: lsd

    com.apple.message.signature2: UNBUNDLED ||| ??? (728.13)

    com.apple.message.signature3: 5736D3C545F3859F1C195CF21F2D0889

    com.apple.message.result: NO

    com.apple.message.summarize: YES

    SenderMachUUID: BAB8DC6C-25DC-37CF-9484-4DEF8FBB8555

     

    This may be a clue as a similar vintage iMac doesn't show this problem. Anyone have an idea how/where to look next?

  • by Eric Root,

    Eric Root Eric Root Sep 12, 2016 5:28 PM in response to JohnZonie
    Level 9 (70,176 points)
    iTunes
    Sep 12, 2016 5:28 PM in response to JohnZonie

    If you can restart normally, download the update from the link below, and then use it to install the update. When I tried the App Store update, I had the same thing happen to me. When I installed from the link download, it worked.

     

    Security Update 2016-001

  • by JohnZonie,

    JohnZonie JohnZonie Sep 13, 2016 7:46 AM in response to Eric Root
    Level 1 (36 points)
    Mac OS X
    Sep 13, 2016 7:46 AM in response to Eric Root

    Thanks but still unable to restart normally. I am trying to download 10.11.6 and install again. If successful, I should be able to restart normally. If so, then I'll try your download link.

     

    (I started the 10.11.6 download from the app store around 5 hours ago and still no action. This on a very high speed 120 Mbps connection.)

  • by JohnZonie,

    JohnZonie JohnZonie Sep 14, 2016 8:35 AM in response to JohnZonie
    Level 1 (36 points)
    Mac OS X
    Sep 14, 2016 8:35 AM in response to JohnZonie

    Was finally able to download 10.11.6 from the app store. After installing, running the security update still hangs restart. I can restart every time from Terminal using:

    sudo shutdown -r now

    but can never restart from the GUI wether a normal or safe boot.

     

    I have noticed a *lot* of messages on this community about the security update - apparently I am not alone.

     

    At this point, this issue seems unsolvable. Hopefully when Sierra comes out, it will resolve this issue and hopefully without a new set of issues.