Macbook Pro won't shut down after installing Yosemite

John- I had similar Safari video issues, but not that bad. Also, I booted into Safe Mode, and my screen was doing some weird stuff... horizontal lines moving up the screen, etc. screen flickering when moving the mouse, like a re-draw problem, etc. I'm trying to forget about Yosemite for a night 🙂 Have some work to do, then tomorrow driving home for big Patriots/Denver game. Monday I will resume my Yosemite bugs.

Bryan

I have noticed that Finder tries to quit, but it can not, the dot in the dock still on. it also cannot be quit nor force restarted, and if attempted to open anything that actually uses Finder (list of downloads etc) then it wisely says that Finder has been shut down. Legacy MBP 2012 here.

Not wanting to rustle any feathers, just a FYI.

One of my 'Mac' machines is a PC running 10.10, based on a Gigabyte Z87x-ud4h motherboard i5 4670k CPU, I've been getting the exact same issue as you real Mac users/owners have been getting, this rules out in my instance at least real Apple Hardware problems + Yosemite, but just a Yosemite first Public Release bug, and dock related quite possible.

The reproducible error has the Dock drop down and freeze before going to black with spinning progress graphic, or with faded background, I have to hard restart the PC. No error messages on succesful reboot.

Just a FYI !

This has also happened to me after installing Yosemite on macbook pro.

It was ok for a few days. Today I went to turn on and got the flashing folder with the question mark- meaning it can't find an OS.

I restarted holding alt/option key down and get to an "internet recovery" option.. I didn't get far in this as I wasn't at home at the time- but I got to a few options for retoring Mavericks- download from Apple, use Time Machine to install a previous version, disk repair.. etc.

I left it there until I make it home to finish process off..

I was also seeing a film.. when I left the cinema my bag almost had steam coming out of it! My laptop was super hot.. I had thought I shut it down but it won't shut down, even when holding down on/off button. So I am waiting now until the battery is dead again.

Such a pain! I will restore Mavericks until this issue is solved I guess..

I was encountering this problem on a 2013 rMBP, FileVault not enabled. Per StructureMedia's suggestion, I used Disk Utility to run Verify Disk on my system disk partition, which did find a problem. Repair Disk on the system disk (which required a reboot, holding ⌘-r to invoke the recovery partition) appears to have fixed my 100% repeatable hang on shutdown. I didn't bother with verify/repair permissions.

My problem turned out to be 'Little Snitch' 3.5 (4228) that has issues with OS X Yosemite 10.10, removed this app and system now stable and reboots shuts-down normally. See thread below.

Case true with 'real' MacBookPro Mid 2014 and Hack.

http://forums.obdev.at/viewtopic.php?f=1&t=9417&sid=bd705683dd858b7b490f3c6baccd 3c12

I was having an issue where I could not log out, restart, or shutdown and the OS would hang when I tried updating from 10.10 to 10.10.1.

The shutdown process would start, my apps would close, the bar at the top would disappear but then it would hang. I could still see the dock and I could open some apps except for Finder which said something like it was closed and no longer available (even though the dot in the dock indicated it was open). I tried verifying permissions and also verifying the disk but they both checked out okay. Additionally, I could shutdown and restart via command line but it did not cause the Software Update to initialize upon reboot. Furthermore, some of the apps that I have on startup did not open as usual when I had to hold the power button down to reboot. Another strange thing that I noticed was that in the App Store, I now had multiple (~3) entries saying I installed 10.10.1 when it never actually installed at all and it still was giving me the original option under "Available Updates" to update/restart the OS.

I followed Furi0us.Bee's advice about the wallpaper and it solved all the problems I was having and I was able to successfully update by just restarting after his fix.

MacBook Pro (Retina, 15-inch, Late 2013)

2.3 GHz Intel i7

Intel Iris Pro

NO FileVault

Just updated to 10.1

Prior to updating I repaired permissions, disconnected all peripherals and just for good luck I switched the wall paper to a default Apple wallpaper.

The update executed with no problems. Installed 10.1, computer rebooted itself as normal, I repaired permissions and was able to reboot with no problem. Switched my wallpaper back to my wallpaper and was able to reboot as normal.

I ran into the problem again when I reconnected my peripherals (3 external HD's, an external monitor, and speakers connected via audio jack), put my machine into clamshell mode, which is how I work at my desk, and tried to reboot.

Same issue, black screen with cursor.

It's cool that my machine will now boot when disconnected from all of my crap, but it ***** that it still won't reboot in clam shell, which is how I use it the most.

Whatever, I'll just wait for it to be fixed. I've been with Apple for a lot of years and, I have to say, I'm just kind of getting tired of it. They aren't what they used to be.

*updated to add computer model*

2.6 MBP (Retina, 13 inch, Mid 2014)

Thanks for your feedback James, i wonder if this issue will be fixed by clean re-install of 10.10.1, i will check it tonight and will get back here with results. If someone also got this fixed or not please don't hesitate to reply here.

The not closing down problem has from from my iMac this last couple of weeks. Not sure what cured it but I have a custom wallpaper and have not changed it to default. I have run permission fixes and cleared out some old software. What I think was causing the problem, not totally sure, but I had Avira Free Anti-virus for Mac installed and I did see it show up in a crash report so I removed it.

Just made clean re-install with PRAM reset of 10.10.1 on my new MacBook Pro 15" retina (+discrete video). Apple fixed NOTHING about this issue and many others. Still system freeze on reboot and still have crazy graphic glitches in many places.

For those with this problem and using FireWire drives, try this. When you get the endless spinner, shut off your drives. Seems Yosemite has a problem with ejecting FireWire drives. Along with not being able to sleep them, allow them to spin down or the myriad of USB 3 issues carried over from Mavericks.

The moment I shut down my drives, all is well. Tried ejecting them before a restart or shutdown and all went well.

I guess I have to address this to Apple users as we are so often reminded that Apple does not monitor these forums. So, we are seeing yet another example of a core process, that worked fine for 30 years, is now beyond the ability of Apple's talented employees (I assume there are still some around with technical ability) to copy code which once worked fine.

The only thing that work here is the "Log-out" method and then shut-down or restart. Otherway I get stuck at the black screen and have to press the PowerBt (that I hate to do so)...

Hope Apple gets this fixed ASAP.

iMac 27, Mid2011

After a clean install of 10.10.1 on my 17" MacBook Pro, I experienced the same problem as others (black screen, cursor still working).

I have managed to solve this issue by doing the following:

1. Reset the PRAM.

2. Reset the SMC.

3. Reinstall Yosemite.

PRAM is reset by holding down P, R, Shift and Command buttons when powering on.

SMC is reset by pressing Control, Option, Left-Shift and Power Buttons at the same time when powered off and plugged in (or power button with no battery or cable if battery can be removed).

If you're unsure, there are videos on YouTube on how to reset those things too.

not sure if I needed to reinstall after doing the two resets, but i did that anyway because the screens during the install were corrupted the first time through. After the resets, everything seems much better. Hope this helps someone else!

I don't really think it's fixed for you because this bug comes back eventually: after reboot, after re-installing some App or installing update from Store etc. I've used the same steps and after 1-2 days this issue appeared again.