Sleep Wake Failure with High Sierra 10.13.2

I have sent in 2 different system diagnostic downloads from my computer and after the second one the senior tech that was working with me said that the engineers had discovered the problem and were working on a fix. That was on Dec. 31, 2017. I haven't been able to contact that tech since. I can't believe they released High Sierra with this many problems. If they ever do get it fixed with an update I am definitely turning off the auto update and waiting in the future for them to get the problems fixed before I update. This has been horrible.

I have had this problem for over a week and have been on to the support team 4 times.

I have been instructed to and have:

Cleared the NVAM

Cleared the SMC

Reinstalled the OS

I have now been told to either travel to an Apple store or go out and buy an external hard drive in order to wipe my iMac completely. My mac has a lot of installed and configured applications that would probably take me 8-10 hours to set back up. After reading through this thread it's unbelievable to me that they would suggest this and waste my time. I am going against their advice as others have stated they have followed all of Apple's suggested steps and to no avail. Not one success story here. First time I've taken to a forum to write anything as I am livid.

This is happening to two of my computers (2 iMacs all others that are laptops are fine). THIS IS A BUG !!!!
They have asked me to wipe my computer and have even asked me do you have any other software on there!!!

Really the only thing that changed was an upgrade to high Sierra the upgrade did not help to the latest 10.13.3!!!

They cannot seem to figure it out... I have been dealing with this for months since High Sierra upgrade.

Unfortunately I must report that after many years of almost glitch free Macbook Pro 15"use since a few months I cannot work efficiently anymore as every day I am faced with the sleep/wake bug. " days ago I reset the "energy saver" setting to default and turned bluetooth off and for almost 48 hrs everything seemed to be normal, than this morning my Mac was again stuck in sleep mode!

iMac (21.5 in, Late 2012) - Sleep Wake Failure after updating to High Sierra, currently Version 10.13.3

There are 637 responses to this comment, that is since mid December 2017, reporting the same issue. I have been reporting to Apple on an almost daily basis for about a month now. There is at least one other thread, discussing the same problem. All respondents are suffering persistent, disruptive and recurrent difficulties with their apple computers rebooting unexpectedly in sleep mode.

It is disgraceful that Apple would not even acknowledge the issue. This is an appalling attitude to mostly faithful and devoted customers.

So very disappointing!

Everyone who is having problems because of the premature release of High Sierra needs to call tech support and complain. I am sure there are many more people out there that are having problems but haven't reported it yet so Apple is not making this a high priority fix. My sister has been having her MacBook crash since HS but she just thought it was a random problem and hasn't reported it. I just sent Apple my third error log this week. I am now working with my 6th different advisor and he claims they are "focused on the problem" but Apple has yet to publicly acknowledge the problem and the engineers won't even give the advisors any kind of updates. So it appears they will continue to take there own sweet time until there is enough adverse public opinion to get the on the stick. If anyone knows how to get this problem out in the news that might help. COME ON APPLE!!!!

I have the same issue on my late 2013 iMac. Apple/AppleCare are in denial that it has anything to do with High Sierra. They act like no on else is having this issue. Their 'default' solution is to wipe the drive and do a clean install of High Sierra. Hopefully they will realize this is a fault and update the OS soon....

I suspect that the problem lies in a rewrite of all or a portion of the screen saver module in High Sierra. I recall that after installing 10.13.x last year, I could not run the BOINC screen saver for a few weeks until they rewrote their code to work with new screen saver APIs in High Sierra.

What is unusual for my iMac is that occasionally, when trying to wake it from sleep using the keyboard, I get no response. Pressing the power button briefly causes it to wake and restore the contents of RAM from the hard drive. I have only ever witnessed this behavior before on my MacBook when the battery is near death and as its final gasp, it saves the contents of RAM to the hard drive.

I am using a brand new iMac Pro and am having a similar problem. When I wake from sleep a gray screen opens ope and notifications show on right side of screen. External hard drives thrash away, then after about 15 minutes the screen itself wakes up and I can work. I think the problem is somehow related to external drives and porting them through the thunderbolt 3 port.

I've been following this thread since December 2017 when I upgraded my late-2012 iMac 21.5" to High Sierra. I'm currently running 10.13.3. Like many others, I've tried all of the suggestions in this thread and nothing works. I keep getting the sleep wake failure every single time my computer goes to sleep. My workaround has been to disable sleep completely, and this obviously works, but I don't like leaving the computer on all the time.

Just chiming in to plead Apple to fix this problem. If there are others out there lurking on this thread, please chime in. This needs a fix.

