Macbook Pro won't shut down after installing Yosemite

Hi,


I just finished installing Yosemite on my Macbook Pro. It's fairly new, the last version with a DVD drive but without retina display (I bought it in May 2014 and it's my first Mac).


I installed Yosemite, updated all my applications from the App Store and tried to shut it down from the Finder but the screen just freezes on a black screen wth the pointer showing and then I to shut it down using the power button which I hate doing.


I turned on FireVault after set up and that is busy encrypting could that be causing this? I did check online and it says you can put your Mac to sleep or shut it down while this is happening, but I haven't been able to. Any tips would be great.

MacBook Pro, OS X Yosemite (10.10)

Posted on Oct 18, 2014 8:37 AM

Reply
122 replies

Nov 30, 2014 4:00 PM in response to Ninnie_89

Same problem, couldn't reboot or shutdown after the 10.10.1 update.


I originally installed 10.10.0 as a clean install (reformat of the drive). I do recall finding it odd after 10.1 update that I my custom desktop picture was reset back to the Yosemite default. That never happened to me ever with a Mac OS update. But didn't think much of it. After I went back to my custom desktop setting, that's when rebooting/shutdown stopped working. Also funny, Guest login activated itself for me after the 10.1 update. Never turned it on before. Strange. I turned Guest login off and it turned itself back on again. Resetting the default desktop did work for me initially. However, it quickly stopped working. After experimenting with fixing permissions, resetting PRAM, disabling all background processes, nothing helped. Turning off FileVault appears to have fixed the issue.


While resetting the default desktop background appears to work for some. I think that's a symptom and not the root case. Maybe there's a set of system files that are not encrypting/decrypting properly which makes them fall back to their pre-decrypted state? Perhaps some system preference data is not getting saved properly when FileVault is active in 10.10.1.

Dec 3, 2014 5:40 AM in response to ricardo.barcelona

Hi,


My system log was full of:

com.apple.xpc.launchd[1] (com.apple.mdworker.bundles[8023]): Could not find uid associated with service: 0: Undefined error: 0 501


I searched files for user (id 501, last number at the end of the log entry), and I "corrected" the owner (setting to root, or myself, depending on neighbor files).

And my Mac shutdown the right way twice. Seems to be fixed again, but I'm not willing to play with wallpaper or Filevault settings.

Dec 16, 2014 6:41 PM in response to Furi0us.Bee

Oh..my god...that changing wallpaper back to default trick really worked!!! After that I change the wallpaper back to my custom wallpaper, the computer shuts down normally.. although it's kinda slow and the dock disappears with a line of shadow at the bottom of the screen... anyway, thanks for the trick. It saved me a lot of time. I have no idea what I did cause such problem

Dec 23, 2014 11:10 AM in response to Warflow

I 've got a brand new MacBook Retina 15" and have the same problem since the first time I turned it on. Sometimes This black screen appears, sometimes not.


On top of that, last time i turned it on, a choice of two users (in stead of 1) appeared at the log in. The administrator user and the Guest User. Is it normal? I did a restart and the Guest User didn't appear again. Then the screen went black again (dark with white cursor).! What is happening?

Jan 7, 2015 7:30 AM in response to Ninnie_89

Hey All,


First off, running Yosemite on my MacPro 2012.


Verifying permissions on the start-up disk, found a 'crap-ton-o' issues.


Repaired permissions... this completely solved my issue of getting stuck on the black screen with the spinning grey wheel after shutting down and closing all open programs normally.


Hope this helps for others having the issue.

Jan 12, 2015 10:13 PM in response to Furi0us.Bee

FB,

i was very excited to encounter your ideas about how to fix a similar problem I was having. I (stupidly?) decided to enable firevault on my mid 2013 Air

