Sleep Wake Failure with High Sierra 10.13.2

I'm having this problem too. The workaround - on a desktop machine - is to leave the thing on all the time by disabling sleep, rather than turning it off.

iMac (2012?) High Sierra 10.13.4

I reset the SMC on my iMac and it has been almost 24 hours without the dreaded Sleep Wake Failure. I'm keeping my fingers crossed!

Disconnecting my second monitor prevents the issue from happening for me.

iMac (27-inch, Late 2013) 10.13.5

I have MacBook Pro (Retina, 13-inch, Early 2015) with the same problem. I went back to Sierra for a while (did that at the genius bar) and that fixed it. Then I assumed after some updates that it was safe to update to High Sierra again - and the problem is back once again with a vengeance!

My advice don't update to HS if you can avoid it.

I have a temporary solution which is to use an app called "InsomniaX" which prevents sleep on lid closure (although it has been known to create overheating problems so you have to watch that closely. I use this when I carry my laptop from one room to another (it the lid closed). Otherwise when I move around it pretty much aways crashes. For longer journeys the computer has to be completely switched off now.

I have found that it is better to shut down my iMac rather than let it go to sleep mode and have a sleep wake issue restart.

It takes about 2 minutes to boot up from a shut down vs 4 minutes for a sleep wake restart

Still a major inconvenience I wish I did not have to deal with!

Here is my story. It started about a week ago. I found my supposed-to-be-sleeping MacBook Air (HS 12.3.3) awake in the middle of the night, green screen with a folder with a flashing question mark. Hard reboot, everything back to normal. From time to time, I started to have wake-from-sleep issues (ie, open the lid, black screen, nothing happens, hard reboot using the power button).


The flashing question mark folder re-appeared almost every night, or in the morning when opening the laptop lid.


Tried everything I found in internet, including PRAM, SMC, safeboot, recoverymode and diskutility, reisntalled combo 10.13.3, installed the recent 10.13.3 supplemental. Nothing works.


Going through console system.log, I found a weird "5 [RE] Reachability changed" as the last entry before the freeze. See these examples:


Feb 21 00:27:35 DZ-MacBookProi5 uc[67]: 5 [UP] Transitioning from 3 to 1


Feb 21 00:27:38 DZ-MacBookProi5 com.apple.xpc.launchd[1] (com.apple.preference.displays.MirrorDisplays): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

Feb 21 00:27:41 DZ-MacBookProi5 uc[67]: 5 [RE] Reachability changed

Feb 21 08:27:38 localhost bootlog[0]: BOOT_TIME 1519198058 0

Feb 21 10:55:45 DZ-MacBookProi5 CheckmateIdleDaemon[117]: The system WILL go to sleep...


Feb 21 10:55:45 DZ-MacBookProi5 loginwindow[122]: magsafeStateChanged state changed old 1 new 2

Feb 21 10:55:46 DZ-MacBookProi5 fud[30895]: objc[30895]: Class MobileAssetUpdater is implemented in both /System/Library/PrivateFrameworks/MobileAccessoryUpdater.framework/Support/fud (0x102ec4e10) and /System/Library/AccessoryUpdaterBundles/ApplePowerAccessoryUpdater.bundle/Conte nts/MacOS/ApplePowerAccessoryUpdater (0x102fd28f8). One of the two will be used. Which one is undefined.

Feb 21 10:55:46 DZ-MacBookProi5 uc[64]: 5 [RE] Reachability changed

Feb 21 11:18:41 localhost bootlog[0]: BOOT_TIME 1519208321 0

Isthat "Reachability changed" entry involved with the freeze? this is the last entry in system.log before the freeze. Anybody seeing the same entry?


As last resort, I tried to disable safesleep.

In /private/var/vm i found a sleepimage file, created on February 15 (when I started to have the issue, but it might be a coincidence).


I disabled safesleep (pmset -a hybernatemode 0), rebooted in recovery mode (CMD+R), disabled SIP (csrutil disable), rebooted, deleted the safesleep file, rebooted in recovery mode, enabled SIP (csrutil enable) and re-booted normally.


System has created a new sleepimage file.


In summary, I removed the old sleepimage, I left hibernatemode on 0. Let's see what happens.


ghogoh wrote:

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.

It is, however, pointless to do so. If you want to express something to Apple, contact them directly. Use the Contact Support button at the top right of every page. Use the feedback page. Or, make an appointment at the Genius Bar at your local Apple Store. If you contact Apple in any of those ways, they track the issues. That's how they learn the scope of a particular problem.

I had a senior advisor tell me that those "anonymous" error reports to Apple are evaluated to discover error trends, but who knows? I guess only Apple knows and they won't say. Apple has really been tight lipped and non-responsive on most of the problems that the crappy High Sierra has caused. Very few of the 9 different advisors that I have contacted knew anything about the sleep wake failure before I talked to them and many tried to get me to wipe my drive and start over which fortunately I didn't do since no one on this discussion had any good results from doing that. I am afraid it could be months or longer before they come out with a solution. My iMac had not been restarting as often since I turned on Power Nap. Apple didn't even know that was a temporary work around.

I did a pretty extreme test. I erased my disk, installed a fresh copy of High Sierra without importing any user or data, without installing any program, just High Sierra. And I still had the Sleep Wake Failure!

I erased my disk again and installed Sierra and no more Sleep Wake Failure. Then I contacted Apple about these tests and Senior Advisor was helpless. She told me I have to go to High Sierra again to see if the problem happens again... Pffff I just know this will happen again! I told her to read this forum. It did not seam like a knowed issue for her. Since I don't have High Sierra anymore, she told me she could not help me.

After having installed the latest developer beta 4 of 10.13.4 (17E170c), I have not experienced any sleep/wake failures within the last 3 days since the update was installed. I also restored the default Energy Saver settings with the Power Nap setting disabled. This problem has also been occurring for me since the original High Sierra install version 10.13.1 and I have a Late 2012 iMac. Has anyone had the problem still occur after installing the latest developer beta 4 update of 10.13.4? Hoping that is the version with the code-fix we've all been waiting for. Fingers crossed!

No it doesn't - well, it might for a few, but I like many others have never had File Vault enabled. Now this next comment is just another observation - it's not a fix, on my two iMacs with very similar setups, the late 2015 has never had a problem, but the late 2013 has been plagued with SWF issues. Since installing 10.13.5 beta 2 neither machine has had a problem, so something in 5 Beta 2 must be interacting differently.

I totally agree with you. The latest Apple rep that I have worked with on the SWF problem says that Apple won't even say if they are working on the problem. High Sierra has been causing the SWF error on my computer since the day I downloaded in November. I am more fortunate than many users since some member in this forum told me that enabling PowerNap stopped their computer from stalling and restarting daily. It has worked for me but HS still screwed my machine up because every time I turn PN off I get the dreaded SWF. Candor and honesty on Apple's part would help. Of course not releasing faulty operating systems would be nice too. Good luck to all of us whose computers are having sleeping problems.

Just an update on my post last week. Since installing 10.13.5 beta 2 the problem has stopped, so something in 5 Beta 2 must be interacting differently. I've had no swfs since installing it. I appreciate not everyone wants to try beta releases, but has anyone on here had problems with 2? it would be interesting to know. I could just be lucky!

I did try the above steps and I'm still having this issues. Apple support were of now help at all. I know it's only a small thing but has everybody who is having this issues reported it to Apple on the feedback form? It may help them take notice Product Feedback - Apple

It's been 4 days now since turning Power Nap back on and I've not had any further problems.