Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Not fixed for me....

I have a mid-2010 13" MBP. Was hopeful after reading a few posts earlier today, but after updating the slow shutdown persists for me.

First shutdown after update was quick, but jumped up again on the next one.

So, looks like it's back to editing the appleevents plist for me.
 
Use your machine between tests. Give OSX time to bog down first.

Did so this morning and still 3 second shut down twice. Will keep on checking later for you. Good luck with yours ;)

Edited: OK Krazy Bill, went back up to 20 seconds again after some use. Not good :( :mad:
 
Last edited:
no change for me.

My 2012 MBA had no improvement on shutdown time.
Even from login screen; shutdown is between 15-20 sec. spinning wheel as before.

whatever, back to the genius bar who told me to wait for 10.3 for my battery drain (20%) overnight while sleeping, and shutdown.

battery drain last eve, 9 hours- 17%.

so glad it will last me 4-5 days while sleeping vs. advertised 30. /s
Taking it back, they can provide a new machine at this point, for 2200- they can give me one that works as advertised right on the box.
 
It's sad that Apple can't fix their crap. And this took 5 months.

It is rather frustrating that my brand spanking new SSD quipped $3k 15" MacBook Pro Retina takes longer (20 seconds) to shut down after "updating" to 10.8.3 vs the (15 seconds) it took to shut down while running 10.8.2.

It's seems that Apples getting worse not better when it comes to shut down times.
 
It is rather frustrating that my brand spanking new SSD quipped $3k 15" MacBook Pro Retina takes longer (20 seconds) to shut down after "updating" to 10.8.3 vs the (15 seconds) it took to shut down while running 10.8.2.

It's seems that Apples getting worse not better when it comes to shut down times.

How does this impact your daily use of the machine?
 
How does this impact your daily use of the machine?

Ever watch your battery getting depleted by 10% in sleep mode over the course of a day? How about rebooting into multiple OS's many times throughout the day?

You know... some of you guys just need to stop scratching your heads and realize that even though certain things have no bearing on your day-to-day workflow, they definitely affect others.
 
Slow shutdown is still present on my mid-2012 15" MBP. Looks like we'll have to wait til OS 10.9 for this problem to be solved. :rolleyes::mad:
 
type these commands into the terminal window one by one and right after terminal repair permissions in the disc utulity

sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.securityd ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.mDNSResponder ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.diskarbitrationd ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchAgents/com.apple.coreservices.appleid.authentication ExitTimeOut -int 1
 
How does this impact your daily use of the machine?

It does affect if you use your laptop for business needs when traveling. Sleep mode drains my battery on a significantly basis.

So if you need to wait half a minute 10 times a day until the shutdown is finished believe me you can get quite annoyed. Additionally your colleagues running Win 7 start bashing you when seeing the shutdown performance - and that's probably the hardest part as it used to be the other way round!
 
It does affect if you use your laptop for business needs when traveling. Sleep mode drains my battery on a significantly basis.

So if you need to wait half a minute 10 times a day until the shutdown is finished believe me you can get quite annoyed. Additionally your colleagues running Win 7 start bashing you when seeing the shutdown performance - and that's probably the hardest part as it used to be the other way round!

I just cannot, cannot get over how Apple thinks this is acceptable. 5 months for this release and they didn't sort it. Is that not caring?
 
It does affect if you use your laptop for business needs when traveling. Sleep mode drains my battery on a significantly basis.

So if you need to wait half a minute 10 times a day until the shutdown is finished believe me you can get quite annoyed. Additionally your colleagues running Win 7 start bashing you when seeing the shutdown performance - and that's probably the hardest part as it used to be the other way round!

Believe it or not, that was one of the main reasons I reverted to SL. However, what PC running any version of windows shuts down more quickly? Based on my experience with XP at work (takes forever to boot up and shut own) and 7 at home (boot camp on an iMac), even ML at its slowest runs rings around them.
 
Believe it or not, that was one of the main reasons I reverted to SL.
Considered this myself but ML has too many features a lot of us are dependent on now. (iCloud, Notifications, Messages, Airplay). Plus, I've installed so many 3rd party hacks/tweaks to minimize the iOS glitz and glitter of ML that it's tolerable right now...

... except the sluggish shutdown time.
 
Believe it or not, that was one of the main reasons I reverted to SL. However, what PC running any version of windows shuts down more quickly? Based on my experience with XP at work (takes forever to boot up and shut own) and 7 at home (boot camp on an iMac), even ML at its slowest runs rings around them.

You probably have a ton of crap running in the background on Windows. My old 2005 PC running Win7 would shut down in 3 seconds max. And currently in bootcamp and emulation on my mini, it shuts down in less than 2.
 
type these commands into the terminal window one by one and right after terminal repair permissions in the disc utulity

sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.securityd ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.mDNSResponder ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.diskarbitrationd ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchAgents/com.apple.coreservices.appleid.authentication ExitTimeOut -int 1


Thanks razmarino - works like a charm. :cool:
 
You probably have a ton of crap running in the background on Windows. My old 2005 PC running Win7 would shut down in 3 seconds max. And currently in bootcamp and emulation on my mini, it shuts down in less than 2.

Pardon my skepticism, but I've owned a lot of different windows machines over the years and did all kinds of stuff to make sure only a minimum of required processes were launching at startup and running in the background and have never seen a windows machine shut down that quickly, ever. Seriously, a forced shut down takes at least 2 seconds to shut down.
 
Pardon my skepticism, but I've owned a lot of different windows machines over the years and did all kinds of stuff to make sure only a minimum of required processes were launching at startup and running in the background and have never seen a windows machine shut down that quickly, ever. Seriously, a forced shut down takes at least 2 seconds to shut down.

If I include the time it takes from the moment I hit "shut down" and Windows exits the desktop, add 4 seconds more. I'm specifically referring to the "Windows is shutting down" screen which is a more accurate indicator if I wish to compare with the hanging grey screen we see in ML.

In either case, it's shameful to see the grey screen in ML hang like that. Oh, how I miss SL and its split-second blue screen.
 
In either case, it's shameful to see the grey screen in ML hang like that. Oh, how I miss SL and its split-second blue screen.

Amen. I was waiting for 10.8.3 to see if it fixed the slow shut down but I guess I'll wait for 10.8.4 or 10.9, before I try to let go of SL again.
 
type these commands into the terminal window one by one and right after terminal repair permissions in the disc utulity

sudo defaults write /System/Library/LaunchDaemons/com.apple.coreservices.appleevents ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.securityd ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.mDNSResponder ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchDaemons/com.apple.diskarbitrationd ExitTimeOut -int 1

sudo defaults write /System/Library/LaunchAgents/com.apple.coreservices.appleid.authentication ExitTimeOut -int 1
I'm thinking of giving this a try, but how would I undo it later on? Also, will these commands have any other effect on my Mac (other than fixing the slow shutdown)?
 
Based on my experience with XP at work (takes forever to boot up and shut own) and 7 at home (boot camp on an iMac), even ML at its slowest runs rings around them.

Seems like your having two problems than - slow shutdown times with your Mac and PC :D

I'm putting my hope on 10.9 as I'm very disappointed since the problem wasn't fix up until now. A lot of people including me uploaded tons of logs via the Apple Bug Reporter after being asked by the Apple developers. But besides the tickets being closed as duplicates nothing really happened during the last five month.
 
Last edited:
same issue here, and i have a SSD.

About 10.9, you can be sure about one thing: it will definitely be slower, not faster. Apple is taking care of iOS stuff now, they don't care bout osx users anymore. Face reality... Now with non upgradable new macbook lines, I may switch back to windows in about 5 years, when current upgradable macbooks won't be available anymore....

Apple is the new microsoft. Who is the new apple for laptops? we need one!!
 
A lot of people including me uploaded tons of logs via the Apple Bug Reporter after being asked by the Apple developers. But besides the tickets being closed as duplicates nothing really happened during the last five month.
Correct. Which led me to believe they were going to fix this issue. Not so.

This tells me they had a "ton" of critical issues to deal with in 10.8.3. and the shutdown lag, though inconvenient was not detrimental to users. Therefore it falls to the bottom.
 
This tells me they had a "ton" of critical issues to deal with in 10.8.3. and the shutdown lag, though inconvenient was not detrimental to users. Therefore it falls to the bottom.

Yeah, probably, but I'm not quite sure to be honest.

Either still a lack in manpower after the massive growth due to the introduction and success of iOS, a shift in focus (again iOS), your explanation above or missing emphasis on quality (yes, also Tim Cook) from the rearranged management.

I still can't understand that a small but widely spread bug with thousands of posts is being ignored. That's just bad publicity which could have quite easily been avoided.

ML still is my favorite OS (started with 10.3), so bashing is not my intention.
 
Considered this myself but ML has too many features a lot of us are dependent on now. (iCloud, Notifications, Messages, Airplay). Plus, I've installed so many 3rd party hacks/tweaks to minimize the iOS glitz and glitter of ML that it's tolerable right now...

... except the sluggish shutdown time.

Going back to Snow Leopard would be counterproductive. On my iMac shut down time is improved considerably with final 10.8.3 release although it's not as good as on Lion 10.7.5 (same iMac).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.