Hi Jim, there are many sites that purport to direct you in backdating to a previous OS. For example you could consult the devils themselves at macOS Sierra: Revert to a previous macOS version. As far as I understand the procedure suggests you return to a time machine backup where you were still with the previous OS. All this, of course, is well and good in emergency situations, where you somehow lost and/or corrupted your work and need to recover the best you can. Now, the instruction to go to a previous backup, appears to assume that one sits around between backups and does nothing else but wait for a new OS upgrade to enjoy and glory.

Why I would want to loose my uncorrupted work, which could be even very valuable, only because an update of the OS malfunctions, is totally beyond me.

Obviously, this is my very individual take on the situation, so please, explore options, which could be helpful in your particular circumstances.

Dear IdrisSeabright,

Thank you for your response. I fully appreciate the proprietary aspects of this forum and I try to respect rules, terms and conditions, use agreements and all. If you (and anyone else, who has the power to decide the fate of this comment) could kindly bear with me for a few more paragraphs, I shall do my best to present my position concisely and in the spirit of this discussion.

Firstly, few people will be surprised, if I say that I have not read the full terms and conditions or the use agreement. That is because many honest people will recognize how just about anyone nowadays (guiltily or not) has answered numerous times 'yes' to the question 'have you read and agreed with the terms and conditions' in order to proceed to the use of or involvement with some conditional offering. In some cases this is critical, in most this is just a way to move forward to more useful and meaningful activities.

I may not have read the TC but I can assure you that I have read more than 95pc of the entries to this and a parallel discussion on the same subject, available at https://discussions.apple.com/thread/8135104?start=105&tstart=0

While we all may enjoy friendly and relaxing discussions or some suggestions about useful tips and simple solutions as available throughout the numerous discussions on this site, the two threads I am referring to, happen to address a significant (critical it seems for some) performance issue with the HS OS. Although going through the usual customer support channels would be the recommended course of action, it doesn’t take long, reading through the threads, to see that not a single person has mentioned any success from going in this direction. Apple customer support staff have not managed any substantial help or resolution to an apparently persistent and impeding problem. Where do we go from here?

Just like with many community wide problems, people take every possible opportunity to press for a resolution, especially to problems, which are not a matter of convenience or ornamentation, but seriously affect their work and even cause damages. Well, the Apple Support Communities is one such direction.

It is unfortunate that we will never see a response from Apple here, but even with a minimal involvement, they may wish to realise that occasionally it might be beneficial to all concerned to go out of one’s way if this will help significantly a great number of people, especially if there is a possibility to prevent exasperating matters exacerbate.

At this stage I see two logical possibilities. Either Apple knows this is not a macOS High Sierra problem, but would maintain its involvement so minimal that would not do as little as to nudge a higher enough level member into even suggesting it, consequently leaving hundreds of users wondering how come their utterly diverse circumstances cause apparently identical malfunction. Or, Apple knows it is a macOS HS issue and would not acknowledge it, which is a lot more serious matter.

Whichever the case may be, hundreds of Apple users, at least those showing on this and the thread I mentioned above, quite likely many more, have been affected over an extended period of time and this forum becomes as good as any for them to express their expectations from Apple to help resolve the issue.

Here is the daily recurring reason for my plea:

Even with Power Nap turned on, the problem continues. Much less frequent than with it off. Roughly 105 hours since the last spontaneous restart.

Date/Time: 2018-02-27 22:13:14 -0600

OS Version: Mac OS X 10.13.3 (Build 17D102)

Architecture: x86_64h

Report Version: 26

Data Source: Stackshots

Event: Sleep Wake Failure

Duration: 0.10s

Steps: 9

Hardware model: iMac14,2

Active cpus: 4

Time Awake Since Boot: 380000s

Nope, not resolved. I have two 21.5 iMacs on a home network, both running Beta 5, one has the sleep wake problem consistently, the other does not. Both machines have very similar set-ups but they are not identical. One is late 2014 - this has the sleep wake problem, the other is late 2015 and does not have the problem. So far I haven't found whatever difference is causing the issue. None of the "fixes" have helped for me. Given that 1) many people have the problem but many people don't, 2) fixes seem to work for some but not all, 3) machines differ, and 4) installed software must differ a lot across the board, 5) problems started for many people with a change of OS ( the introduction of High Sierra), I believe the issue is probably far more complicated than we think and therefore there is no miracle cure. I'm sure Apple are working on it, and we'll get a result one day!

After updating to 10.13.4 yesterday, I decided to try disabling Power Nap again so that my iMac would actually sleep through the night. When I woke this morning, it did not respond to pressing the keyboard to wake. I had to briefly press the power switch to wake it. It woke, but with the gray screen where it reloads the contents of RAM back from the hard drive. It seems that sometime overnight, it decided that it was low on "battery power" and needed to save RAM contents. This on an iMac always connected to AC power. Sigh.