Sleep Wake Failure with High Sierra 10.13.2

I found it helpful to quit all of the apps at night. Then it doesn't have the sleep mode issue so bad. I also just started turning off the computer every night - that really solved the problem.

For those of us that use CAD- the problem is CAD doesn't upgrade their software as fast as apple is creating new operating systems. SO be careful..

Really sorry to learn about it, jtonn. It would have been utterly ridiculous, if it was not so painfully disruptive for such a long time now. How did they manage to only part-solve the problem! Compared to the pre-10.13.5 daily reboots, it is, admittedly, some progress, but why the SWF hasn't been eliminated completely is totally baffling. As you say, let's cling to hope :-/

Hi again. Ok, I may have discovered a work-around to this problem.

This morning I went to wake my (27" late 2012) iMac (OS 10.13.6) but it would not wake. I have Power Nap enabled, as this has been suggested may be good practice for the SWF... and for the last few occasions this seems indeed to have made a difference. However, today it would not wake.

I wondered if I were to press the space bar (or any other keys) for a time then, because Power Nap is enabled, the Mac would "wake" during one of these presses (to check for mail or whatever) and "know" that it's being asked to wake.

No joy.

It then occurred to me that if I were to give it a real jolt, then that may be sufficient to wake it. So I plugged in a USB-powered drive... and hey presto, the Mac burst into life.

This only happened this morning, so I haven't repeated the experiment - thus I only offer this as a possible solution, and would be interested to hear if it works for others. Please let me know. Thanks.

I had this problem on my 2014 MB pro 15 inch (max specs). I had the problem persist and it would restart so many times the battery would drain between 60-80% in 1 hour. I would travel to work or a friends house (with max charge) and get to my destination with basically little to no battery. I did a full restore 3 times - at the apple store. Apple also removed and replaced my entire computer (except for the display) many times and the problem persisted. I spilled a tiny bit of water and the intake sucked it in, my 2014 MB Pro went kaputs.

Bought a 2015 brand new 15 inch MB Pro in June (when they still had the old ones - I got it for 1399 no tax 😀 big come-up). The sleep wake failure has happened 2 times since. I had set up the Mac completely new. Maybe after a whole year and a whole OSX later, they might have the problem resolved or even better, give us new software quirks, bugs, and garbage.

5 FRESH setups later (NOT EVEN TIME MACHINE BACKUPS), we still have the same problem but apple will still blame the user.

I feel as though something in the cloud is causing these errors. My iPhone X has a ton of issues and on amount of "set up as new" helps. I have set up my iPhone X as new twice since November and the same problems persist (even with a new device). Apple claims its impossible for there to be errors in iCloud, even for a power user (load of BS in my opinion). Apple ignores the issue because they are too big to fail. Just like all the iTunes issues they haven't fixed in 7 years. Without Steve, I don't know if they are launching items with proper testing or not. Seems like there is no more quality control.

Well, I just installed Mojave. I think I'll wait for a few days before I test out disabling "Power Nap" to see how my iMac behaves. I really, truly hope that this thread will become an annoying, distant memory.

I have the same issue with the new I9 MacBook pro. This issue is still present after the upgrade to Mojave. Once the screensaver starts, roughly 25 mins later a reboot takes place and you to provide my password to log in (touchId will not work)

This happens you set a corner to be a hot corner that triggers the screen saver and you are required to log in to get back into the MacBook.

If you close the lid you do not have the issue. Once you reopen the lid you can use touchId to get into the MacBook and all applications are in the same state as you left them.

I will try lock screen from the apple in the upper right corner next to see if that makes any difference after roughly 25 mins?

I use Parallels Desktop and I found out, that it's function "check for update" is causing "sleep wake failure".

It just happened to me again, after almost 22 days. I was woken by the double bong restart shortly after midnight. Sigh. Note that this is with Power Nap enabled.

Well, that experiment didn't last long (Power Nap disabled). Less than 24 hours before a spontaneous restart. Back to enabling Power Nap to cut down on the number of restarts.

You can downgrade to normal Sierra here:

https://support.apple.com/en-us/HT208202

I wouldn't hold your breath.

Same problem with my 2012 iMac. 10.13.2 breaks the Sleep. Fix coming????

Same problem with my 2012 mac mini running 10.13.2. The daily timer to supend it a midnight is not working any more. In the morning the timer warning "goind to sleep soon" is is still on the screen.

It worked on my iMAC. Thanks.

Nevermind. I put it to sleep after I was done posting that, and then five minutes later it rebooted itself. I give up. It's sad to think that my Windows 10 Surface Pro 4 is my stable computer.