running Yosemite today . initiated the process on 17% battery, was Told to connect to power source but I noticed that making the connection didn't change the phrase on the screen that should have recognized I had connected it (or something,i was not paying close attention at the time). Stupidly again, because i approach apple products with the false expecitation they will 'just work', i went ahead with generating recovery key etc. On restart, ive now had 10 hours of continuous black screen with pinwheel spinning. Not knowing if this was part of the "patience" required I waited a very long time. finally, decided to restart in safe mode, which was sluggish and just as my custom wallpaper would appear it would be polluted by flashes of horizontal bars and static but would load. Each time I would return to the blank screen after running safe mode. But I've been fiddling with my wallpaper for months and had it changing every 30 minutes. after reading your post, I went in again and ONLY changed the wallpaper (deleted new files that I had added and returned it to the Yosemite image). And just like that, I had a normal restart, fire vault appearing to BEGIN encrypting (goodbye 10 hours of waiting, hello 14

more), and its now the recognizing power appropriately. Thank you to you and to everyone participating in this discussion. Forgive me if a few pages down this is all been clarified and refined. Id say if you've come this far and youve been adding wallpaper files just try this fix in safe mode before wiping or Reinstalling anything! - cheers from NYC

Mar 18, 2015 3:17 PM in response to Ninnie_89

Hello everyone

The same problem exists for me as well on rMBP early 2013. After i upgraded to Yosemite the issue started to appear. I did a clean install and that did not help as well. The problem gets worse when i plug in an external USB 3 hard disk or when i plug my thunderbolt display. I also performed the permissions and disks checks the problem returns. I have concluded though that if i do not plug any drive and perform normal work the laptop shuts down normally. If I plug a disk most likely will not shut down.

By the way is there a keyboard shortcut to force shut down? the reason i am asking is because i use the laptop on a dock with a thunderbolt display and external apple wireless keyboard which does not have the power button.

Let's hope that there will be a solution some time soon

Mar 25, 2015 4:08 PM in response to Ninnie_89

I had this problem on an "Early 2009" Mac book, running Yosemite. My problem was pretty easy to solve and it may apply to some others; I had installed Kaspersky Antivirus (I know Macs don't get viruses...Wrong). Anyway, I uninstalled Kaspersky and my Mac shut down just fine. Later I tried Bitdefender Antivirus and the same thing happened. Anyone having the shut down or restart issues should check for any third party applications which are probably causing the problems, especially any antivirus software. Hope this helps someone.

Mar 28, 2015 9:59 PM in response to Ninnie_89

logout/restart didn't work.

command+r on start verify/repair permissions on system drive fixed it. the log revealed wrong permissions 0 vs 80 for my HP 6500 wireless printer so my driver did it in my case. Shutdown worked multiple times perfectly now.

Very likely apple has an issue at the kernel level. The OS itself should protect against wrong permissions on fundamental services. I see how this can actually comeback since in Unix permissions change based on what rights the current user has that executes these files. My printer was working before and is working now so why would the shutdown services hang if some files/scripts don't have the correct permissions. shouldn't shutdown operate at a more super user like level. this is just a bug and it seems a nasty one in the kernel. I can see how any software you install may do this. some people even report custom desktop settings causing this for god sake...

by the way I am sick of wi fi issues before maverick pre 2012 every thing seemed fine with WiFi then all of a sudden I observe that they have introduced some sort of crazy soft low power mode which I think may put WiFi to sleep. I tried a caffeinate command someone recommended which apparently removes the stupid sleep mode. after that it seemed to work until Yosemite came and back to WiFi issues, its not my router since I own multiple other systems and no issues, Mac will disconnect randomly, its the most annoying issue, and it causes other kernel issues...my mac (s) will not be stable when this happens finder is weird..... I just got tired of it and ran cables to my macs..no more WiFi issues. these are just bad bad bad decisions by their os and qa groups. I am sure these issues must have been detected and discussed at apple. way too many ppl complaining about this for very different reasons. apple pls release stuff slower just fix these issues. reliability over amount of features plsssssss!!!!! Steve jobs would have never have released these pieces of junk (mavericks/Yosemite)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Macbook Pro won't shut down after installing Yosemite

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.