HT205579: About the OS X El Capitan v10.11.2 Update

Learn about About the OS X El Capitan v10.11.2 Update
Clone100

Q: Are many people having a shut down problem with El Capitan? Do Apple plan to fix this?

Are many people having a shut down problem with El Capitan? Do Apple plan to fix this?

Posted on Dec 22, 2015 1:27 PM

Close

Q: Are many people having a shut down problem with El Capitan? Do Apple plan to fix this?

  • All replies
  • Helpful answers

  • by frazzm737,

    frazzm737 frazzm737 Dec 22, 2015 2:05 PM in response to Clone100
    Level 3 (896 points)
    iTunes
    Dec 22, 2015 2:05 PM in response to Clone100

    You need to describe your shutdown problem otherwise, we can only guess what you are talking about.

  • by BobTheFisherman,

    BobTheFisherman BobTheFisherman Dec 22, 2015 2:17 PM in response to Clone100
    Level 6 (15,242 points)
    Dec 22, 2015 2:17 PM in response to Clone100
  • by Clone100,

    Clone100 Clone100 Jan 11, 2016 1:47 PM in response to frazzm737
    Level 1 (1 points)
    Jan 11, 2016 1:47 PM in response to frazzm737

    Hello,

     

    Apologies for the abruptness of my first message and my delay in replying to your post.

     

    I upgraded to El Capitan on my MacBook pro 15' Retina and had a problem when I chose the Shut Down or Restart options from the Apple menu. The menu bar at the top of the screen would disappear and any open apps would close but then the process would freeze and my Desktop would remain open and empty. The computer wasn't frozen though and I could still access the dock and open apps, however I couldn't access the menu bar at the top of the screen. It's as if the shut down process just stopped half way through.

     

    Anyway, I reinstalled Yosemite and all was fine again and then after a few weeks I reinstalled El Capitan after speaking to Apple (primarily about another problem) and being vaguely told the shut down problem had been resolved. Unfortunately this does not seem to be the case and I still can't successfully run the shut down process after choosing it from the Apple menu. I can force shut down by holding the power button but have not completed a proper shut down or restart since the second installation of El Capitan. I'm running El Capitan 10.11.1 and have a pending El Capitan update in the App Store that I can't install as I need to do a restart at the end of the installation process but am unable to as the shut down/restart process just hangs.......

     

    After installing El Capitan the first time and noticing the issue I booted up in Recovery mode and tried to repair the disc using the Disc Utility. I have run a process to clean/repair the PRAM as instructed by Apple support (apologies my recollection of the process is hazy as it was a few months ago) and tried a few similar repair/clean-up processes as found on various Apple Support forums, but nothing has worked.

     

    I've seen that other people seem to have similar shut down problems since installing El Capitan but have not been able to find a definitive solution. I've also spoken to the reseller where I bought the Mac but they are none the wiser. Any help would be greatly appreciated.

     

    Yours hopefully = )

  • by John Galt,Apple recommended

    John Galt John Galt Jan 11, 2016 2:18 PM in response to Clone100
    Level 8 (48,515 points)
    Mac OS X
    Jan 11, 2016 2:18 PM in response to Clone100
    • Read Resetting the System Management Controller (SMC) on your Mac - Apple Support. Since you contacted AppleCare about the issue, presumably they had you follow all those steps already.
    • They should also have had you restart your Mac in "safe mode" to determine if the problems continued in that mode, or not.
    • They should also have had you log in while bypassing your User Account's Login Items.

     

    If they did not do all those things, write back for instructions. If they did, please describe the outcome of each of those three individual troubleshooting steps: specifically, did any of them result in normal shutdown, or not.

     

    If that does not help there are a couple more suggestions that may indicate a cause. Shut down your Mac and then start it by temporarily using "verbose mode" as described in the following: How to start up your Mac in single-user or verbose mode - Apple Support. When you start the Mac, various messages will appear and will not remain on your screen long enough to read. Some may seem to indicate errors or failures. That's normal. Ignore them and log in normally. When you shut down, various messages will appear again. If the shutdown sequence appears to stall on any particular message or messages, describe them. A readable photograph of the screen may be useful.

     

    If you shut down your Mac and it stalls after the screen becomes dark leaving no viewable messages you can describe, force your Mac to shut down again and then use Console to extract potentially meaningful system log entries. To do that you will need to examine your system.log file. Read below.

     

    Next time you shut it down note the time in your Mac's menu bar or some other accurate timepiece. Then, shut down as you have been doing and allow sufficient time for it to complete.

     

    Then, start the Mac the way you normally start it.

     

    Then, find the Console app - it is in your Mac's Utilities folder and looks like this

     

    Screen Shot 2013-10-15 at 1.28.39 AM.png

     

    You can find it by selecting Utilities from the Finder's Go menu.

     

    Open Console.

     

    If the log list column on the left is not already displayed, show the log list by selecting Show Log List from Console's View menu.

     

    Locate system.log in the list and select it. Many date and time-stamped entries will appear, hundreds of them, and you must find the entries relevant to your Mac's problem.

     

    To do that type the words bootlog in the Filter field at the upper right of the Console window:

     

    Screen Shot 2013-11-07 at 6.36.40 PM.png

     

    That will cause all log entries to be hidden, except for the entries containing those words. The last entry in the list will correspond to the last time you started the Mac. It will have a time stamp in the form hh:mm:ss later than the time you noted in the Mac's menu bar prior to shutdown.

     

    Make note of that exact time in hours, minutes, and seconds.

     

    Next: Clear the filter field by clicking the x in the above screenshot. It should then look like this:

     

    Screen Shot 2013-10-15 at 1.04.42 AM.png

     

    All previously displayed log entries will reappear.

     

    Next: Find the log entry that corresponds exactly to the time you noted in hours, minutes, and seconds containing the words "BOOT_TIME". You may have to scroll up or down a considerable distance. When you find that line, select it and drag your cursor up and prior to the entry corresponding to the approximate time you noted before shutting down the Mac. This will result in a selection of perhaps 100 lines or so.

     

    One or more of them, along with their time stamps, may reveal the reason for the unusually long shutown delay.

     

    Copy and paste those log entries in a reply. Please don't post thousands and thousands of lines.

     

    Most of the entries will be cryptic but will contain information you might consider personal such as your Mac's name. If you do not want that information to appear, delete or obscure it when posting your reply. Leave enough information so that the entries can be deciphered.

  • by Clone100,

    Clone100 Clone100 Jan 24, 2016 1:04 PM in response to Clone100
    Level 1 (1 points)
    Jan 24, 2016 1:04 PM in response to Clone100

    Hello,

     

    I tried the SMC reset and it didn't seem to make any difference. I can shut down and restart in safe mode but I'm not too sure about the logging on while bypassing my login items option. If I understood how to do this you need to also hold the shift key when starting up but for a shorter period of time the when triggering safe mode. I'm not too sure exactly when or for how long you need to press and hold the shift key so I'm not sure if the bypass step worked. If it did then I can't restart or shut down normally.

     

    I can't check the text after running verbose mode as I need to force shut down and no text appears on the screen.

     

    I tried looking at the console system log but when I choose the relevant bootleg entry and scroll up to the entry before the approximate time I shut down there are only 2 rows of text not hundreds.

     

    Next steps?........

  • by John Galt,Solvedanswer

    John Galt John Galt Jan 26, 2016 12:33 PM in response to Clone100
    Level 8 (48,515 points)
    Mac OS X
    Jan 26, 2016 12:33 PM in response to Clone100

    Holding a shift key as you log in (as opposed to starting your Mac) will temporarily bypass your Login Items, if you specified any.

     

    Or, just follow these instructions: OS X El Capitan: If you think you have incompatible login items

  • by Clone100,

    Clone100 Clone100 Jan 26, 2016 12:37 PM in response to John Galt
    Level 1 (1 points)
    Jan 26, 2016 12:37 PM in response to John Galt

    Hello,

     

    Many thanks. With your aid I finally sorted the problem out. It was the login items. I took a print screen of them, deleted them all, restarted the Mac and was able to shut down and restart without problems. I then added the few apps I actually want to start after logging in back, restarted as a check and all is well.

     

    Many thanks for your help!!

  • by John Galt,

    John Galt John Galt Jan 26, 2016 7:52 PM in response to Clone100
    Level 8 (48,515 points)
    Mac OS X
    Jan 26, 2016 7:52 PM in response to Clone100

    Great! Thanks for the update.

  • by Diamond Pete,

    Diamond Pete Diamond Pete Jun 24, 2016 11:08 AM in response to John Galt
    Level 1 (8 points)
    Mac OS X
    Jun 24, 2016 11:08 AM in response to John Galt

    I've been having the same Shut Down problem that you so graciously responded to above back in January 2016. As per your instructions I downloaded the Console file as you suggested and started looking back from the time the last entry prior to the Shut Down creating the blank screen with only the cursor present. The problem is I don't know how to interpret the prior system log entries. Any guidance would be greatly appreciated.

     

    Thanks.

     

    Jun 24 10:50:01 petersmac sessionlogoutd[422]: sessionlogoutd Launched

    Jun 24 10:50:01 petersmac sessionlogoutd[422]: DEAD_PROCESS: 95 console

    Jun 24 10:50:01 petersmac sharingd[252]: 10:50:01.055 : SCDynamicStoreCopyConsoleUser returned NULL

    Jun 24 10:50:01 petersmac sharingd[252]: 10:50:01.055 : SDActivityAdvertiser::consoleUserChanged: Stopping for user 501 on logout

    Jun 24 10:50:01 petersmac sharingd[252]: 10:50:01.055 : SCDynamicStoreCopyConsoleUser returned NULL

    Jun 24 10:50:01 petersmac sharingd[252]: 10:50:01.056 : SCDynamicStoreCopyConsoleUser returned NULL

    Jun 24 10:50:01 --- last message repeated 1 time ---

    Jun 24 10:50:01 petersmac fseventsd[48]: implementation_removed_client: did not find client 0x7fa3f2202bc0 for path = '/.docid'

    Jun 24 10:50:01 petersmac mdworker[391]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    Jun 24 10:50:01 petersmac mdworker[396]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    Jun 24 10:50:01 petersmac mdworker[394]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    Jun 24 10:50:01 petersmac mdworker[393]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    Jun 24 10:50:01 petersmac mdworker[413]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    Jun 24 10:50:01 petersmac mdworker[395]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    Jun 24 10:50:01 petersmac mdworker[414]: (ImportBailout.Error:1331) Asked to exit for Diskarb

    Jun 24 10:50:01 petersmac com.apple.kextd[47]: Warning: /Volumes/Mac HD/System/Library/Extensions: No such file or directory

    Jun 24 10:50:01 --- last message repeated 1 time ---

    Jun 24 10:50:01 petersmac com.apple.kextd[47]: '/Volumes/Mac HD' updating, delaying reboot.

    Jun 24 10:50:01 petersmac com.apple.kextcache[428]: Warning: /Volumes/Mac HD/System/Library/Extensions: No such file or directory

    Jun 24 10:50:01 petersmac com.apple.kextcache[428]: rebuilding /Volumes/Mac HD/System/Library/Extensions.mkext

    Jun 24 10:50:01 petersmac kernel[0]: hfs: unmount initiated on Mac HD on device disk3s2

    Jun 24 10:50:01 petersmac com.apple.kextcache[428]: failed to create cache folder /Volumes/Mac HD/System/Library.

    Jun 24 10:50:01 petersmac com.apple.kextcache[428]: Data error before mkext rebuild.

    Jun 24 10:50:01 petersmac com.apple.kextcache[428]: Error 107 rebuilding /System/Library/Extensions.mkext

    Jun 24 10:50:01 petersmac com.apple.kextcache[427]: /Volumes/Mac HD: no /usr/standalone/bootcaches.plist; skipping

    Jun 24 10:50:01 petersmac com.apple.kextd[47]: helper error while updating /Volumes/Mac HD (error count: 1)

    Jun 24 10:50:01 petersmac com.apple.kextd[47]: Warning: /Volumes/Mac HD/System/Library/Extensions: No such file or directory

    Jun 24 10:50:01 petersmac com.apple.kextd[47]: / is still busy, delaying reboot.

    Jun 24 10:50:01 petersmac com.apple.kextd[47]: Warning: /Volumes/Mac HD/System/Library/Extensions: No such file or directory

    Jun 24 10:50:01 petersmac com.apple.kextd[47]: /Volumes/Mac HD is still busy, delaying reboot.

    Jun 24 10:50:01 petersmac com.apple.kextd[47]: async child pid 428 exited with status 71

    Jun 24 10:50:01 petersmac com.apple.kextcache[431]: /Volumes/Mac HD - No such file or directory.

    Jun 24 10:50:01 petersmac com.apple.kextcache[432]: /Volumes/Mac HD - No such file or directory.

    Jun 24 10:50:01 petersmac com.apple.kextd[47]: async child pid 431 exited with status 66

    Jun 24 10:50:01 petersmac com.apple.kextd[47]: async child pid 432 exited with status 66

    Jun 24 10:50:33 localhost bootlog[0]: BOOT_TIME 1466779833 0

     

    The computer is an iMac late 2012 vintage with iCore 7 chipset running at 3.4 GHZ. 16 MB RAM and an external firewire HD (Mac HD) running off one of the Thunderbolt ports via an Apple Firewater Adapter. Most of the time the Shut down menu option will not work, but on 1 or 2 rare occasions it will.

  • by Eric Root,

    Eric Root Eric Root Jun 24, 2016 12:55 PM in response to Diamond Pete
    Level 9 (69,813 points)
    iTunes
    Jun 24, 2016 12:55 PM in response to Diamond Pete

    You might want to consider starting a new discussion. Since this one is marked solved, less people are likely to look at it. You can link to this one.

     

    Do you have an application called Diskarb installed? Try quitting it before shutting down.