Q: After installing mavericks, the iMac will not wake from sleep properly (at all)

I Tried a new approach to the verify disk permissions from info on another post.

So far so good (fingers crossed). My computer is a 21.5-inch, late 2009 iMac. 

I was previously unable to wake from computer sleep 90% of the time. 

I could occasionally wake from sleep if it had just gone to sleep within minutes.

I'll let you know if it isn't a long term fix.

1. Shut down computer, unplugged power cord for 30 seconds.
2. Plugged in waited 10 seconds
3. Held down alt/option key and then booted up to be able to boot fromRecovery partion.
4. When given a choice selected boot from OS X recovery partition.
5. Selected disk utility.
6. Verify disc permissions
7. Repair disc permissions
8. Reboot
9. Went to system preferences/Energy saver and selected restore defaults to test ability to wake from sleep.

Also there is no power nap option on this vintage IMac.

Current settings to test :

• Computer sleep 10min
• Display sleep 10min
• Put hard disk to sleep when possible selected
• Wake for network access selected
• Start up automatically after a power failure Not selected

Well I spoke to soon...  Still not waking up after prolonged sleep

I see a slightly illuminated black screen and an occasional momentary view of the curser moving across the screen also. I am also getting annoyed with this. I sure wish I would have postponed my migration until 10.9.1 or .2 or what ever it takes comes out....

I am also having audio output problems. Not the Apple role out I was expecting from watching the Apple keynote video.

My iMac was the most stable computer I have ever owned up until now.

I am so thankful I didn't upgrade my mother in-laws iMac from 10.6.8 that I recommended she get.

I use MacBook Air 13 (2013 version) and after upgrading to Mavericks, got the same problem while on battery. I simply unmarked "Put hard disks to sleep when possible" option and my problem appears to have gone away for now. Of course, will update if it comes back again.

I set Computuer Sleep at 'Never' and this has worked for me. My Display is still set to sleep at 15 min and Hard disks set to sleep when possible. Not saving any energy of course, but wake up in the morning is much swifter!

Unfortunately Sosby although it fixes (or stops) the issue it is not really a true solution as although I do not really care about saving energy etc keeping your mac in a pusedo awake condition leaves the components still fully powered and thus reducing their overall lifespan as even with the hard disks powered down you are still supplying every other component with full working power and they will just be burning themselves out over a shorter period of time.

Many thanks though for offering what we all hope is a temporary solution until Apple resolve this issue and at least as you say it is a working solution for now.

As it happens just prior to this post my iMac once again locked up and required a 13 amp reset - the next thing that I will be looking into is turning off App Napping - not the power Nap but the process that sends dormant apps to a low process queue - it would not surprise me if this is causing memory leaks that could be stopping the macs from waking up correctly due to the saved ram state changing from awake to sleep and back to awake modes again - here is how to turn this off for individual apps:

Turn off App Nap

To give you more battery life Apple turns off apps when it thinks they are not doing anything. That's clearly a good thing, but if you want to override this feature you can turn it off if the app supports it. To do so find the App in the Applications folder and then right click to Get Info. Tick the box that says "Prevent App Nap".

Hope this helps.

I use a 2007 macbook pro and have had the same issue.  I did a completely fresh install of Mavericks without installing any 3rd party apps and let it sleep overnight, but still had the same problem.

Hum... Makes me wonder if you walked in and purchased a new Mac with OS X loaded if it would have the same  sleep issue?

If not... why?

Mr Mo-Fo, I take you point about everything remaining powered up, it is very unsatifactory. Let's hope Apple clear this up in an update - the resets just do not work for imac.

Ok, I can confirm now that for my MacBook Air 13, unmarking "Put hard disks to sleep when possible" worked.

This is getting interesting. I use a 2007 macbook pro.

Disabling the “put hard disks to sleep” setting did not fix the problem for me.  Also, changing the setting for the computer to never sleep as Sosby did not help because macbooks will automatically sleep upon closing the lid.

Now, even crazier is it is happening on my Snow Leopard (SL) I have on another partition.  I also did a fresh clean install of SL on a new partition and the problem is occurring.

Each of the 3 OS's have some user folders symlinked to another drive, so they share downloads, documents, pictures, movies and music folders (although only Mavericks access/uses iTunes), but they each use their own ~/Library folder so I don't think that is the problem.

I've tried resetting SMC and PRAM multiple times.  I don't know what else to try.

Hopefully Apple will come up with an answer soon.

I am having similar problems.  I installed 10.9 the first day or two after general release.  Shortly after that I started not being able to wake up the computer sometimes.  Particularly in the morning when I had not been on it for an extended time.

A couple of days ago I called AppleCare.  They did not seem to be aware of any issue like this with 10.9 (at least not yet :-) ).  They had me go through the SMC and NVRAM/PRAM resets.  We then tried setting sleep times to 1 minute and seeing what happened.  With just a short period of sleeping it woke up OK and the call was left open for follow up if the problem had not been resolved.  (The indication seemed to be a next step if needed might be a "hardware evaluation".  I am not clear if that involves taking it into an Apple Store.)

I am still seeing the problem however, and am currently trying different combinations of energy and screen saver settings.  (I thought with never sleep set for everything I did not see the problem at one point early on).  I have just done the Permissions check and repair and will continue to experiment to get better evidence.

On the permissions it was interesting that I got a long list of complaints in the Applications/iBooks area (which is new or changed in 10.9, right?  I also got some compolaints in the Printers/Canon/IJScanner area but that may be unrelated.  One other complaint during the verify was:

Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.

I have no idea what to make of that, but it is not out of the question that it could be related.

Hey Bob,

Your comment that “ They didn’t seem to be aware of any issue “ with sleep. Surprises me a little. I would think Apple would have people scouring these support communities… but I have been wrong before.

I guess I wouldn’t be surprise me that one AppleCare tech didn’t know about it.

I do wonder if Apple is aware and just not talking about it, for whatever reason?

Because my computer is late 2009 I don’t feel like calling and paying to get the advise on a SMC reset; I would like to call and let Apple know I’m having a problem along with may others, this post is approaching 2600 views currently.

"They" refers to what the AppleCare tech reflected.  I have not found a way to inform Apple formally of a problem, or check on what they are aware of, and I have often seen comments that suggest the forums get little attention.  I beleive they do have some other mechanisums in place to gather information that are not always obvious to users.  Example, digging down on my iOS7 iPhone I found logs that get reported to Apple showing information like app crashes (I beleive you click somewhere to allow anonymous sharing of info and I think that is the sort of thing I found).  In the iPhone case there are many thousands of apps, and I guess it helps Apple to keep things under control to know when one is having problems - in that case the app developers and the distribution of apps are tightly controlled by Apple - not so much with OS X, but maybe there are similar monitoring aspects to help Apple be aware of what is going on.